MCP-researcher Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERPLEXITY_MODEL | No | The Perplexity model to use (e.g., sonar-reasoning) | sonar-reasoning |
| PERPLEXITY_API_KEY | Yes | Your Perplexity API key from https://www.perplexity.ai/settings/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Perform a general search query to get comprehensive information on any topic |
| get_documentationB | Get documentation and usage examples for a specific technology, library, or API |
| find_apisC | Find and evaluate APIs that could be integrated into a project |
| check_deprecated_codeC | Check if code or dependencies might be using deprecated features |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: checking deprecated code, finding APIs, getting documentation, and performing general searches. The descriptions make it easy for an agent to select the right tool for each specific research task.
Three tools follow a consistent verb_noun pattern (check_deprecated_code, find_apis, get_documentation), but 'search' deviates as a single verb without an object. This minor inconsistency slightly affects predictability, though all names remain readable.
With only 4 tools, the set feels thin for a research server that aims to cover broad information-gathering tasks. While each tool is useful, the scope suggests more specialized research operations could be missing, making it borderline appropriate.
The tools cover key research functions like checking deprecations, finding APIs, getting docs, and general searches, but there are notable gaps. For example, missing tools for comparing technologies, validating information sources, or tracking research progress limit comprehensive workflow coverage.