How to add an MCP server to ECA
ECA reads its MCP servers from ~/.config/eca/config.json (global) or .eca/config.json in the project and connects to them over stdio (a local process), Streamable HTTP and HTTP+SSE.
123,032 of the 123,032 servers we can write a config for work in it.
A local server
A local server runs on your machine, started by ECA from its package. It needs Node.js installed first. For example, Azure MCP Server goes in ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"azure": {
"command": "npx",
"args": ["-y", "@azure/[email protected]", "server", "start"]
}
}
}A remote server
A remote server runs on its publisher's machines, and ECA connects to its address. Nothing needs installing. For example, Context7 goes in ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"context7": {
"url": "https://mcp.context7.com/mcp"
}
}
}Which servers work in ECA
ECA can send a key in a header, so the 3,251 servers that need one work in it.
| Runs | Servers | In ECA? |
|---|---|---|
| Local (stdio) | 85,194 | Works |
| Remote, Streamable HTTP | 30,876 | Works |
| Remote, Streamable HTTP, key in a header | 3,204 | Works |
| Remote, HTTP+SSE | 3,711 | Works |
| Remote, HTTP+SSE, key in a header | 47 | Works |
If the server does not show up
- A remote server that does not connect
- The environment variables servers ask for
- ECA's own MCP documentation
Matches the official docs The configs follow ECA's MCP docs, read on 2026-11-01.