Connect an external coding agent through MCP
Set up ACP's published stdio MCP package and understand the board actions it can perform.
Create account access in ACP
ACP exposes a Model Context Protocol server so tools such as Codex or Claude Code can act on your board. In Settings → Account → Agent access, create an MCP account token. Treat it as a credential: only share it with the client you intend to connect and revoke it if exposed. The remote package uses a local stdio process that calls ACP's authenticated HTTPS API; ACP does not expose a public MCP-over-HTTP endpoint.
Initialize your client
Run the published package's init command for your client, passing your ACP API URL and token. The initializer verifies your account and client before changing its configuration. It writes the token to a restricted local file and registers an MCP entry that points at that file. For a client-specific example, replace the placeholder values below; do not paste a real token into shared notes or screenshots.
- Use --client claude for Claude Code, or --client project for supported project-level client files.
- The published package connects to a remote ACP account; source-tree local mode is a separate developer workflow.
- Settings' manual Copy MCP config may contain a plaintext token. Prefer init when possible.
npx -y @errr0rr404/mcp@latest init --client codex --api-url https://YOUR-ACP-API --token YOUR_TOKENStart with a read, then a small action
Ask the connected client to list visible projects and read one ticket before creating or starting work. MCP can create and run standalone tickets, inspect state and logs, and participate in a Feature lifecycle. It does not expose Product roadmap planning, credential changes, team administration, or every dashboard action. Its write calls use the ticket's current workflow version; if someone else advances the ticket first, refresh its state and retry the correct action rather than replaying an old command.