The agent workflow
- 1
Scope a key to one project
Create an API key limited to the project the agent owns. Isolation is enforced server-side, per key.
- 2
Connect the agent over MCP
Point Claude Code, Cursor or any MCP-compatible agent at the Artikko MCP server with that key.
- 3
Let the agent pull its queue
The agent calls list_tickets to find work — filtered by status and severity — instead of being spoon-fed tasks.
- 4
Close the loop automatically
As the agent fixes issues it calls update_ticket to move status, reassign, or lower severity — the backlog stays truthful.
Why per-key isolation matters for agents
An autonomous agent with workspace-wide write access is a liability. Artikko scopes every key to its assigned projects at the API layer — the agent literally cannot see tickets outside its lane. That's the difference between "we let an agent touch production data" and "we gave a contractor exactly one project."
Agents pull their queue
Agents pull work by severity instead of waiting for assignment.
Auditable updates
Status changes are auditable — every update is attributed to the key.
One shared board
Humans keep the same board: agent updates appear in real time alongside the team's.
See pricing → · Back to the MCP server →
Hand an agent its first project
Full MCP access ships in the Free plan — try an agent on a scoped project before rolling it out to the team.