AgentDock MCP

Install

Works in

• Claude Code
• Codex
• Cursor
• Claude Desktop
• SourceCraft
• Koda
• Coddy

Manual install

{
  "mcpServers": {
    "agentdock": {
      "url": "http://127.0.0.1:8765/mcp",
      "headers": {
        "Authorization": "Bearer <AGENTDOCK_AUTH_TOKEN>"
      }
    }
  }
}

What it does

AgentDock is a standalone tool runtime for agents: it gives unified, controlled access to files, commands, Git, skills, MCP and a browser on the machines you choose. From one conversation in the agent you can operate several computers and servers: write code, change configuration, run commands and deploy right where the work belongs. File reads and writes are atomic with path boundaries and private-directory protection. It connects over MCP through a local HTTP address with a bearer token, installs via Docker or natively, and ships built-in skills.

Who it is for. For developers and devops who need to give an agent controlled access to machines and servers.

Example request

Connect to my server and restart the service after updating the configuration

MCP

Transport

http

Authentication

API key

Limitations

The runtime gives the agent access to commands and files on real machines, so access and tokens must be tightly controlled. MCP connection goes over HTTP with a bearer token, and remote work needs careful network setup. It installs via Docker or natively.

How to disable. Remove the agentdock server from the MCP config and stop the runtime or container.

README in short

The README describes AgentDock as a standalone tool runtime for agents that gives controlled access to files, commands, Git, skills, MCP and a browser across several machines. From one conversation the agent operates computers and servers: writing code, changing configuration, running commands and deploying services. File work is atomic with path boundaries and private-directory protection. MCP connection goes through a local HTTP address with a bearer token, installed via Docker or natively. Apache-2.0 licensed.