Poordjaevin vs Context7
A side-by-side look at the Poordjaevin and Context7 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Poordjaevin for developer tools work as a local process; choose Context7 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 Poordjaevin when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
POORDJAEVIN_BACKEND, POORDJAEVIN_ACP_MODEL, POORDJAEVIN_ACP_TIMEOUT, POORDJAEVIN_ACP_MAX_COST, POORDJAEVIN_ABSTAIN, DEVIN_CLI_PATH, DEVIN_CREDENTIALS_PATH.
Choose Context7 when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
resolve-library-id, query-docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | POORDJAEVIN_BACKENDPOORDJAEVIN_ACP_MODELPOORDJAEVIN_ACP_TIMEOUTPOORDJAEVIN_ACP_MAX_COSTPOORDJAEVIN_ABSTAINDEVIN_CLI_PATHDEVIN_CREDENTIALS_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 63,150 |
| Directory activity | 0 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Poordjaevin | View Context7 |
Tools & capabilities
Poordjaevin tools
No tool names declared yet. Check the project README from the listing page.
Context7 tools 2
resolve-library-idResolves a general library name into a Context7-compatible library ID.query-docsRetrieves documentation for a library using a Context7-compatible library ID.
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.
Poordjaevin
{
"mcpServers": {
"poordjaevin": {
"command": "uvx",
"args": [
"poordjaevin"
],
"env": {
"POORDJAEVIN_BACKEND": "YOUR_POORDJAEVIN_BACKEND_HERE",
"POORDJAEVIN_ACP_MODEL": "YOUR_POORDJAEVIN_ACP_MODEL_HERE",
"POORDJAEVIN_ACP_TIMEOUT": "YOUR_POORDJAEVIN_ACP_TIMEOUT_HERE",
"POORDJAEVIN_ACP_MAX_COST": "YOUR_POORDJAEVIN_ACP_MAX_COST_HERE",
"POORDJAEVIN_ABSTAIN": "YOUR_POORDJAEVIN_ABSTAIN_HERE",
"DEVIN_CLI_PATH": "YOUR_DEVIN_CLI_PATH_HERE",
"DEVIN_CREDENTIALS_PATH": "YOUR_DEVIN_CREDENTIALS_PATH_HERE"
}
}
}
}
Context7
{
"mcpServers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"ctx7"
]
}
}
}
Frequently asked questions
Poordjaevin is categorized under Developer Tools and uses a local stdio subprocess. Context7 belongs to Developer Tools and uses a local stdio subprocess. Pick Poordjaevin for developer tools work and Context7 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.
Poordjaevin has no declared pricing — check the project's own site. Context7 is listed as free. 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 poordjaevin and upstash-context7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Poordjaevin has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. Context7 has 65/100 (Great) with 9 views, 0 installs and 63,150 GitHub stars.