MCP Graphql vs Npm Trends API
A side-by-side look at the MCP Graphql and Npm Trends API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Graphql for developer tools work as a local process; choose Npm Trends API for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Graphql when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
introspect-schema, query-graphql.
Choose Npm Trends API when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TRENDSAPI_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed |
Tools & capabilities
MCP Graphql tools 2
introspect-schemaThis tool retrieves the GraphQL schema. Use this first if you don't have access to the schema as a resource.query-graphqlExecute GraphQL queries against the endpoint. By default, mutations are disabled unless `ALLOW_MUTATIONS` is set to `true`.
Npm Trends API tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Graphql
{
"mcpServers": {
"blurrah-mcp-graphql": {
"command": "npx",
"args": [
"-y",
"mcp-graphql"
]
}
}
}
Npm Trends API
{
"mcpServers": {
"npm-trends-api-2": {
"command": "uvx",
"args": [
"trendsapi-npm"
],
"env": {
"TRENDSAPI_KEY": "YOUR_TRENDSAPI_KEY_HERE"
}
}
}
}
Frequently asked questions
MCP Graphql is categorized under Developer Tools and uses a local stdio subprocess. Npm Trends API belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Graphql for developer tools work and Npm Trends API for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Graphql is listed as free. Auth: no auth required. Npm Trends API has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add blurrah-mcp-graphql and npm-trends-api-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Graphql has a quality signal of 57/100 (Good) with 4 views, 0 installs and 408 GitHub stars. Npm Trends API has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.