Der CorpusIQ MCP-Server,
verbunden mit einem Klick.

“Nutze „get_connector_status“: Return a pre-formatted Markdown dashboard showing every configured connector's status. IMPORTANT: The output is a complete, ready-to-display.”

“Nutze „resolve_connector“: Discover how to answer the user's data question. ALWAYS call this FIRST for any data-related request. For broad questions — business health,.”

“Nutze „ask_corpusiq“: Answer a business question through CorpusIQ's deterministic server-side runbook executor. In router_first mode, CorpusIQ selects and pins th.”

“Nutze „select_runbook“: Use this FIRST for broad executive/business questions such as 'How healthy is my business?', 'How are we doing?', 'What should I focus on?',.”

get_connector_status — Return a pre-formatted Markdown dashboard showing every configured connector's status. IMPORTANT: The output is a complete, ready-to-display

resolve_connector — Discover how to answer the user's data question. ALWAYS call this FIRST for any data-related request. For broad questions — business health,

ask_corpusiq — Answer a business question through CorpusIQ's deterministic server-side runbook executor. In router_first mode, CorpusIQ selects and pins th

select_runbook — Use this FIRST for broad executive/business questions such as 'How healthy is my business?', 'How are we doing?', 'What should I focus on?',

list_runbooks — Browse a compact list of CorpusIQ runbooks/skills. Do not use this to choose a runbook for a user's broad question; call select_runbook firs

run_runbook — Run a specific CorpusIQ runbook by id. By default this returns the playbook (`skill_body`) for client-side execution. Set execution_mode=ser

list_skills — Browse a compact list of CorpusIQ Skills (cross-source runbooks). Do not use this to discover the best skill for a broad user question; call

invoke_skill — Fetch a named CorpusIQ Skill runbook by id. IMPORTANT: this returns a PLAYBOOK (a step-by-step runbook), NOT the final answer. The response