A multi-agent research MCP server + mini client adapter - orchestrates a net of async agents or streaming swarm to conduct ensemble consensus-backed
A multi-agent research MCP server + mini client adapter - orchestrates a net of async agents or streaming swarm to conduct ensemble consensus-backed research. Each task builds its own indexed pglite database on the fly in web assembly. That is what the openrouter agents mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Production MCP server for multi-agent AI research. Plan, parallelize, synthesize.
Installation goes through your MCP client rather than a global install: point it at @terminals-tech/openrouter-agents on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 14 tools. What each one is for:
research — Async research (returns job_id)conduct_research — Sync research with streamingbatch_research — Parallel batch queriesresearch_follow_up — Context-aware follow-upagent — Unified entrypoint (auto-routes)search — Hybrid BM25+vector searchretrieve — Index or SQL queryquery — SQL SELECT with paramsget_report — Get report by IDhistory — List recent reportscheckpoint — Named save pointsfork_session — Create alternate timelineConfiguration is passed through the environment: OPENROUTER_API_KEY, INDEXER_ENABLED. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. OpenRouter Agents's toolset — research, conduct_research, batch_research and 11 more — is a fair guide to whether it matches your workflow. It is maintained by wheattoast11; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| research | Async research (returns job_id) |
| conduct_research | Sync research with streaming |
| batch_research | Parallel batch queries |
| research_follow_up | Context-aware follow-up |
| agent | Unified entrypoint (auto-routes) |
| search | Hybrid BM25+vector search |
| retrieve | Index or SQL query |
| query | SQL SELECT with params |
| get_report | Get report by ID |
| history | List recent reports |
| checkpoint | Named save points |
| fork_session | Create alternate timeline |
| graph_traverse | Explore knowledge graph |
| graph_clusters | Find node clusters |
{
"mcpServers": {
"openrouter-agents": {
"command": "npx",
"args": ["@terminals-tech/openrouter-agents", "--stdio"],
"env": {
"OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}",
"INDEXER_ENABLED": "true"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPENROUTER_API_KEY | Credential the server authenticates with. | Yes |
| INDEXER_ENABLED | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.