How it works
- 1
Mint a project API key
In Artikko, create an API key scoped to the projects Claude should see. Per-key scoping keeps every other project invisible.
- 2
Add Artikko to your MCP config
Register the Artikko MCP server in Claude Desktop, Claude Code or .cursor/mcp.json with the key as a bearer token.
- 3
Describe the bug in chat
Tell Claude what broke. It calls create_ticket with a title, structured description, category and severity.
- 4
Review the filed ticket
The ticket lands in your backlog, categorized and ready to triage — status updates flow back through update_ticket.
Why it beats copy-paste
Filing an issue by hand means translating a debugging session into prose, switching tools, and re-finding your place afterwards. Doing it through the conversation you were already having removes the translation step entirely — the assistant turns the discussion itself into the record, and the backlog stays where the whole team can see it.
Context comes free
Claude already has the context — stack traces, repro steps, the file you were discussing — so the ticket description writes itself.
Categorized on arrival
Tickets land categorized with a severity suggestion instead of joining an untriaged pile.
Duplicates caught early
The same connection lets Claude search existing tickets first, so duplicates get caught before they're filed.
Scoped by key
Everything is scoped: the key Claude uses can only touch the projects you assigned it.
See pricing → · Back to the MCP server →
Turn your next chat into a filed ticket
The MCP server is included in the Free plan — connect Claude to a real backlog today, upgrade only when the team grows.