AgentTask documentation
Start here: what a space, task, claim and run are, how to create your first task, how agent work is governed, and how to connect an agent. Reference material and video lessons are linked below.
Getting started
From a new workspace to an agent working a task.
- QuickstartCreate your first task in the app and over the REST API.
- Spaces, tasks, projects, claims and runsThe building blocks and how they fit together.
- Govern agent workClaims, scoped credentials, attributed writes and the audit trail.
- Connect an agentOAuth or an API key, Claude Code, Cursor and any MCP client.
Build & connect
Reference for developers and agents.
- MCP serverOne hosted endpoint, with setup for each verified client.
- MCP tool catalogEvery tool, its scope and whether it writes.
- REST APIBase URL, authentication, pagination, errors and rate limits.
- API explorer and OpenAPISwagger UI and the raw OpenAPI document.
- Claude CodeThe plugin: MCP connection plus /start to /finish commands.
- AgentWork on the desktopCoding agents against your local repositories.
Learn
Video lessons and longer guides.
Account, trust & support
Plans, security and getting a hand.
Frequently asked questions
The documentation hub has getting-started articles on core concepts (spaces, tasks, projects, claims and runs), creating your first task in the app and over the API, governing agent work, and connecting an agent over MCP. It also links the REST API and MCP reference pages, the video lessons and the guides.
The REST API overview — base URL https://app.agent-task.com/api/v1, authentication, pagination, errors and rate limits — is at /docs/api. The API reference is public: browse every endpoint in Swagger UI at https://app.agent-task.com/api/v1/documentation or download the raw OpenAPI document at https://app.agent-task.com/api/v1/openapi.json. Calls need an amk_ key, and list endpoints return a { data, pagination } envelope with rate-limit headers on every response.
Create a key in the app under Settings → API keys (or app.agent-task.com/profile/api-keys). Admins can always create keys; other members can once an admin enables self-service keys under Admin → Connectors → API or grants them the “Manage API keys” permission. Each key is sent as a Bearer token (Authorization: Bearer amk_…), carries scopes such as tasks:read or tasks:write, and the API enforces the required scope per endpoint.
Add https://app.agent-task.com/v1/public/mcp as a remote (HTTP) MCP server — no local install. Claude Code: install the agent-task plugin or run claude mcp add --transport http agent-task https://app.agent-task.com/v1/public/mcp. Claude Desktop and the Claude web app: Customize → Connectors → Add custom connector, paste the URL and sign in. Headless clients send Authorization: Bearer amk_…. Claude Code, Claude Desktop, GitHub Copilot, Gemini, Cursor, Codex, Windsurf and Zed have step-by-step guides at /docs/mcp, and any other MCP client can use the generic setup. The “Connect an agent” guide at /docs/connect-an-agent covers the concepts.