01 · Why connect
Copilot CLI documents local and remote HTTP MCP servers. Subscription and org policies still apply.
Use the documented HTTP MCP example, not a stdio npx wrapper for Make0. The Make0 MCP URL is https://make0.ai/mcp. GitHub Copilot CLI can sign in with OAuth on any plan, or use an API key on Pro and Max. Either way, you pick which brains it can use.
02 · How to connect GitHub Copilot CLI
Install Make0 Brain in 4 steps
- 01
Install Copilot CLI
Install and authenticate GitHub Copilot CLI.
- 02
Edit MCP config
Add make0-brain with URL https://make0.ai/mcp in ~/.copilot/mcp-config.json.
- 03
Sign in
Complete Make0 OAuth when Copilot CLI starts the server.
- 04
Test
Ask Copilot CLI to list brains or search a known memory.
03 · ~/.copilot/mcp-config.json
Copy this into GitHub Copilot CLI
Use HTTP or Streamable HTTP. Do not wrap Make0 as a local stdio command. This config signs in with OAuth.
{
"mcpServers": {
"make0-brain": {
"type": "http",
"url": "https://make0.ai/mcp"
}
}
}04 · API key
Or connect with an API key
On Pro and Max you can skip the sign-in and use an API key. In Make0, open Connect Brain via MCP, choose API key MCP, and create a key with the brains and access it needs. Add a headers block to the server in mcp-config.json.
~/.copilot/mcp-config.json
{
"mcpServers": {
"make0-brain": {
"type": "http",
"url": "https://make0.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_MAKE0_API_KEY"
}
}
}
}Replace YOUR_MAKE0_API_KEY with your key. Make0 shows a key once, so keep it somewhere safe. You can revoke it any time in Settings.
05 · System instruction
Tell the agent to prefer Make0 Brain
Paste this into GitHub Copilot CLI’s system instructions or custom instructions so it reads and writes memory through Make0 instead of its own store.
Make0 Brain is my source of truth for durable memory. Always search it before answering about me, my work, people, preferences, or past decisions. Save lasting facts and decisions to Brain. Never guess or invent memories. Use Brain exclusively for durable memory.
Questions
Connecting GitHub Copilot CLI
How do I connect Make0 Brain to GitHub Copilot CLI?+
Add Make0 as a remote HTTP MCP server using https://make0.ai/mcp. In the Make0 connect dialog, choose OAuth and GitHub Copilot CLI will open a sign-in so you can pick which brains it can use. On Pro or Max, if GitHub Copilot CLI accepts custom headers, you can choose API key MCP instead and send the key to this URL as Authorization: Bearer.
What is the Make0 MCP URL?+
The production Make0 Brain MCP endpoint is https://make0.ai/mcp. Use HTTP or Streamable HTTP if the client asks for a transport. Server name: make0-brain.
Does Make0 Brain MCP use OAuth?+
Yes. Compatible clients discover OAuth from the MCP server, you sign in to Make0, and you grant read or write access to specific brains. Two-factor authentication may be required.
Can I use an API key instead of OAuth?+
On Pro or Max, yes, for apps that let you set an HTTP header. Open Connect Brain via MCP, choose API key MCP, and create a key for specific brains or all brains. Send it to https://make0.ai/mcp as Authorization: Bearer. OAuth works on every plan; Free and Lite use OAuth.
Official GitHub Copilot CLI MCP docs: docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers
