Developer Research MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | Your unique OpenRouter API key. | |
| OPENROUTER_API_URL | No | The base URL for the OpenRouter API. Defaults to https://openrouter.ai/api/v1. | https://openrouter.ai/api/v1 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_webC | Search the web using OpenRouter and return relevant results |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The purpose is unambiguous.
The tool name 'search_web' follows a clear verb_noun pattern, which is consistent and predictable.
With only one tool, the server feels very thin for a 'Developer Research' server. A few more tools would be expected to cover the domain adequately.
The server only offers a single web search operation. For developer research, one might expect additional capabilities like code or documentation search, but the basic search function is complete for its narrow purpose.