MCP Tools

All eight tools exposed by @cueapi/mcp, with schemas and examples.

Eight tools, one per CueAPI surface an agent actually needs. Each is a thin wrapper over a REST endpoint — see the API Reference for the underlying HTTP contract.

`cueapi_create_cue`

Create a recurring (cron) or one-time (at) cue.

Arguments:

Field	Type	Notes
`name`	string, required	Human-readable cue name
`cron`	string, optional	Cron expression, e.g. `"0 9 * * *"`
`at`	string, optional	ISO-8601 timestamp for one-time fire
`callback_url`	URL, optional	Webhook URL fired when the cue triggers. Omit for worker transport.
`worker`	boolean, optional	`true` for worker transport (no callback URL)
`timezone`	string, optional	IANA timezone, default `"UTC"`
`payload`	object, optional	Arbitrary JSON payload delivered with the cue
`description`	string, optional

Provide either cron or at, not both. Provide either callback_url or worker: true.

`cueapi_list_cues`

List cues on the authenticated account.

Arguments:

Field	Type	Notes
`status`	`"active"` \| `"paused"`, optional	Filter by status
`limit`	integer, optional	1 to 100
`offset`	integer, optional

`cueapi_get_cue`

Fetch a single cue by ID, including current schedule and most recent execution.

Arguments:

Field	Type
`cue_id`	string, required

`cueapi_pause_cue`

Pause a cue. Paused cues do not fire until resumed. Equivalent to PATCH /v1/cues/{id} with {"status": "paused"}.

Arguments:

Field	Type
`cue_id`	string, required

`cueapi_resume_cue`

Resume a previously-paused cue. Equivalent to PATCH /v1/cues/{id} with {"status": "active"}.

Arguments:

Field	Type
`cue_id`	string, required

`cueapi_delete_cue`

Delete a cue permanently. Irreversible.

Arguments:

Field	Type
`cue_id`	string, required

`cueapi_list_executions`

List executions — the historical record of times a cue actually fired.

Arguments:

Field	Type	Notes
`cue_id`	string, optional	Filter to one cue
`status`	string, optional	Filter by execution status
`limit`	integer, optional	1 to 100
`offset`	integer, optional

`cueapi_report_outcome`

Report the outcome of an execution. Write-once — the outcome record is immutable. This is the accountability primitive: attach evidence that proves the work actually happened.

Arguments:

Field	Type	Notes
`execution_id`	string, required
`success`	boolean, required
`external_id`	string, optional	ID from the downstream system
`result_url`	URL, optional	Public URL proving the work happened (tweet, PR, etc.)
`summary`	string, optional	Short human summary, max 500 chars

The outcome is validated against the cue's verification policy. A missing required evidence field sets outcome_state = verification_failed even when success = true.

Example conversation

You: Schedule a daily 9am UTC job that posts a digest to my webhook https://my-app.example.com/digest.

Assistant (uses cueapi_create_cue): Created cue cue_abc123, first fire tomorrow at 9:00 UTC.

You: Show me the last five executions.

Assistant (uses cueapi_list_executions): ...

You: That last one reported success but I don't see the output. Report it as failed.

Assistant (uses cueapi_report_outcome): Recorded execution exec_... as failed.

Scope

The tools are bounded by what the API key is allowed to do. See API key scope.

Previous← Overview NextClaude Desktop →