Skip to content

Build on AgentTask: REST API and MCP server

Build on AgentTask — a REST API and an MCP server, secured by organization-scoped API keys. The full endpoint reference is public: browse the Swagger UI at app.agent-task.com/api/v1/documentation or download the OpenAPI spec at app.agent-task.com/api/v1/openapi.json.

At a glance

MCP endpoint
https://app.agent-task.com/v1/public/mcp (remote MCP over HTTP)
MCP tools
87, each with a declared scope
MCP sign-in
OAuth 2.1 with dynamic client registration and PKCE, or a Bearer organization API key (amk_…)
REST API
/api/v1 on the app host; OpenAPI document at https://app.agent-task.com/api/v1/openapi.json
Pagination
limit (1 to 500, default 100) and offset
Rate limits
X-RateLimit-* headers on every response; over the limit returns 429 with Retry-After

Resources

MCP endpoint

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

Built on the Model Context Protocol; protected-resource metadata follows RFC 9728. Sign in with OAuth 2.1 (no key to copy), or send an organization API key as Authorization: Bearer amk_…. Setup for each client.

Service state for the API and MCP endpoint is on the status page, which is attested by hand rather than live.

ChangelogWhat’s new across the API and platform.

Developer FAQ

https://app.agent-task.com/api/v1. The OpenAPI document is at https://app.agent-task.com/api/v1/openapi.json and Swagger UI is at https://app.agent-task.com/api/v1/documentation.

Send an API key as a Bearer token (Authorization: Bearer amk_…). Keys carry scopes such as tasks:read or tasks:write, and the API enforces the required scope per endpoint. The MCP endpoint also supports OAuth 2.1 browser sign-in.

Combined API + MCP volume is 2,500 requests/day on Free, 10,000/day on Pro, 50,000/day on Team and 1M/day on Enterprise.

https://app.agent-task.com/v1/public/mcp, a remote MCP server over HTTP. Setup for each verified client is at /docs/mcp and the tool list is at /docs/mcp/tools.