MCP Execution Tools
Tools for monitoring and managing skill executions over MCP.
Skills are not executed directly over MCP. Executions are started by the Clanker agent in chat or by slash commands in the app. Over MCP, these tools let you check status, list past runs, and cancel an active execution. To follow a run in real time, connect to the SSE stream:
GET /api/v1/executions/:executionId/eventsSee Executions for event types.
get-execution-status
Check the status of the current or most recent skill execution.
Parameters
None required.
Example
{
"tool": "get-execution-status",
"arguments": {}
}
Response (Running)
{
"success": true,
"data": {
"executionId": "exec_abc123def456",
"status": "running",
"skillSlug": "readme-generator",
"startedAt": "2024-01-15T10:30:00.000Z"
}
}
Response (Idle)
{
"success": true,
"data": {
"status": "idle",
"message": "No active executions"
}
}
list-executions
List recent skill executions with their status and results.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
limit | number | No | 20 | Max results (1-100) |
offset | number | No | 0 | Offset for pagination |
Example
{
"tool": "list-executions",
"arguments": {
"limit": 10
}
}
Response
{
"success": true,
"data": [
{
"executionId": "exec_abc123",
"skillSlug": "readme-generator",
"skillName": "README Generator",
"status": "completed",
"cost": 45,
"artifactId": "art_abc123",
"startedAt": "2024-01-15T10:30:00.000Z",
"completedAt": "2024-01-15T10:31:30.000Z",
"hasConnectorResult": false,
"connector": { "type": "remote", "fields": {} }
},
{
"executionId": "exec_def456",
"skillSlug": "code-reviewer",
"skillName": "Code Reviewer",
"status": "completed",
"cost": 120,
"artifactId": "art_def456",
"startedAt": "2024-01-15T09:15:00.000Z",
"completedAt": "2024-01-15T09:18:45.000Z",
"hasConnectorResult": false,
"connector": { "type": "remote", "fields": {} }
}
],
"pagination": { "hasMore": true }
}
cancel-execution
Cancel an active skill execution.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
executionId | string | No | Execution ID to cancel (defaults to current execution) |
Example
{
"tool": "cancel-execution",
"arguments": {}
}
Response
{
"success": true,
"data": {
"cancelled": true,
"executionId": "exec_abc123"
}
}
Errors
| Code | Description |
|---|---|
NOT_FOUND | No active execution or execution already completed |
Monitoring Workflow
Typical Flow
1. A skill execution is started in the Clanker app (chat or slash command).
2. MCP client:
- Calls get-execution-status() to see if a run is active
- Calls list-executions() to review recent runs and their results
- Calls list-artifacts() / get-artifact(id) to retrieve generated output
3. To follow a run live, connect to the SSE stream:
GET /api/v1/executions/:executionId/events
Handling Long Executions
Executions can take up to 65 minutes. The MCP client should:
- Poll
get-execution-statusorlist-executionsperiodically - Or connect to the SSE event stream for the execution
- Or instruct the user to check the mobile app