Connect AI agents to Acta over MCP

Open Account → Agents and make a key. Choose what it may do and which workspaces it reaches:

• Read: list boards, tasks, roadmap ideas and activity, and search across every board.
• Write: also create, change, sort, comment on, delete and restore tasks, one at a time or many at once.
• Manage: also create boards, edit labels, projects, fields and status names, run the public roadmap and triage ideas.

A key acts as the person who made it, never further. Everything an agent does is marked with the key's name, like “Elliot via Claude Code”. You can revoke a key at any time.

claude mcp add --transport http --scope user acta https://acta.aaenz.no/api/mcp \
  --header "Authorization: Bearer <key>"

Add Acta to ~/.codex/config.toml:

[mcp_servers.acta]
url = "https://acta.aaenz.no/api/mcp"
http_headers = { Authorization = "Bearer <key>" }

Add Acta to ~/.cursor/mcp.json, or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "acta": {
      "url": "https://acta.aaenz.no/api/mcp",
      "headers": { "Authorization": "Bearer <key>" }
    }
  }
}

Add Acta to .vscode/mcp.json:

{
  "servers": {
    "acta": {
      "type": "http",
      "url": "https://acta.aaenz.no/api/mcp",
      "headers": { "Authorization": "Bearer <key>" }
    }
  }
}

Any MCP client that speaks streamable HTTP works. The server is at https://acta.aaenz.no/api/mcp and takes the key as Authorization: Bearer <key>.

Put a line like this in your project's AGENTS.md, CLAUDE.md or README:

Acta board: workspace/board

The server tells agents how to work: check for an existing task before starting, move it to in progress and assign it to themselves, keep one progress comment up to date, and move it to review when there's something to look at.

• Reading: list_boards, get_board, list_tasks, search_tasks, get_task, list_activity, list_suggestions
• Writing: create_tasks, update_task, update_tasks, sort_column, add_comment, edit_comment, delete_task, restore_task
• GitHub: link_github, unlink_github, open_github_issue
• Managing: create_board, update_board, update_roadmap, review_suggestion

Each tool describes its own arguments, and the HTTP API lists them as JSON Schema.

Agents moving work from another tracker can keep its history: when each task was created and shipped, and who wrote each comment and when. Work closed as not planned goes to canceled.