cueapi-mcp
OfficialThis server connects MCP-enabled AI assistants to CueAPI, allowing them to schedule, manage, and track agent tasks with structured evidence of outcomes.
Create cues (
cueapi_create_cue): Schedule recurring (cron) or one-time (at) jobs with optional webhook callbacks, worker transport mode, custom JSON payloads, timezone, and description.List cues (
cueapi_list_cues): Retrieve all cues, with optional filtering by status (active/paused) and pagination.Get cue details (
cueapi_get_cue): Fetch a single cue's full configuration and most recent execution info by ID.Fire on demand: Trigger a cue immediately with an optional payload override.
Update cues: Modify mutable fields such as name, schedule, callback URL, and payload.
Pause/resume cues (
cueapi_pause_cue/cueapi_resume_cue): Temporarily stop or restart a cue without deleting it.Delete cues (
cueapi_delete_cue): Permanently remove a cue.List executions (
cueapi_list_executions): View historical execution records, filterable by cue ID or status, with pagination.Get execution details: Fetch a specific execution's state and outcome.
Claim executions: Atomically claim outstanding worker executions for processing (list claimable, claim by ID, or claim the next available).
Heartbeat: Extend the claim lease on an in-flight execution.
Report outcomes (
cueapi_report_outcome): Attach immutable, evidence-backed records to executions (success/failure, summary, external ID, result URL) to prove work actually happened.
cueapi-mcp
Official Model Context Protocol server for CueAPI, the open-source coordination layer for AI agent systems.
Give your MCP-enabled assistant (Claude Desktop, Cursor, Zed, or any other MCP host) the ability to schedule agent work, fetch execution history, and close the loop with evidence-backed outcome reports, all from inside a conversation.
Why
Agents don't finish in one call. They coordinate across time, tools, environments, agents, and humans. Every handoff is a place where silent failure hides. CueAPI closes each handoff with structured evidence: an external ID, a result URL, or an artifact. This MCP server gives the agent direct access to that surface, so the agent can both schedule its own follow-up work and report outcomes with proof.
Install
npm install -g @cueapi/mcp
# or use via npx (no install):
npx -y @cueapi/mcpConfigure (Claude Desktop)
Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"cueapi": {
"command": "npx",
"args": ["-y", "@cueapi/mcp"],
"env": {
"CUEAPI_API_KEY": "cue_sk_..."
}
}
}
}Generate your API key at cueapi.ai. Self-hosting? Set CUEAPI_BASE_URL alongside CUEAPI_API_KEY.
Configure (Cursor / Zed / other hosts)
Any MCP host that supports stdio servers can run this. Point the host at the cueapi-mcp binary and pass CUEAPI_API_KEY in the environment.
Tools exposed
Tool | What it does |
| Create a recurring (cron) or one-time ( |
| List cues, filter by status |
| Fetch details for a single cue |
| Fire an existing cue immediately, optional payload override |
| Update a cue's mutable fields (name, schedule, callback, payload, etc.) |
| Pause a cue so it stops firing |
| Resume a paused cue |
| Delete a cue permanently |
| List historical executions, filter by cue/status |
| Fetch a single execution by ID, with state + outcome |
| List unclaimed worker executions, filter server-side by task/agent |
| Atomically claim a specific execution for processing |
| Claim the next available execution (optional task filter) |
| Extend the claim lease on an in-flight execution |
| Report write-once outcome with evidence (external ID / URL) |
Example conversation
You: Schedule a daily 9am job that posts a digest to my webhook.
Assistant (uses
cueapi_create_cue): Created cuecue_abc123, first fire tomorrow at 9:00 UTC.You: Show me the last five times it ran.
Assistant (uses
cueapi_list_executions): ...
Development
npm install
npm test # vitest smoke tests for the tool surface
npm run build # compile TypeScript to dist/
npm run dev # run the server locally with tsxLinks
CueAPI homepage: https://cueapi.ai
Docs: https://docs.cueapi.ai
Core (open source): https://github.com/cueapi/cueapi-core
Model Context Protocol: https://modelcontextprotocol.io
Changelog
0.4.1. Add
cueapi_update_cuetool: update a cue's mutable fields (name, schedule, callback URL, timezone, payload, description). WrapsPATCH /v1/cues/{id}. Sparse update — only provided fields are sent. Closes the cross-wrapper parity gap (every other client wrapper exposed update; MCP didn't until now).0.4.0. Add five execution-lifecycle tools —
cueapi_get_execution,cueapi_list_claimable_executions,cueapi_claim_execution,cueapi_claim_next_execution,cueapi_execution_heartbeat. Closes the receive-claim-process-complete loop for MCP-host agents that want to consume worker-transport executions from in-session (e.g. Claude Desktop, Cursor, Zed). Highlights:list_claimable_executionsfilters server-side viatask/agentquery params (client-side filtering hits a known LIMIT-50 starvation bug);claim_next_executionaccepts an optionaltask_nameand internally fans out (filtered list → pick oldest → claim by ID) since the server doesn't yet support a task filter on the bare claim endpoint;execution_heartbeatsendsworker_idvia theX-Worker-Idrequest header (the server's transport for that field) and requires it in the schema so misconfigured callers fail at the wrapper instead of silently bypassing race protection. Internal:CueAPIClient.request()gains an optionalextraHeadersparameter to support per-call custom headers.0.3.0. Add
cueapi_fire_cuetool: fire an existing cue immediately with an optionalpayload_override(andmerge_strategy: 'merge' | 'replace', default'merge'). WrapsPOST /v1/cues/{id}/fire. Lets agents trigger ad-hoc one-shot executions without creating throwaway cues, and lets per-fire dynamic data flow through to webhook dispatch + worker-claim responses without mutating the stored cue.0.1.4. Fix
cueapi_pause_cue/cueapi_resume_cueto usePATCH /v1/cues/{id}with{"status": "paused" | "active"}(previously called non-existent/pauseand/resumeendpoints, returning a runtime 404). PR #1. This is the release that actually contains the fix; 0.1.3 was published prematurely with this note but without the merged code.0.1.3. Premature publish, superseded by 0.1.4. No functional changes from 0.1.2.
0.1.2. Register with the Official MCP Registry.
0.1.0. Initial release: 8 tools for create / list / get / pause / resume / delete cues, list executions, report outcome.
License
MIT © Vector Apps Inc.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cueapi/cueapi-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server