Skip to main content

​
Why use MCP with DispatchQ?

MCP gives agents safe, structured primitives for background execution instead of direct long-running HTTP calls.

​
MCP server setup (Claude Desktop)

See full setup in MCP Setup. Once configured, your agent can call DispatchQ tools directly.

​
All 10 tools

create_job

Create a job with delay, approval, dedupe, idempotency.

get_job

Fetch status, results, errors, and next actions.

cancel_job

Cancel pending/awaiting_approval jobs.

approve_job

Approve a job awaiting human review.

retry_job

Create a retry copy from failed/cancelled job.

list_jobs

List/filter recent jobs.

create_schedule

Create recurring cron schedule.

get_schedule

Get one schedule.

list_schedules

List schedules.

delete_schedule

Delete a schedule.

​
Conversation example

User: Run monthly usage reconciliation every first day at 09:00 UTC.
Agent: I'll create a schedule now.
Agent (tool: create_schedule): {"cron_expr":"0 9 1 * *", ...}
Agent: Schedule created as sch_123. I can pause/resume it later.

​
Polling pattern for async job results

1) create_job
2) store returned job id
3) poll get_job every 2-5s
4) stop when status in [completed, failed, cancelled]