Five tools, the whole ticket lifecycle

The MCP surface is deliberately small and complete — everything an agent needs to manage a ticket from report to resolved:

list_projects

The projects this key is allowed to see, nothing more.

list_tickets

List and search tickets with filters an agent can reason about.

create_ticket

File new tickets with category, severity and description.

update_ticket

Change status, severity and assignee as work progresses.

list_users

Resolve teammates for assignment.

Connect Claude in two minutes

Add Artikko to .cursor/mcp.json, Claude Desktop or Claude Code with one block of config:

{
  "mcpServers": {
    "artikko": {
      "url": "https://api.artikko.com/mcp",
      "headers": { "Authorization": "Bearer <your-project-api-key>" }
    }
  }
}

Per-key project scoping, not workspace-wide access

Every MCP key is scoped to its assigned projects. An agent connected with a key for one client project cannot list, read or touch any other project — isolation is enforced at the API layer, not by prompt convention. That is what makes it safe to hand an autonomous agent the backlog.

What teams run over MCP

Create tickets from Claude

Describe a bug in chat, get a filed, categorized ticket. How it works →

Give an AI agent the backlog

Agents pick up, work and close tickets end to end. How it works →

Triage bugs with AI

Batch-classify severity and route new reports. How it works →

MCP access is free — on every plan

Unlike trackers that gate agent access behind enterprise tiers, Artikko includes the full MCP server in the Free plan. Create a workspace, mint a key, connect Claude — before your coffee cools. See pricing →

Give your agents a backlog they can actually work

Full MCP server on the Free plan. Create a workspace, mint a key, connect Claude — before your coffee cools.

Get started free See pricing