openrouter-deep-research

OpenRouter Agents MCP server provides a multi-agent research environment that exposes a set of tools for research planning, knowledge management, session graphs, and model routing. The server uses the OpenRouter Agents package to orchestrate agents and toolchains, enabling synchronous and asynchronous research tasks, knowledge-base queries, and embedding-based model selection. Typical usage is via STDIO transport, where MCP clients (such as Claude, Jan AI, Continue, or custom clients) communicate with the server to run tools like research, batch_research, retrieve, and graph operations. Tools are grouped under categories such as Research, Knowledge Base, Session & Graph, Rail Protocol, and Utility, each exposing commands for planning, data retrieval, and exploration of knowledge graphs and routing rails. To connect, configure the MCP client to launch the server via npx @terminals-tech/openrouter-agents --stdio and provide the necessary environment variable OPENROUTER_API_KEY.

Prerequisites:

• Node.js (LTS version recommended, e.g., 18.x) and npm installed.
• Access to an OpenRouter API key (OPENROUTER_API_KEY).

Installation steps:

1. Ensure Node.js and npm are installed.
2. Install and run the MCP server client using npx:

npx @terminals-tech/openrouter-agents --stdio

3. If you need to wire this into an MCP configuration file, use the following example (adjust KEYs as needed):

{
  "mcpServers": {
    "openrouter-agents": {
      "command": "npx",
      "args": ["@terminals-tech/openrouter-agents", "--stdio"],
      "env": {
        "OPENROUTER_API_KEY": "<OPENROUTER_API_KEY>",
        "INDEXER_ENABLED": "true"
      }
    }
  }
}

4. Optionally integrate with Claude or other MCP clients by following the client-specific setup in the README (e.g., using the provided JSON snippets or CLI commands).

Tips and caveats:

• The server defaults to STDIO transport; use HTTP mode explicitly if your client requires it (see transport options in the README).
• Set OPENROUTER_API_KEY in your environment to enable OpenRouter access; you can also provide a rotating set with OPENROUTER_API_KEYS if needed.
• If you encounter macOS/Node 25 related shutdown messages, they are cosmetic; data is checkpointed. You can enable in-memory mode by setting DB_AUTO_HEAL=true for no-persistence operation.
• The MCP configuration supports embedding routing, knowledge indexing, and circuit-breaker features; configure EMDEDING_ROUTING_ENABLED and INDEXER_ENABLED as needed.
• When updating dependencies (e.g., MCP SDK, Zod, Express), verify compatibility with your MCP specification version (2025-11-25).