Schedule agent work and report write-once outcomes via CueAPI from any MCP host.
{
"mcpServers": {
"ai-cueapi-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Schedule agent work and report write-once outcomes via CueAPI from any MCP host.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Official Model Context Protocol server for CueAPI — the open-source execution accountability primitive for AI agents.
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.
CueAPI makes silent agent failure impossible: every scheduled run has to come back with evidence of what actually happened — an external ID, a result URL, or an artifact — before the cycle closes. This MCP server exposes that primitive directly to the agent itself, so the agent can both schedule its own follow-up work and report outcomes with proof.
npm install -g @cueapi/mcp
# or use via npx (no install):
npx -y @cueapi/mcp
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.
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.
| Tool | What it does |
|---|---|
cueapi_create_cue | Create a recurring (cron) or one-time (at) cue |
cueapi_list_cues | List cues, filter by status |
cueapi_get_cue | Fetch details for a single cue |
cueapi_pause_cue | Pause a cue so it stops firing |
cueapi_resume_cue | Resume a paused cue |
cueapi_delete_cue | Delete a cue permanently |
cueapi_list_executions | List historical executions, filter by cue/status |
cueapi_report_outcome | Report write-once outcome with evidence (external ID / URL) |
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): ...
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 tsx
cueapi_pause_cue / cueapi_resume_cue to use PATCH /v1/cues/{id} with {"status": "paused" | "active"} (previously called non-existent /pause and /resume endpoints → runtime 404).MIT © Vector Apps Inc.
No automated test available for this server. Check the GitHub README for setup instructions.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationNo known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.
MCP Security Weekly
Get CVE alerts and security updates for ai.cueapi/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.