ActionDock

Supervised API-write gateway for AI agents.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • List Actions: List every action available to the agent, including input schemas and side-effect flags.
  • 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 decision.
  • Get Job: Get the current status and result of an action job.

What data it sees

Do you need an account

No: the server works without sign-in

Supervised API-write gateway for AI agents. The agent proposes the exact HTTPS request to a workspace-approved REST API, a human owner approves the exact request in the dashboard, the credential stays server-side and never enters the agent context, and every job keeps an execution record (intent, decision, outcome, including an honest execution_unknown state when the provider response is lost).

Tools: list_actions, list_connections, run_action, get_job, wait_for_job, list_events, list_usage.

Setup: create a workspace and an API key at https://actiondock.app/dashboard, then configure this server with the key; initialize and tools/list work without a key, tools/call requires it. Docs: https://actiondock.app/agents and https://actiondock.app/llms.txt.

How to connect

How to connect ActionDock to Claude

The server address to paste into Claude settings:

https://actiondock--actiondock.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect ActionDock to ChatGPT

The server address to paste into ChatGPT settings:

https://actiondock--actiondock.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect ActionDock to Cursor

The server address to paste into Cursor settings:

https://actiondock--actiondock.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (7)

Raw names from tools/list. Only developers need these.

list_actionsList every action available to the agent, including input schemas and side-effect flags.
run_actionCreate 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 decision.
get_jobGet the current status and result of an action job.
wait_for_jobWait 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 when the timeout elapses is returned as awaiting_approval; call again to keep waiting. Keep timeout_seconds below your client's tool timeout.
list_eventsList recent job and callback events for workflow continuation and audit.
list_connectionsList the workspace-approved HTTPS API connections and their method/path allowlists. Credentials are never returned.
list_usageList metered action debits and the current UTC-month usage total.