Sugra API MCP vs CorpusIQ — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sugra API MCP vs CorpusIQ
In-depth architectural comparison of the Sugra API MCP and CorpusIQ 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
Sugra API MCP
Data Platforms · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
CorpusIQ
Data Platforms · Remote HTTP/SSE
Quality: 75/100 (Great) | Auth: OAuth 2.0
Verdict Summary: Choose Sugra API MCP if you need specialized Data Platforms tools running via a local process. Choose CorpusIQ if your workspace requires Data Platforms integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Sugra API MCP when:
You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
Connector between LLM agents and world data - 1,500+ endpoints aggregating 160+ primary sources across 36 data domains: markets, macroeconomics, company fundamentals, government, news, climate, maritime, and entity screening. Install via pip install sugra-api-mcp or hosted at app.sugra.ai/mcp.
65+ MCP tools for business operations: ecommerce, finance, marketing, and analytics data through one streamable-HTTP endpoint. Built for operators.
Category & Scope
Tools & Capabilities Breakdown
Sugra API MCP Tools (11)
fetch_data
One-step: find best endpoint for a natural-language query and call it. Combines search + call in one round trip.
search_endpoints
Search the bundled endpoint catalog. Runtime search does not fetch `/openapi.json`.
describe_endpoint
Inspect an endpoint by `operation_id`, including path, method, parameters, required inputs, `agent_hints`, and `request_body_schema` for JSON-body POST operations.
call_endpoint
Call a Sugra API operation by `operation_id`. Arbitrary path calls are no longer supported.
list_toolsets
List catalog groups with endpoint counts and descriptions.
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).
Sugra API MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, CorpusIQ belongs to Data Platforms using remote streaming HTTP/SSE transport. Select Sugra API MCP when you need capabilities focused on data platforms and CorpusIQ when you require tools for data platforms.
Screen a name against sanctions and watchlists (Sugra Entity).
sugra_entity_lookup
Composed entity lookup by identifier - `anchor` is `lei` or `vat`, plus the identifier `value`; returns registry identity + screening (Sugra Entity).
resolve_entity
Free text (ticker, company, indicator, coin, currency pair) to a canonical market or macro entity. Ambiguous matches return ranked candidates, never a silent pick.
get_snapshot
Entity plus a named recipe to one composed current view with freshness, provenance, coverage, and billing blocks. Composed calls charge a fixed recipe cost (1-2 requests) from the daily quota.
get_timeseries
Entity plus metric (`price`, `macro_series`, `etf_flows`, `etf_monthly_flows`) to a bounded series with an explicit downsampling flag. `etf_flows` estimates at filing cadence; `etf_monthly_flows` is the fund's own NPORT-P monthly creations and redemptions.