# Actiondock MCP server

Source: https://glimind.com/server/mcp-registry%2Fapp.actiondock%2Factiondock
Registry id: `mcp-registry/app.actiondock/actiondock`
Status: live (checked 2026-10-27T02:38:10.759Z)

## Verdict

Actiondock MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 842 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (100/100) across 8 tools, costing an agent about 1,312 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 842 ms | 27% of MCP servers |
| p95 handshake latency | 2979 ms | — |
| Checks in 30 days | 4,912 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 14 min | — |
| Agent-readiness score | 100/100 (A) | 94% of MCP servers |
| Tools | 8 | — |
| Tool-list size for an agent | ~1,312 tokens | 61% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "actiondock-mcp-server": {
      "type": "http",
      "url": "https://actiondock.app/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http actiondock-mcp-server https://actiondock.app/mcp
```

## Tools (8)

- `get_job`: Get the current status and result of an action job.
- `list_actions`: List every action available to the agent, including input schemas and side-effect flags.
- `list_connections`: List the workspace-approved HTTPS API connections, method/path allowlists and public operator identification with the effective User-Agent. Credentials are neve
- `list_events`: List recent job and callback events for workflow continuation and audit.
- `list_job_reconciliations`: Read the owner's append-only observations about an unknown write. These are owner reports, not verified provider facts, a changed job status, or permission to r
- `list_usage`: List metered action debits and the current UTC-month usage total.
- `run_action`: Create an action job. External writes always wait for workspace-owner approval in the dashboard; the owner is emailed, and wait_for_job blocks until the decisio
- `wait_for_job`: Wait for an action job to reach a decision or a final state: approved and executed, rejected, failed, or execution_unknown. A job still awaiting owner approval 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.