Fetch vs Servicegraph
A side-by-side look at the Fetch and Servicegraph MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fetch for search & data extraction work as a local process; choose Servicegraph for search & data extraction over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
fetch.
Choose Servicegraph when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
SERVICEGRAPH_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 80/100 · Excellent | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | SERVICEGRAPH_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,540 | 61 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Fetch | View Servicegraph |
Tools & capabilities
Fetch tools 1
fetchFetches a URL from the internet and extracts its contents as markdown.
Servicegraph 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.
Fetch
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}
}
Servicegraph
{
"mcpServers": {
"servicegraph": {
"url": "https://mcp.servicegraph.co"
}
}
}
Frequently asked questions
Fetch is categorized under Search & Data Extraction and uses a local stdio subprocess. Servicegraph belongs to Search & Data Extraction and uses a remote HTTP/SSE transport. Pick Fetch for search & data extraction work and Servicegraph for search & data extraction.
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.
Fetch is listed as free. Auth: no auth required. Servicegraph 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 fetch and servicegraph as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fetch has a quality signal of 80/100 (Excellent) with 5 views, 0 installs and 91,540 GitHub stars. Servicegraph has 40/100 (Fair) with 0 views, 0 installs and 61 GitHub stars.