AI Tasker does not claim this client supports a specific channel (MCP, API or otherwise) until confirmed in its official documentation and tested; this page describes how to discover AI Tasker via MCP or API.

How to connect AI Tasker

MCP server

Register AI Tasker as a remote (Streamable HTTP) or stdio MCP server in your client.
Authenticate with a per-workspace API key (Bearer atkr_ or x-api-key).
Discover the exposed tools and limit the set to the scopes you need.

https://mcp.ai-tasker.theboomer.dev/mcp

HTTP API

If your client cannot load MCP servers, call the per-workspace REST HTTP API.
Read /agent/service-info to see limits and channels without authenticating.

https://api.ai-tasker.theboomer.dev/agent/service-info · https://api.ai-tasker.theboomer.dev/docs

Official source

Kilo Code docs
https://docs.kilocode.ai/

AI Tasker grants no implicit permissions: tools, scopes, credentials and limits are defined per workspace.

Agents: read /llms.txt and /.well-known/ai-tasker.json for the discovery contract.