Fetch vs Staan
A side-by-side look at the Fetch and Staan MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
StaanSearch & Data Extraction · Local subprocess (stdio)Web search with full-page content and grounded answers from the Staan API.52GoodAuth: api key requiredVerdict: choose Fetch for search & data extraction work as a local process; choose Staan for search & data extraction as a local process. 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
create_entities, create_relations, add_observations.
SChoose Staan when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
STAAN_API_KEY. - You want tools like
web_search, answer.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Staan | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 90/100 · Excellent | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Not declared |
| Required env vars | None listed | STAAN_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,147 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | 2 |
| Full listing | View Fetch | View Staan |
Tools & capabilities
Fetch tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
Staan tools 2
web_searchSearches the web through `POST /v2/search/web`. Each call returns one page of up to 10 resultsanswerAsks `POST /v2/answer` for an answer grounded in web sources (or in sources you supply). The
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": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Staan
{
"mcpServers": {
"staan": {
"command": "uvx",
"args": [
"staan-mcp"
],
"env": {
"STAAN_API_KEY": "YOUR_STAAN_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Fetch is categorized under Search & Data Extraction and uses a local stdio subprocess. Staan belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Fetch for search & data extraction work and Staan 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. Staan has no declared pricing — check the project's own site. Auth: api key required. 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 staan 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 90/100 (Excellent) with 4 views, 0 installs and 91,147 GitHub stars. Staan has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.