CorpusIQ vs Jitsu

A side-by-side look at the CorpusIQ and Jitsu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

CorpusIQ logoCorpusIQData Platforms · Remote HTTP/SSE65+ MCP tools for business operations: ecommerce, finance, marketing, and analytics data through one streamable-HTTP endpoint. Built for operators.83ExcellentAuth: oauth 2.0Jitsu logoJitsuData PlatformsManage Jitsu data pipelines: destinations, streams, connections, functions, live events.41FairAuth: not declared

Verdict: choose CorpusIQ for data platforms work over a hosted endpoint; choose Jitsu for data platforms. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

CorpusIQ logoChoose CorpusIQ when

  • You need dedicated capabilities in the Data Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like get_connector_status, resolve_connector, ask_corpusiq.
Explore CorpusIQ

Jitsu logoChoose Jitsu when

  • You need dedicated capabilities in the Data Platforms domain.
Explore Jitsu

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCorpusIQ logoCorpusIQJitsu logoJitsu
CategoryData PlatformsData Platforms
Quality signal83/100 · Excellent41/100 · Fair
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthOAuth 2.0Not declared
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars245,109
Directory activity 19 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools121Not listed

Tools & capabilities

CorpusIQ tools 121

  • get_connector_statusReturn a pre-formatted Markdown dashboard showing every configured connector's status. IMPORTANT: The output is a complete, ready-to-display Markdown table — show it to the user exactly as returned, do NOT summarize or paraphrase. Each row includes connector name, provider, connection status (with emoji indicators), and a clickable link to authenticate if needed. After displaying the table, offer to help the user connect any unauthorized services and mention they can say 'refresh status' after authenticating.
  • resolve_connectorDiscover how to answer the user's data question. ALWAYS call this FIRST for any data-related request. For broad questions — business health, performance, growth, financial pulse, recap, 'how are we doing', 'what should I focus on', or any cross-source question — the response returns a CorpusIQ Skill in `skill.skill_body`: a pre-built runbook you should execute step-by-step, honoring any presentation rules it specifies. For narrow single-source questions, the response returns 2-4 ready-to-call tool schemas. The `supporting_actions` list is available as helpers when a skill is attached — do not call them ahead of the runbook. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it.
  • ask_corpusiqAnswer a business question through CorpusIQ's deterministic server-side runbook executor. In router_first mode, CorpusIQ selects and pins the best matching runbook before validating connectors and executing its fixed read-only tool allowlist. In required_runbook mode, the caller pins an explicit runbook id. Returns the answer, source evidence, warnings, and a verifiable execution receipt; unsupported runbooks and missing prerequisites fail closed. Use this for supported executive financial-health or financial snapshot workflows even when the user names QuickBooks or another single service. Use raw connector tools for simple lookups that are not executive workflows. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • select_runbookUse this FIRST for broad executive/business questions such as 'How healthy is my business?', 'How are we doing?', 'What should I focus on?', or 'Give me an executive summary'. Selects the best CorpusIQ runbook and returns the next step. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • list_runbooksBrowse a compact list of CorpusIQ runbooks/skills. Do not use this to choose a runbook for a user's broad question; call select_runbook first so the canonical semantic router can choose without sending the full catalog to the model. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • run_runbookRun a specific CorpusIQ runbook by id. By default this returns the playbook (`skill_body`) for client-side execution. Set execution_mode=server_side for the bounded executive-snapshot pilot; unsupported runbooks fail closed. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • list_skillsBrowse a compact list of CorpusIQ Skills (cross-source runbooks). Do not use this to discover the best skill for a broad user question; call select_runbook first so Haiku can classify without sending the full skills catalog to the model. Use list_skills only when the user explicitly asks to browse available skills. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • invoke_skillFetch a named CorpusIQ Skill runbook by id. IMPORTANT: this returns a PLAYBOOK (a step-by-step runbook), NOT the final answer. The response carries `status: runbook_returned`, `next_step: execute_runbook`, and `skill_body` with the ordered steps to execute. After receiving the runbook you MUST call the connector tools/actions it references to gather data, then synthesize a response for the user honoring any presentation rules in the runbook. Never present the raw runbook text to the user as the answer. The user's CorpusIQ identity is forwarded automatically; no separate authentication is required. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • cross_source_ads_connectorCross-source analysis correlating Google Ads spend with GA4 web traffic and revenue. Use when comparing ad spend to sessions, conversions, or ROAS across platforms. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • cross_source_email_connectorCross-source analysis correlating Klaviyo email activity with web traffic, ecommerce revenue, and ad spend. Use for channel attribution, email-driven revenue, and unified marketing analytics. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • canonical_context_getRead the user's declared CorpusIQ canonical facts, recent decisions, and declared metric specs. Use at the start of business, product, pricing, company, positioning, board, investor, factual, OR KPI/metric questions when stable user-approved truth may matter. This is read-only and returns only content the user deliberately saved. If declared metric specs are returned, prefer calling metric_spec_resolve(key=...) over computing the same KPI from raw connector tool calls. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • canonical_facts_getGet one declared canonical business fact by key. Read-only. Use when the user asks for a stored fact such as pricing, connector count, tagline, team detail, certification, or product fact. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.
  • +109 more on the listing page

Jitsu 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.

CorpusIQ

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "corpusiq": {
      "url": "https://mcp2.corpusiq.io/mcp"
    }
  }
}

Jitsu

No confirmed install command for Jitsu yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

CorpusIQ is categorized under Data Platforms and uses a remote HTTP/SSE transport. Jitsu belongs to Data Platforms and uses an install path we have not confirmed yet. Pick CorpusIQ for data platforms work and Jitsu for data platforms.

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. Jitsu has no confirmed install command yet — follow its own setup instructions.

CorpusIQ is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Jitsu has no declared pricing — check the project's own site. 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 corpusiq and jitsu as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, CorpusIQ has a quality signal of 83/100 (Excellent) with 19 views, 0 installs and 24 GitHub stars. Jitsu has 41/100 (Fair) with 1 views, 0 installs and 5,109 GitHub stars.