A side-by-side look at the Fetch and Vectorize MCP Server 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 Vectorize MCP Server for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
create_entities, create_relations, add_observations.VECTORIZE_ORG_ID, VECTORIZE_TOKEN, VECTORIZE_PIPELINE_ID.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 90/100 · Excellent | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | VECTORIZE_ORG_IDVECTORIZE_TOKENVECTORIZE_PIPELINE_ID |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,147 | 115 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Fetch | View Vectorize MCP Server |
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 namesNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
{
"mcpServers": {
"vectorize-io-vectorize-mcp-server": {
"command": "npx",
"args": [
"-y",
"@vectorize-io/vectorize-mcp-server@latest"
],
"env": {
"VECTORIZE_ORG_ID": "YOUR_VECTORIZE_ORG_ID_HERE",
"VECTORIZE_TOKEN": "YOUR_VECTORIZE_TOKEN_HERE",
"VECTORIZE_PIPELINE_ID": "YOUR_VECTORIZE_PIPELINE_ID_HERE"
}
}
}
}