Connect an agent to AgentTask over MCP

Choose how the agent signs in

• OAuth (recommended for Claude Desktop and the Claude web app): each person signs in with their own account, writes are attributed to them, and the connection is limited to the spaces they tick on the consent screen.
• Organization API key (amk_…): for scripts, automation and clients that cannot run a browser flow. Create it in the app under Settings, then API keys (an admin can always; other members need self-service keys enabled or the “Manage API keys” permission) and grant it the scopes it needs. By default it reaches every space in the organization within those scopes; you can confine a key to specific spaces when you create it.

The endpoint

The server speaks the Model Context Protocol over Streamable HTTP, on a single HTTPS URL with no local install:

https://app.agent-task.com/v1/public/mcp

Use it exactly as shown, with no extra path and no trailing slash. A client without a token gets a 401 with OAuth discovery metadata, which is how OAuth-capable clients find the sign-in flow on their own.

Claude Desktop or the Claude web app

Add a custom connector, paste the endpoint as its URL, and sign in to AgentTask when the browser opens. Review the scopes and tick at least one space on the consent screen, then approve. Write tools ask for your approval in the client before they run.

Claude Code

The AgentTask plugin wires the MCP connection and adds workflow commands (/start, /plan, /update, /triage, /standup, /report, /organize, /note, /init, /finish) plus skills that keep the ticket current while you work. Install it from the plugin marketplace:

/plugin marketplace add AgentTaskLLC/AgentTask-plugin
/plugin install agent-task@agent-task

Cursor and other MCP clients

Any MCP-capable client can connect with a Bearer key. A typical configuration looks like this:

{
  "mcpServers": {
    "agent-task": {
      "type": "http",
      "url": "https://app.agent-task.com/v1/public/mcp",
      "headers": { "Authorization": "Bearer ${AGENT_TASK_API_KEY}" }
    }
  }
}

Check that it works

Ask the agent to list the spaces in your organization; it will call list_spaces. Copy a space uuid from the result, then ask for a small reversible change, such as moving a task to in_progress, and approve the write. To begin real work the agent calls start_work, which claims the ticket so two agents never collide.

If the endpoint returns 404 on a self-managed install, the administrator has not enabled the MCP server (and, for OAuth, MCP OAuth) on the API service.