cueapi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CUEAPI_API_KEY | Yes | Your CueAPI API key, generated at cueapi.ai | |
| CUEAPI_BASE_URL | No | Base URL for self-hosting CueAPI, used alongside CUEAPI_API_KEY |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cueapi_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. |
| cueapi_list_cuesC | List cues on the authenticated account, optionally filtered by status. |
| cueapi_get_cueA | Fetch a single cue by ID, including current schedule and most recent execution. |
| cueapi_pause_cueA | Pause a cue. Paused cues do not fire until resumed. |
| cueapi_resume_cueB | Resume a previously-paused cue. |
| cueapi_delete_cueA | Delete a cue permanently. Irreversible. |
| cueapi_list_executionsB | List executions — the historical record of times a cue actually fired. Optionally filter by cue, status, or paginate. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.