Crawlwise vs Project Context MCP
A side-by-side look at the Crawlwise and Project Context MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
CrawlwiseDeveloper ToolsSEO audits and AI crawler checks. Honest findings only; no invented scores.35FairAuth: oauth 2.0Verdict: choose Crawlwise for developer tools work; choose Project Context MCP 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?
CChoose Crawlwise when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: OAuth 2.0.
Choose Project Context MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Crawlwise | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 35/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Crawlwise | View Project Context MCP |
Tools & capabilities
Crawlwise tools
No tool names declared yet. Check the project README from the listing page.
Project Context MCP 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.
Crawlwise
No confirmed install command for Crawlwise yet — follow the setup steps linked from its listing page rather than a guessed package name.
Project Context MCP
{
"mcpServers": {
"ericbrown-project-context-mcp": {
"command": "uvx",
"args": [
"project-context-mcp"
]
}
}
}
Frequently asked questions
Crawlwise is categorized under Developer Tools and uses an install path we have not confirmed yet. Project Context MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Crawlwise for developer tools work and Project Context MCP 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. Crawlwise has no confirmed install command yet — follow its own setup instructions.
Crawlwise is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Project Context MCP is listed as free. Auth: no auth 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 crawlwise and ericbrown-project-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Crawlwise has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Project Context MCP has 51/100 (Good) with 3 views, 0 installs and 6 GitHub stars.