CueAPI MCP Server for Claude

Overview

CueAPI is an open coordination layer for multi-step agent work. The official cueapi/cueapi-mcp package exposes CueAPI as a stdio Model Context Protocol server so hosts like Claude Desktop, Cursor, and Zed can schedule cues, inspect executions, claim worker jobs, and report evidence-backed outcomes from chat.

CueAPI closes handoffs with structured proof—external IDs, result URLs, or artifacts—so silent failures are easier to detect across long-running workflows.

Features

• Create recurring cron cues or one-time at schedules.
• List, pause, resume, update, fire, and delete cues.
• List and fetch execution history with state and outcomes.
• Claim executions individually or claim-next with optional task filters.
• Send execution heartbeats to extend worker leases.
• Report write-once outcomes with verifiable evidence.

Use Cases

• Schedule a daily digest webhook without maintaining a separate cron service.
• Claim the next available worker execution from an MCP-hosted agent session.
• Fire an ad-hoc cue with a payload override for a one-shot integration test.
• Inspect the last five runs of a production cue before changing its schedule.
• Report an outcome URL after an external job completes.

Installation

npm global install

npm install -g @cueapi/mcp

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "cueapi": {
      "command": "npx",
      "args": ["-y", "@cueapi/mcp"],
      "env": {
        "CUEAPI_API_KEY": "cue_sk_..."
      }
    }
  }
}

Claude Code

claude mcp add cueapi --env CUEAPI_API_KEY=cue_sk_YOUR_KEY -- npx -y @cueapi/mcp

Restart the host after updating MCP configuration.

Configuration

{
  "mcpServers": {
    "cueapi": {
      "command": "npx",
      "args": ["-y", "@cueapi/mcp"],
      "env": {
        "CUEAPI_API_KEY": "cue_sk_YOUR_KEY",
        "CUEAPI_BASE_URL": "https://api.cueapi.ai"
      },
      "type": "stdio"
    }
  }
}

Set CUEAPI_BASE_URL only when pointing at a self-hosted CueAPI core deployment.

Examples

Schedule a daily cue

Create a CueAPI cron cue that fires every weekday at 09:00 UTC and posts to my webhook.

Inspect executions

List the last five executions for cue_abc123 and summarize failures.

Claim and report

Claim the next available execution for task_name=data-sync, process it, then report the outcome URL.

Security

• Treat cue_sk_* keys like production credentials; rotate them if exposed.
• Confirm callback URLs before firing cues that dispatch to external webhooks.
• Use heartbeats during long-running claims so another worker cannot steal the lease unexpectedly.

Troubleshooting

Invalid API key

Generate a fresh cue_sk_* key at cueapi.ai and update the MCP env block.

404 on pause or resume older docs

Current tools use PATCH /v1/cues/{id} with status paused or active; upgrade @cueapi/mcp if you run an old release.

Claim starvation

Prefer cueapi_list_claimable_executions with server-side task or agent filters instead of client-side filtering.

Self-hosted connection errors

Set CUEAPI_BASE_URL to your core API origin and verify TLS or VPN reachability from the MCP host.