EveryPage vs Codegraphcontext
A side-by-side look at the EveryPage and Codegraphcontext MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose EveryPage for marketing work as a local process; choose Codegraphcontext 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 EveryPage when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EVERYPAGE_API_KEY.
Choose Codegraphcontext 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 | ||
|---|---|---|
| Category | Marketing | Developer Tools |
| Quality signal | 43/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | EVERYPAGE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 4,338 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View EveryPage | View Codegraphcontext |
Tools & capabilities
EveryPage tools
No tool names declared yet. Check the project README from the listing page.
Codegraphcontext 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.
EveryPage
{
"mcpServers": {
"everypage": {
"command": "npx",
"args": [
"-y",
"everypage-mcp"
],
"env": {
"EVERYPAGE_API_KEY": "YOUR_EVERYPAGE_API_KEY_HERE"
}
}
}
}
Codegraphcontext
{
"mcpServers": {
"shashankss1205-codegraphcontext": {
"command": "uvx",
"args": [
"kuzu"
]
}
}
}
Frequently asked questions
EveryPage is categorized under Marketing and uses a local stdio subprocess. Codegraphcontext belongs to Developer Tools and uses a local stdio subprocess. Pick EveryPage for marketing work and Codegraphcontext 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.
EveryPage has no declared pricing — check the project's own site. Codegraphcontext 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 everypage and shashankss1205-codegraphcontext as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EveryPage has a quality signal of 43/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. Codegraphcontext has 59/100 (Good) with 5 views, 0 installs and 4,338 GitHub stars.