mcp · cueapi — Claude Code MCP server: features and setup
The mcp server connects Claude Code and other compatible MCP hosts to CueAPI, letting agents schedule work, inspect past runs, and record outcomes with supporting evidence.
claude mcp add --env CUEAPI_API_KEY=<CUEAPI_API_KEY> --env CUEAPI_BASE_URL=<CUEAPI_BASE_URL> --transport stdio cueapi-mcp -- npx -y @cueapi/mcpWhat mcp does
This server gives an MCP-enabled agent access to CueAPI for work scheduled at a recurring interval or a specific time. The agent can inspect jobs, review execution records, and trigger an existing job on demand. Tasks can continue beyond the current conversation.
Its tools cover job creation and maintenance, including edits, pausing, resuming, and permanent deletion. Agents can also retrieve executions awaiting workers, claim work for processing, and extend an active claim. A separate operation stores a final outcome alongside evidence such as an external identifier or URL. Each outcome is write-once.
Set CUEAPI_API_KEY to authenticate with CueAPI. Self-hosted deployments also need CUEAPI_BASE_URL. The package can run through npx -y @cueapi/mcp, provided the MCP host supports stdio servers. The API key is required to configure the connection.
What it helps with
- Schedule recurring or one-off agent jobs
- Inspect execution history and job status
- Claim an available worker execution
- Trigger an existing job with replacement or merged payload data
- Record a completed outcome with a supporting URL or external ID
Example prompts for the agent
- Create a daily job that sends a digest to my webhook.
- Show the execution history for this job and retrieve its recent results.
- Find an available execution, claim it for processing, and report the outcome with a result URL.
How to install mcp
Platform CLI
claude mcp add --env CUEAPI_API_KEY=<CUEAPI_API_KEY> --env CUEAPI_BASE_URL=<CUEAPI_BASE_URL> --transport stdio cueapi-mcp -- npx -y @cueapi/mcpReplace <…> with your own values
Platform CLI
codex mcp add cueapi-mcp --env CUEAPI_API_KEY=<CUEAPI_API_KEY> --env CUEAPI_BASE_URL=<CUEAPI_BASE_URL> -- npx -y @cueapi/mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"cueapi-mcp": {
"command": "npx",
"args": [
"-y",
"@cueapi/mcp"
],
"env": {
"CUEAPI_API_KEY": "<CUEAPI_API_KEY>",
"CUEAPI_BASE_URL": "<CUEAPI_BASE_URL>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"cueapi-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cueapi/mcp"
],
"env": {
"CUEAPI_API_KEY": "<CUEAPI_API_KEY>",
"CUEAPI_BASE_URL": "<CUEAPI_BASE_URL>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e CUEAPI_API_KEY=<CUEAPI_API_KEY> -e CUEAPI_BASE_URL=<CUEAPI_BASE_URL> cueapi-mcp npx -y @cueapi/mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about mcp
How do I install mcp in Claude Code?
Run claude mcp add mcp -e CUEAPI_API_KEY=<CUEAPI_API_KEY> -- npx -y @cueapi/mcp. Replace <CUEAPI_API_KEY> with your CueAPI key.
What does the mcp MCP server do?
It connects an agent to CueAPI for scheduling and managing jobs, retrieving execution history, and handling worker tasks. Agents can also submit a final result with an external ID or URL as evidence.
How do I configure mcp for a self-hosted CueAPI instance?
Set both CUEAPI_API_KEY and CUEAPI_BASE_URL. In Claude Code, run claude mcp add --env CUEAPI_API_KEY=<CUEAPI_API_KEY> --env CUEAPI_BASE_URL=<CUEAPI_BASE_URL> --transport stdio cueapi-mcp -- npx -y @cueapi/mcp.
Similar MCP servers
All MCP servers for Agent setup: memory, context, orchestration →mcp by other authors comes first.
