MCP Server

The Kadoa MCP server gives any compatible AI model or agent a standardized, secure way to work with Kadoa via the Model Context Protocol. It has tools for creating, running, and managing workflows, fetching and exporting extracted data, and configuring notifications, variables, and templates, all through natural language. Kadoa’s MCP server follows the authenticated remote MCP spec, so the server is centrally hosted and managed. For help getting started after setup, see some of our example prompts.

Setup

General

The server is centrally hosted and managed by Kadoa, using Streamable HTTP as its transport. There is nothing to install and no API key to manage. There are two ways to connect:

Personal connection (https://mcp.kadoa.com/mcp): You sign in with your own Kadoa account, and every tool call runs as you, under your role and active team. Best for individual use.
Service connector (https://service.mcp.kadoa.com/mcp): A workspace admin generates OAuth credentials once, and applications or organization members connect as a shared workspace service account, with no Kadoa login. Best for organization-wide rollouts and app contexts where nobody can sign in interactively. See MCP Service Connector →.

	Personal connection	Service connector
Who signs in	Each user	Nobody; OAuth client ID and secret
Acts as	You (your role and team)	Shared workspace service account
Set up by	Each user	A workspace admin, once
Best for	Individual use	Organizations, apps, automations

For a personal connection, add the server in your client: a browser opens so you can sign in with your Kadoa account and grant access. The connection then stays authorized; if a session expires, your client prompts you to sign in again.

With a personal connection, the MCP server acts as you: every tool runs under your Kadoa role and active team, and each action is recorded in the workflow’s history.

Instructions for specific clients follow below.

Claude

Team, Enterprise (Claude.ai) A Claude organization owner can roll Kadoa out to everyone at once: add a custom connector for https://mcp.kadoa.com/mcp under Admin settings → Connectors (members sign in with their own Kadoa accounts), or use the service connector so members connect without Kadoa accounts. Individual members can also add it themselves under Settings → Connectors → Add custom MCP with the same URL. Free, Pro (Claude.ai)

Go to Settings → Connectors → Add custom MCP
Enter the URL: https://mcp.kadoa.com/mcp
Sign in with your Kadoa account via OAuth

Claude Code

claude mcp add kadoa --transport http https://mcp.kadoa.com/mcp

Then run /mcp in a Claude Code session to go through the authentication flow.

Claude Desktop

Add the server to your Claude Desktop config file (create it if it doesn’t exist), then restart Claude Desktop:

// macOS:   ~/Library/Application Support/Claude/claude_desktop_config.json
// Linux:   ~/.config/Claude/claude_desktop_config.json
// Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "kadoa": {
      "type": "http",
      "url": "https://mcp.kadoa.com/mcp"
    }
  }
}

ChatGPT

Go to Settings → Connectors → Add MCP server
Enter the URL: https://mcp.kadoa.com/mcp
Choose OAuth authentication and sign in with your Kadoa account

Codex

codex mcp add kadoa --url https://mcp.kadoa.com/mcp

Then run codex mcp login kadoa to go through the authentication flow. If this is your first remote MCP server in Codex, enable the rmcp client in ~/.codex/config.toml first:

[features]
experimental_use_rmcp_client = true

Cursor

// .cursor/mcp.json
{
  "mcpServers": {
    "kadoa": {
      "type": "http",
      "url": "https://mcp.kadoa.com/mcp"
    }
  }
}

Gemini CLI

gemini mcp add -t http kadoa https://mcp.kadoa.com/mcp

Others

Any MCP-compatible client can connect with the following settings:

URL: https://mcp.kadoa.com/mcp
Transport: Streamable HTTP
Auth: OAuth (sign in with your Kadoa account)

Tools

The tools you can use depend on your team role. Members, Admins, and Owners can use every tool except approve_workflow, which is reserved for Compliance Officers. Viewers and Compliance Officers otherwise have read-only access. If a tool is not available for your role, you’ll receive an error message with instructions to contact your team admin. The columns below show access for the Member / Admin / Owner, Viewer, and Compliance Officer roles.

Workflows

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`create_workflow`	Create an agentic navigation workflow from a prompt
`list_workflows`	List all workflows with status
`get_workflow`	Get detailed workflow information including prompt, schedules, and notification config
`update_workflow`	Update workflow configuration and schema
`delete_workflow`	Delete a workflow
`approve_workflow`	Approve and activate a workflow
`pause_workflow`	Pause an active workflow so it stops running on its schedule
`request_workflow_update`	Ask the Kadoa Assistant to update an existing workflow without replacing it

To find workflows that need action, call list_workflows with statusFilters: ["group:attention"]. It includes workflows waiting for an Assistant answer, unfinished setup, or preview approval.

Kadoa Assistant

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`get_workflow_assistant`	Get Assistant lifecycle state and any pending clarification question
`get_workflow_assistant_timeline`	Read paginated customer-visible Assistant messages and questions
`answer_workflow_assistant_question`	Answer the current clarification question and request resume
`interrupt_workflow_assistant`	Safely interrupt Assistant work without pausing the workflow schedule
`resume_workflow_assistant`	Resume inactive or interrupted Assistant work
`stop_workflow_assistant`	Stop active Assistant work without deleting the workflow
`get_workflow_strategy`	Get the latest customer-safe build strategy when available
`get_workflow_history`	List configuration revision history with field-level diffs

Realtime monitoring

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`create_realtime_monitor`	Create an asynchronous realtime monitor after notification settings are persisted

Runs and extracted data

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`list_workflow_runs`	List execution run history; filter by outcome and paginate
`run_workflow`	Execute a workflow
`fetch_data`	Get extracted data from a workflow (paginated, with filters and sorting)
`export_data`	Export the full extracted dataset as a signed URL, ideal for large workflows

Detected changes

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`list_changes`	List detected data changes across real-time monitoring workflows
`get_change`	Get detailed information about a specific detected change

Notifications

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`list_notification_channels`	List notification channels for a workflow or workspace
`create_notification_channel`	Create an email, webhook, Slack, or WebSocket notification channel
`delete_notification_channel`	Delete a notification channel
`list_notification_settings`	List event-to-channel notification mappings
`configure_notifications`	Set up notifications for workflow events in one step
`delete_notification_setting`	Remove a notification event-to-channel mapping

Teams and identity

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`whoami`	Show current user details and team memberships
`team_list`	List all teams you belong to and see which is active
`team_switch`	Switch the active team by name or ID

whoami identifies the current account and team. In Kadoa Assistant sessions, it reports the selected team by name and role rather than an internal identifier.

Activity

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`list_activity`	List team-wide Activity Log events, with filters and optional change details

Use list_activity to answer team-wide questions such as who changed a workflow, which workflows failed, or what happened this week. Events are newest first. Filter by time, workflow, user, event type, resource type, or interface. Use get_workflow_history instead when you need configuration revisions and field-level diffs for one workflow.

Observability

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`get_observability`	Get workflow health, throughput, recovery, and attention items for the active team

get_observability reports a 30-day window by default. Ask for a shorter or longer window when you need it, up to 365 days. It returns a ranked attention list for down and degraded workflows. Add includeWorkflows or includeDailySeries only when you need the larger result.

Usage

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`get_usage`	Get current workflow slots, extracted rows, billing-period details, and billable workflows
`get_usage_history`	Get daily workflow-slot, billing-period, or activity history

Use get_usage for current plan usage and renewal details. Use get_usage_history for trends. Both tools use the active team by default. Organization scope is available only when the active team belongs to an organization. Billing-period values reset at renewal; active workflow slots do not.

Variables

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`create_variable`	Create a key-value variable (STRING, NUMBER, BOOLEAN, or JSON)
`list_variables`	List all variables in the current team scope
`get_variable`	Get a specific variable by ID
`update_variable`	Update a variable’s key, value, or data type
`delete_variable`	Delete a variable (two-step confirmation)

Templates

Tool	Description	Member / Admin / Owner	Viewer	Compliance Officer
`list_templates`	List all templates in the current team
`get_template`	Get a template by ID, including all published versions
`create_template`	Create a reusable template for workflow configurations
`update_template`	Update a template’s name or description
`delete_template`	Delete a template (two-step confirmation)
`create_template_version`	Publish a version with prompt, schema, and notifications
`save_workflow_as_template`	Create a template from an existing workflow’s configuration
`list_template_schemas`	List schemas associated with a template
`link_template_to_workflows`	Link existing workflows to a template
`apply_template_version`	Roll out a template version to linked workflows
`list_template_workflows`	List workflows linked to a template
`unlink_template_from_workflows`	Unlink workflows from a template, keeping their configuration

The status field returned by list_workflows and get_workflow shows the computed workflow status, such as Complete, Running, Failed, Paused, or Scheduled. The tool’s state filter uses these computed status values rather than the API response’s persisted state field.

Scheduling

The create_workflow tool accepts an interval parameter for recurring extractions (defaults to ONLY_ONCE). Use CUSTOM with cron expressions for fine-grained control. See Scheduling → for all available intervals and examples.

Fetching and exporting data

Two tools retrieve extracted data: use fetch_data for paginated reads (default 50 rows, max 500) with filters, sortBy, and order; use export_data for the full dataset. It returns a self-authenticating signed URL ideal for Claude for Excel (‘Get Data from Web’) or pandas/duckdb code execution.

Workflow history

get_workflow_history returns configuration revision history: who changed a workflow and which fields changed. list_workflow_runs is different: it returns execution outcomes, timing, record counts, and errors. Use its status filter (success, failed, or in_progress) and pagination when diagnosing runs.

Updating workflows with the Assistant

Use request_workflow_update to change an existing workflow in place. Then use get_workflow_assistant to inspect lifecycle state and any pending question. Answer a pending question with answer_workflow_assistant_question; do not use resume_workflow_assistant for a question that still needs an answer. Interrupt, resume, and stop control Assistant work, not the workflow schedule. create_realtime_monitor is asynchronous and requires at least one notification channel. It returns the workflow, session, thread, and job IDs for follow-up. See Kadoa Assistant for the full lifecycle.

Common use cases

Once connected, you manage the full workflow lifecycle through natural conversation. Copy an example prompt into your client to explore what’s possible; see the tools above for the full surface:

Build and run a scraper

Create a workflow that extracts product name, price, and rating from https://sandbox.kadoa.com/ecommerce, run it, and show me the first results.

Scheduled monitoring

Set up a workflow that scrapes competitor prices from https://sandbox.kadoa.com/ecommerce daily at 6:00, and email me when a run finishes or fails.

Change detection review

Show me all changes my real-time monitors detected this week and summarize what moved.

Data export and analysis

Export the full ‘Product Monitor’ dataset and analyze price trends by category.

Workflow maintenance

Update the ‘Product Monitor’ schema to add a rating field, then pause the old ‘Legacy Scraper’ workflow.

Assistant follow-up

My Product Monitor is waiting for a question. Show me what it needs, then answer it: use the US store.

Template rollouts

Save ‘Product Monitor’ as a template called ‘Product Scraper’, then create a workflow from it for each of these five store URLs.

Workspace health and usage

Which workflows need attention, how many workflow slots are in use, and what changed across my team this week?

Team administration

List my teams, switch to Acme Corp, and show me which workflows are failing there.

Changing a template

A published template version is an immutable snapshot. To change shared prompt, schema, validation, notifications, or frequency, create a new version and apply it to the workflows that should adopt it. update_template changes only a template’s name or description. See Templates for the rollout flow.

Troubleshooting

I don’t have access to Kadoa

Verify the MCP server is configured in the correct config file
Restart your MCP client after configuration changes
Re-authenticate via OAuth if prompted

Authentication failed

Your OAuth session may have expired, so re-authenticate when prompted by your MCP client
If switching teams, verify the team exists with team_list before using team_switch

`update_workflow` returns “No approval received”

This message comes from your MCP client, not from Kadoa. Claude (and some other clients) gate certain tool calls behind a one-time approval prompt, and update_workflow is often the first tool in a session to hit it. The call never reaches the Kadoa MCP server, so nothing on the Kadoa side (roles, team permissions, API access) is involved.

Retry the call. The gate usually clears for the rest of the session after the first prompt.
If it persists, look for an approval prompt in your client and click through it, or set the Kadoa connector’s tools to “Always allow” in your client’s connector settings.
Read-only tools (get_workflow, fetch_data) and other write tools (run_workflow, delete_workflow) are not affected, so if those work and only update_workflow fails, this is the cause.

Foundations

Security & Compliance

Build with UI

Build with Code

Integrations

Setup

General

Claude

Claude Code

Claude Desktop

ChatGPT

Codex

Cursor

Gemini CLI

Others

Tools

Workflows

Kadoa Assistant

Realtime monitoring

Runs and extracted data

Detected changes

Notifications

Teams and identity

Activity

Observability

Usage

Variables

Templates

Scheduling

Fetching and exporting data

Workflow history

Updating workflows with the Assistant

Common use cases

Changing a template

Troubleshooting

I don’t have access to Kadoa

Authentication failed

`update_workflow` returns “No approval received”

​Setup

​General

​Claude

​Claude Code

​Claude Desktop

​ChatGPT

​Codex

​Cursor

​Gemini CLI

​Others

​Tools

​Workflows

​Kadoa Assistant

​Realtime monitoring

​Runs and extracted data

​Detected changes

​Notifications

​Teams and identity

​Activity

​Observability

​Usage

​Variables

​Templates

​Scheduling

​Fetching and exporting data

​Workflow history

​Updating workflows with the Assistant

​Common use cases

​Changing a template

​Troubleshooting

​I don’t have access to Kadoa

​Authentication failed

​update_workflow returns “No approval received”

Setup

General

Claude

Claude Code

Claude Desktop

ChatGPT

Codex

Cursor

Gemini CLI

Others

Tools

Workflows

Kadoa Assistant

Realtime monitoring

Runs and extracted data

Detected changes

Notifications

Teams and identity

Activity

Observability

Usage

Variables

Templates

Scheduling

Fetching and exporting data

Workflow history

Updating workflows with the Assistant

Common use cases

Changing a template

Troubleshooting

I don’t have access to Kadoa

Authentication failed

`update_workflow` returns “No approval received”