Catalogapi vs Codegraphcontext
A side-by-side look at the Catalogapi 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 Catalogapi for e-commerce work over a hosted endpoint; 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 Catalogapi when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_coverage, search_rewards, get_reward_details.
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 | E-Commerce | Developer Tools |
| Quality signal | 48/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 4,349 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Catalogapi | View Codegraphcontext |
Tools & capabilities
Catalogapi tools 4
check_coverageWhich countries are covered, and which categories are available in eachsearch_rewardsExample items from a demonstration catalog for one countryget_reward_detailsDetail for a single catalog itemhow_it_worksAnswers about the service itself: coverage, fulfillment, pricing, integration
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.
Catalogapi
{
"mcpServers": {
"catalogapi-2": {
"url": "https://api.catalogapi.com"
}
}
}
Codegraphcontext
{
"mcpServers": {
"shashankss1205-codegraphcontext": {
"command": "uvx",
"args": [
"kuzu"
]
}
}
}
Frequently asked questions
Catalogapi is categorized under E-Commerce and uses a remote HTTP/SSE transport. Codegraphcontext belongs to Developer Tools and uses a local stdio subprocess. Pick Catalogapi for e-commerce 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.
Catalogapi 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 catalogapi-2 and shashankss1205-codegraphcontext as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Catalogapi has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Codegraphcontext has 59/100 (Good) with 5 views, 0 installs and 4,349 GitHub stars.
