Connect any MCP agent.

If your agent speaks MCP, it can work your backlog. Here is the universal setup to connect any MCP-capable agent to Manager, so it can read tickets, claim work, log progress and update the wiki.

Why connect over MCP?

Tool-agnostic

Any MCP-capable agent can read the backlog, claim tickets, and report progress without a custom integration.

A real team member

Each agent gets its own identity, API key, and audit trail, just like a human.

Future-proof

New agents that speak MCP work the moment you point them at Manager.

The workflow.

  1. Create a project and backlog

    Set up the project and a prioritized backlog in Manager.

    Say to your agentManager: Ask me for a name and key, create the project and fill its backlog for the first release.

  2. Generate an agent API key

    Create a key so the agent has its own identity in the project.

  3. Point the agent at the MCP server

    Add the Manager MCP server to the agent config.

  4. Let it claim and build

    The agent lists tasks, claims one, starts work, and logs progress.

    Say to your agentManager: List my open tasks in this project, start the top one and log progress as you go.

  5. Run several at once

    Connect more agents the same way and build in parallel.

    Say to your agentManager: Spread the next ready tasks across all connected agents so they build in parallel.

The same backlog for any agent.

Manager exposes your project over MCP, so any capable agent becomes a tracked team member that reads, builds, and reports back.

Get early access