How to add an MCP server to mcp-client-cli
mcp-client-cli reads its MCP servers from ~/.llm/config.json and connects to them over stdio (a local process).
85,195 of the 123,047 servers we can write a config for work in it.
A local server
A local server runs on your machine, started by mcp-client-cli from its package. It needs Node.js installed first. For example, Azure MCP Server goes in ~/.llm/config.json:
{
"mcpServers": {
"azure": {
"command": "npx",
"args": ["-y", "@azure/[email protected]", "server", "start"]
}
}
} Which servers work in mcp-client-cli
mcp-client-cli cannot send a header to a remote server, so the 3,252 servers that need a key in one do not work in it.
| Runs | Servers | In mcp-client-cli? |
|---|---|---|
| Local (stdio) | 85,195 | Works |
| Remote, Streamable HTTP | 30,889 | No |
| Remote, Streamable HTTP, key in a header | 3,205 | No |
| Remote, HTTP+SSE | 3,711 | No |
| Remote, HTTP+SSE, key in a header | 47 | No |
If the server does not show up
- A remote server that does not connect
- The environment variables servers ask for
- mcp-client-cli's own MCP documentation
Matches the official docs The configs follow mcp-client-cli's MCP docs, read on 2026-10-31.
mcp-client-cli on plug.directory · Best MCP servers for mcp-client-cli