cueapi-mcp
Officialcueapi-mcp
CueAPI를 위한 공식 Model Context Protocol 서버입니다. CueAPI는 AI 에이전트를 위한 오픈 소스 실행 책임 원시 요소(execution accountability primitive)입니다.
MCP가 활성화된 어시스턴트(Claude Desktop, Cursor, Zed 또는 기타 MCP 호스트)에게 에이전트 작업 예약, 실행 기록 가져오기, 증거 기반 결과 보고서로 루프 닫기 기능을 대화 내에서 직접 제공하세요.
목적
CueAPI는 에이전트의 조용한 실패를 방지합니다. 모든 예약된 실행은 사이클이 종료되기 전에 외부 ID, 결과 URL 또는 아티팩트와 같은 실제 발생 결과에 대한 증거를 반환해야 합니다. 이 MCP 서버는 해당 원시 요소를 에이전트에게 직접 노출하여, 에이전트가 후속 작업을 스스로 예약하고 증거와 함께 결과를 보고할 수 있도록 합니다.
Related MCP server: moo-tasks
설치
npm install -g @cueapi/mcp
# or use via npx (no install):
npx -y @cueapi/mcp설정 (Claude Desktop)
Claude Desktop 설정 파일(~/Library/Application Support/Claude/claude_desktop_config.json, macOS 기준)에 다음을 추가하세요:
{
"mcpServers": {
"cueapi": {
"command": "npx",
"args": ["-y", "@cueapi/mcp"],
"env": {
"CUEAPI_API_KEY": "cue_sk_..."
}
}
}
}cueapi.ai에서 API 키를 생성하세요. 자체 호스팅을 하시나요? CUEAPI_API_KEY와 함께 CUEAPI_BASE_URL을 설정하세요.
설정 (Cursor / Zed / 기타 호스트)
stdio 서버를 지원하는 모든 MCP 호스트에서 실행할 수 있습니다. 호스트를 cueapi-mcp 바이너리로 지정하고 환경 변수에 CUEAPI_API_KEY를 전달하세요.
노출된 도구
도구 | 기능 |
| 반복(cron) 또는 일회성( |
| 상태별로 필터링하여 큐 목록 조회 |
| 단일 큐에 대한 세부 정보 가져오기 |
| 큐를 일시 중지하여 실행 중단 |
| 일시 중지된 큐 재개 |
| 큐 영구 삭제 |
| 큐/상태별로 필터링하여 과거 실행 목록 조회 |
| 증거(외부 ID / URL)와 함께 일회성 결과 보고 |
대화 예시
사용자: 매일 오전 9시에 내 웹훅으로 요약 정보를 게시하는 작업을 예약해 줘.
어시스턴트 (
cueapi_create_cue사용): 큐cue_abc123이 생성되었습니다. 첫 실행은 내일 오전 9시(UTC)입니다.사용자: 마지막으로 실행된 5번의 기록을 보여줘.
어시스턴트 (
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 홈페이지: https://cueapi.ai
코어 (오픈 소스): https://github.com/cueapi/cueapi-core
Model Context Protocol: https://modelcontextprotocol.io
라이선스
MIT © Vector Apps Inc.
Available Tools
8 toolscueapi_create_cueA
Create a new CueAPI cue — a scheduled job that fires a callback (or enqueues worker work) on a cron or one-time trigger.
Inputs: name (required), cron, at, callback_url, +4 more.
cueapi_delete_cueA
Delete a cue permanently. Irreversible.
Inputs: cue_id (required).
cueapi_get_cueA
Fetch a single cue by ID, including current schedule and most recent execution.
Inputs: cue_id (required).
cueapi_list_cuesC
List cues on the authenticated account, optionally filtered by status.
Inputs: status, limit, offset.
cueapi_list_executionsB
List executions — the historical record of times a cue actually fired. Optionally filter by cue, status, or paginate.
Inputs: cue_id, status, limit, offset.
cueapi_pause_cueA
Pause a cue. Paused cues do not fire until resumed.
Inputs: cue_id (required).
cueapi_report_outcomeA
Report the outcome of an execution. CueAPI's core accountability primitive: attach evidence (external_id, result_url, summary) that proves the work actually happened. Write-once — the outcome record is immutable.
Inputs: execution_id (required), success (required), external_id, result_url, +1 more.
cueapi_resume_cueB
Resume a previously-paused cue.
Inputs: cue_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose targeting specific operations on cues or executions. There is no overlap: create, delete, get, list, pause, resume, list_executions, and report_outcome are all unique actions with well-defined boundaries.
All tools follow a consistent 'cueapi_verb_noun' pattern with snake_case throughout. The naming is predictable and uniform, making it easy to understand each tool's function at a glance.
With 8 tools, the server is well-scoped for managing cues and executions. Each tool earns its place, covering core CRUD operations, lifecycle management (pause/resume), and accountability features without being overwhelming.
The toolset provides complete coverage for the CueAPI domain: full CRUD for cues (create, get, list, delete), lifecycle control (pause/resume), execution tracking (list_executions), and accountability (report_outcome). There are no obvious gaps, enabling agents to handle all typical workflows.
Maintenance
Related MCP Connectors
Hosted MCP server for task-first delegation to remote workstations and workers.
MCP server for CertScore.ai public website risk-signal workflows.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceServer-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what agents must produce — the server blocks the call if they don't. Works with any MCP-compatible client.214MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.16 npm3MIT

Ennodiaofficial
AlicenseAqualityBmaintenanceMCP server that orchestrates multi-agent reviews by running installed agent CLIs, tracking child tasks, and using Compare to produce a traceable recommended answer with receipts.6875 npm6MIT- AlicenseNot gradedqualityNot gradedmaintenanceEnables enterprise agent fleets to register workers, dispatch tasks by capability, monitor continuous heartbeat telemetry, trip automated circuit breakers, and recover from checkpointed state through a zero-dependency MCP server.MIT