CueAPI MCP server
✓ VerifiedMemungkinkan AI agent untuk menjadwalkan tugas berulang atau satu kali, mengelola riwayat eksekusi, dan melaporkan hasil dengan bukti terstruktur.
Juga dikenal sebagai cueapi/cueapi-mcp, cueapi-mcp, @cueapi/mcp
- Stars
- 2
- Tools
- 15
- Unduhan, 30 hari
- 282
- Versi terbaru
- 0.1.3
- Commit terakhir
- 3 Agu 2026
- Lisensi
- MIT
Apa itu CueAPI MCP?
CueAPI adalah MCP server. Memungkinkan AI agent untuk menjadwalkan tugas berulang atau satu kali, mengelola riwayat eksekusi, dan melaporkan hasil dengan bukti terstruktur. Server ini menyediakan 15 tool, seperti cueapi_create_cue, cueapi_list_cues, cueapi_get_cue.
Ringkasan dibuat dari README proyek
Tentang CueAPI MCP server
Server ini memungkinkan Anda untuk menjadwalkan tugas agent yang berulang dan mengelola riwayat eksekusi langsung dari dalam AI assistant. Server ini menyediakan lapisan koordinasi bagi agent yang menggunakan Claude Desktop, Cursor, atau Zed untuk menangani pekerjaan yang berlangsung melintasi waktu dan berbagai lingkungan berbeda. Dengan menggunakan server ini, seorang agent dapat membuat jadwal berbasis cron atau satu kali, melacak riwayat eksekusi, dan melaporkan hasil yang telah selesai menggunakan bukti terstruktur seperti URL atau ID eksternal.
Pengguna terhubung ke layanan ini dengan menginstal package melalui npm dan mengonfigurasi MCP host mereka dengan CUEAPI_API_KEY. Bagi Anda yang melakukan self-hosting, CUEAPI_BASE_URL juga dapat ditentukan. Toolset ini mencakup perintah spesifik untuk seluruh siklus hidup tugas, seperti cueapi_create_cue untuk penjadwalan, cueapi_claim_execution untuk mengambil pekerjaan yang tertunda, dan cueapi_report_outcome untuk memberikan bukti penyelesaian. Hal ini memungkinkan agent untuk mengelola serah terima yang kompleks dan memastikan bahwa kegagalan yang tidak terdeteksi dapat ditemukan melalui hasil yang terdokumentasi.
Apa yang bisa Anda lakukan dengannya
- 1Menjadwalkan workflow agent yang berulangSeorang agent dapat mengatur tugas harian untuk mengirim data ke webhook tertentu.
- 2Memantau riwayat eksekusi tugasSeorang developer dapat meminta assistant mereka untuk meninjau hasil eksekusi sebelumnya dari sebuah job yang dijadwalkan.
- 3Mengambil dan memproses tugas yang tertundaAI agent dapat mengambil eksekusi worker yang tersedia untuk menjalankan tugas-tugas spesifik.
- 4Memberikan bukti untuk pekerjaan yang telah selesaiSeorang agent dapat menutup loop tugas dengan mengirimkan URL hasil sebagai bukti keberhasilan.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal CueAPI MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal CueAPI MCP di Claude Code
$ claude mcp add --env 'CUEAPI_API_KEY=<YOUR_CUEAPI_API_KEY>' cueapi-mcp -- npx -y @cueapi/mcpInstal CueAPI MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cueapi-mcp": {
"command": "npx",
"args": [
"-y",
"@cueapi/mcp"
],
"env": {
"CUEAPI_API_KEY": "<YOUR_CUEAPI_API_KEY>"
}
}
}
}Instal CueAPI MCP di VS Code
.vscode/mcp.json
{
"servers": {
"cueapi-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cueapi/mcp"
],
"env": {
"CUEAPI_API_KEY": "<YOUR_CUEAPI_API_KEY>"
}
}
}
}Instal CueAPI MCP di VS Code CLI
$ code --add-mcp '{"name":"cueapi-mcp","type":"stdio","command":"npx","args":["-y","@cueapi/mcp"],"env":{"CUEAPI_API_KEY":"<YOUR_CUEAPI_API_KEY>"}}'Instal CueAPI MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"cueapi-mcp": {
"command": "npx",
"args": [
"-y",
"@cueapi/mcp"
],
"env": {
"CUEAPI_API_KEY": "<YOUR_CUEAPI_API_KEY>"
}
}
}
}Instal CueAPI MCP di Codex
$ codex mcp add cueapi-mcp --env 'CUEAPI_API_KEY=<YOUR_CUEAPI_API_KEY>' -- npx -y @cueapi/mcpInstal CueAPI MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.cueapi-mcp] command = "npx" args = ["-y", "@cueapi/mcp"] [mcp_servers.cueapi-mcp.env] CUEAPI_API_KEY = "<YOUR_CUEAPI_API_KEY>"
Instal CueAPI MCP di Gemini CLI
$ gemini mcp add -s user -e 'CUEAPI_API_KEY=<YOUR_CUEAPI_API_KEY>' cueapi-mcp npx -- -y @cueapi/mcpInstal CueAPI MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cueapi-mcp": {
"command": "npx",
"args": [
"-y",
"@cueapi/mcp"
],
"env": {
"CUEAPI_API_KEY": "<YOUR_CUEAPI_API_KEY>"
}
}
}
}Tool CueAPI MCP 15
Terdeteksi dari READMEcueapi_create_cuecueapi_list_cuescueapi_get_cuecueapi_fire_cuecueapi_update_cuecueapi_pause_cuecueapi_resume_cuecueapi_delete_cuecueapi_list_executionscueapi_get_executioncueapi_list_claimable_executionscueapi_claim_execution
| cueapi_create_cue | — | |
| cueapi_list_cues | — | |
| cueapi_get_cue | — | |
| cueapi_fire_cue | — | |
| cueapi_update_cue | — | |
| cueapi_pause_cue | — | |
| cueapi_resume_cue | — | |
| cueapi_delete_cue | — | |
| cueapi_list_executions | — | |
| cueapi_get_execution | — | |
| cueapi_list_claimable_executions | — | |
| cueapi_claim_execution | — |
Tampilkan semua 15 toolTampilkan lebih sedikit tool
cueapi_claim_next_executioncueapi_execution_heartbeatcueapi_report_outcome
| cueapi_claim_next_execution | — | |
| cueapi_execution_heartbeat | — | |
| cueapi_report_outcome | — |
Konfigurasi
CUEAPI_API_KEYWajibRahasiaCueAPI API key. Generate at https://cueapi.ai
CUEAPI_BASE_URLOverride the CueAPI base URL for self-hosted instances. Defaults to https://api.cueapi.ai
| Nama | Deskripsi | Tipe |
|---|---|---|
| CUEAPI_API_KEY | CueAPI API key. Generate at https://cueapi.ai | WajibRahasia |
| CUEAPI_BASE_URL | Override the CueAPI base URL for self-hosted instances. Defaults to https://api.cueapi.ai |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkaucueapi/cueapi-mcp is public and reachablegithub.com/cueapi/cueapi-mcp ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernya@cueapi/mcp names cueapi/cueapi-mcp as sourcenpmjs.com/package/@cueapi/mcp ↗Lolos
- Provenance build (atestasi Sigstore)No build attestation published for this releaseTidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-08-03github.com/cueapi/cueapi-mcp ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from @cueapi/mcpLolos
- Tidak ada advisory kritis pada paket atau dependensinya99 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model15 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelNo tool named like delete, drop or execLolos
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubcueapi-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/mcp
Configure (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 |
|---|---|
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_fire_cue |
Fire an existing cue immediately, optional payload override |
cueapi_update_cue |
Update a cue's mutable fields (name, schedule, callback, payload, etc.) |
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_get_execution |
Fetch a single execution by ID, with state + outcome |
cueapi_list_claimable_executions |
List unclaimed worker executions, filter server-side by task/agent |
cueapi_claim_execution |
Atomically claim a specific execution for processing |
cueapi_claim_next_execution |
Claim the next available execution (optional task filter) |
cueapi_execution_heartbeat |
Extend the claim lease on an in-flight execution |
cueapi_report_outcome |
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 tsx
Links
- 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.
Pertanyaan tentang CueAPI MCP
Bagaimana cara menambahkan CueAPI MCP ke Claude Code?
Jalankan claude mcp add --env 'CUEAPI_API_KEY=<YOUR_CUEAPI_API_KEY>' cueapi-mcp -- npx -y @cueapi/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan CueAPI MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan CueAPI MCP?
Server ini menyediakan 15 tool, termasuk cueapi_create_cue, cueapi_list_cues, cueapi_get_cue, cueapi_fire_cue, cueapi_update_cue.
Bagaimana cara menginstal CueAPI MCP server?
Anda dapat menginstalnya secara global menggunakan npm dengan npm install -g @cueapi/mcp atau menjalankannya tanpa instalasi menggunakan npx -y @cueapi/mcp.
Jenis tugas apa yang bisa saya jadwalkan?
Anda dapat membuat tugas berulang menggunakan jadwal cron maupun tugas satu kali menggunakan perintah 'at'.
Apakah saya bisa menggunakannya dengan Claude Desktop?
Ya, Anda dapat mengonfigurasi Claude Desktop dengan menambahkan server ke file claude_desktop_config.json Anda dan menyertakan CUEAPI_API_KEY Anda.