ANHA in Copilot
GitHub Copilot reads MCP servers from a JSON file. Which file, and which root key, depends on whether you are in VS Code or the CLI — and getting that pair wrong is the single most common reason ANHA does not appear.
Install
VS Code: create .vscode/mcp.json
In your workspace, create .vscode/mcp.json with a servers block.
VS Code speaks the HTTP transport directly, so no local shim is needed.
.vscode/mcp.json{ "servers": { "anha": { "type": "http", "url": "https://resolver.anha.ai/mcp" } } }VS Code uses the root key servers. The Copilot CLI uses mcpServers. They are not interchangeable, and the wrong one fails silently.
Copilot CLI: create the Agent Host config
The CLI no longer reads .vscode/mcp.json. Put this in ~/.copilot/mcp-config.json for every project, or .mcp.json in a project root.
~/.copilot/mcp-config.json{ "mcpServers": { "anha": { "type": "http", "url": "https://resolver.anha.ai/mcp" } } }Sign in
Approve the handle you want Copilot to act for. The browser opens once and the token is cached on this machine.
Terminalnpx -y anha-mcp login
Test
List the servers
In VS Code, run MCP: List Servers from the command palette — it also offers start, stop and restart.
Configure only one location per server: the same server in both places causes conflicts.
MCP: List ServersYou should see
anha http RunningThen ask for something real
A passing check only proves the connection works. This proves the model can actually reach the tools.
“Use ANHA to resolve @nike.ai and tell me what it can do.”
Troubleshoot
- ANHA never appears, and there is no error
Cause — The root key does not match the host: servers for VS Code, mcpServers for the CLI and Agent Host.
Fix — Open the file and check the root key against the host you are actually running. Both are valid JSON, so neither host complains.
- It works in VS Code but not in the CLI
Cause — The config lives in .vscode/mcp.json, which the CLI stopped reading.
Fix — Copy it to ~/.copilot/mcp-config.json or .mcp.json, changing the root key to mcpServers.
- No ANHA tools appear at all
Cause — The config file was edited while the app was running, so it is still holding the old server list.
Fix — Quit the app completely and start it again. Opening a new tab or window is not enough.
- The tools are listed, but every call answers that you are not signed in
Cause — The browser approval was closed before it finished, or you approved with an email address that owns no handle.
Fix — Run npx -y anha-mcp login again and sign in with the same email you registered the handle under. If you have no handle yet, register one first — the approval screen has nothing to offer otherwise.
- An order or payment just hangs
Cause — This is not a fault. The merchant requires phone approval, so the call returns a pending status with a request id.
Fix — Approve it on your phone. A human decision can take minutes, and the caller polls until it lands.
Still stuck?
Every guide shares the same sign-in and the same tools, so a fix on another platform often applies here too.