LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

CorpusIQ Runbook Executor

123 tools built around runbooks: pick one for the question, run it server-side, and get a deterministic answer across connected sources.

by CorpusIQ ↗Data Platform: Pipelines, Warehousing, BI & Governance✓ Official

LABSCO SUMMARY

Deterministic runbooks are a direct answer to the thing that makes agent analytics untrustworthy.

Ask a model to compute business health from five data sources and it will improvise a method, differently each time. CorpusIQ's answer is to make the method a stored artefact — a runbook with an id — and execute it server-side, so the same question gives the same answer for the same reason. The tool descriptions enforce the pattern, telling the client which call must come first. The cost is the length of that tool list; the discovery-first design is presumably why that is bearable.

What it is

CorpusIQ's hosted endpoint, which identifies itself as multi-source-mcp. The design is unusual: rather than exposing raw data tools, it routes questions to server-side runbooks that execute deterministically.

What you get

  • resolve_connector — the documented first call for any data question: work out how it can be answered
  • select_runbook — for broad business questions, pick the runbook that fits before running anything
  • list_runbooks and run_runbook — browse the catalogue, then execute one by id with arguments and a date range
  • ask_corpusiq — a business question answered through the deterministic runbook executor
  • get_connector_status — a formatted dashboard of every configured connector
  • And the rest, covering the individual connected sources

Requirements

A CorpusIQ account, with every connector you want to use authorized first in its dashboard. ChatGPT, Claude and Perplexity sign in through a browser OAuth window, and CLI tools and agents use device login, sending the token as an Authorization Bearer header.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen