MCP server providing research tools by proxying an upstream API (e.g., Perplexity)
If you already use Researcher MCP, the researcher mcp mcp server is the piece that lets your assistant work with it directly. MCP server providing research tools by proxying an upstream API (e.g., Perplexity).
A powerful research assistant that integrates with Cline and Claude Desktop! Leverages Perplexity AI for intelligent search, documentation retrieval, API discovery, and code modernization assistance - all while you code.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: PERPLEXITY_API_KEY, PERPLEXITY_MODEL. 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.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by clssck; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Researcher MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"perplexity-server": {
"command": "node",
"args": ["[path/to/researcher-mcp/build/index.js]"],
"env": {
"PERPLEXITY_API_KEY": "pplx-...",
"PERPLEXITY_MODEL": "sonar-reasoning" // you can use different models
},
"disabled": false,
"alwaysAllow": [],
"autoApprove": [
"search",
"get_documentation",
"find_apis",
"check_deprecated_code",
"get_request_status"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PERPLEXITY_API_KEY | Credential the server authenticates with. | Yes |
| PERPLEXITY_MODEL | 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.