API.market MCP Gateway vs Project Context MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
API.market MCP Gateway vs Project Context MCP
In-depth architectural comparison of the API.market MCP Gateway and Project Context MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
API.market MCP Gateway
Developer Tools · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: OAuth 2.0
Project Context MCP
Developer Tools · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose API.market MCP Gateway if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Project Context MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
A
Choose API.market MCP Gateway when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
Proprietary hosted Streamable HTTP MCP gateway for API discovery, operation schemas, API calls, usage checks and subscription management through five tools: search_apis, get_api_tools, call_api, check_usage and manage_subscription. Requires an API.market account with OAuth (recommended) or API-key authentication. Free tiers, paid plans and limits vary by API; API calls and subscription changes may incur charges. OAuth/PKCE and five-tool discovery verified with Claude Code 2.1.281; not every API operation or client has been tested. The public integration repository contains configuration and documentation, not the hosted server implementation. Connect directly to https://api.market/api/mcp/gateway; no local package is required.
Exposes .context/ folder files as MCP resources, giving Claude Code instant access to project documentation via @ mentions.
Tools & Capabilities Breakdown
API.market MCP Gateway Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Project Context MCP Tools (6)
Recursive .context/ file discovery
MCP resource exposure
Claude Code @ mention selection
Automatic resource names and descriptions
Nested folder support
context:// resource URIs
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
API.market MCP Gateway is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Project Context MCP belongs to Developer Tools using local stdio subprocess. Select API.market MCP Gateway when you need capabilities focused on developer tools and Project Context MCP when you require tools for developer tools.