Pick a tool
Link GitHub pull requests to the tickets they fix
Artikko listens to GitHub webhooks and ties pull requests to tickets, so the board reflects what the code is actually doing. When the PR merges, the ticket knows.
Artikko What you get
- PR-to-ticket linking driven by webhooks — no manual cross-referencing.
- Status flows from code to board: open PR, review, merged, closed.
- Works per project: each Artikko project maps to its own repositories.
- Pairs with the MCP server so coding agents can update the linked ticket as they push.
Ticket events in Slack, discussion on the ticket
Use Artikko’s REST API and webhooks to push ticket events into Slack channels — new widget reports, severity changes, assignments. The alert lives in Slack; the discussion and evidence stay ticket-scoped in Artikko, where the next assignee can find them.
Artikko What you get
- Webhook-driven notifications for new reports and status changes.
- Keep Slack for alerts and Artikko’s ticket-scoped chat for the actual debugging thread.
- REST API lets you build exactly the routing your team wants.
- Every event carries the ticket link — one click from channel to full context.
Claude reads and works your backlog over MCP
Artikko ships a first-party MCP (Model Context Protocol) server, so Claude connects natively — no middleware. Five tools cover the ticket lifecycle: list_projects, list_tickets, create_ticket, update_ticket and list_users, all scoped to what the API key is allowed to see.
Artikko What you get
- File tickets from a Claude conversation — described once, categorized on arrival.
- Search the backlog before filing to catch duplicates.
- Update status, severity and assignee without leaving the chat.
- Per-key project scoping keeps agent access contained.
Claude talks to Artikko through the first-party MCP server — list, create and update tickets with access scoped per API key.
Claude Code works tickets like a teammate
Register Artikko’s MCP server in Claude Code and the agent in your terminal gains a backlog: it can pull its queue with list_tickets, read the captured evidence, fix the bug, and move the ticket with update_ticket — the same loop a developer runs, minus the tab-switching.
Artikko What you get
- One config block in your MCP settings — bearer token, done.
- Agents pick work by severity instead of waiting for a prompt.
- Ticket updates are attributed to the key, so agent work stays auditable.
- Combine with GitHub PR linking: fix, push, PR links to the ticket it closes.
Claude Code talks to Artikko through the first-party MCP server — list, create and update tickets with access scoped per API key.
The backlog, one mcp.json away from Cursor
Drop Artikko into .cursor/mcp.json and Cursor’s agent can see your tickets: search what’s open, read the report a widget captured — console log included — and update the ticket as the fix lands. MCP is the Model Context Protocol; Artikko’s server is first-party and included on every plan.
Artikko What you get
- Configure once in .cursor/mcp.json with a project-scoped key.
- Fix-from-ticket flow: read the evidence, write the code, close the loop.
- Same five MCP tools as Claude — one server, every MCP client.
- Free plan includes full MCP access, so trying it costs nothing.
Cursor talks to Artikko through the first-party MCP server — list, create and update tickets with access scoped per API key.
OpenAI-powered workflows, one shared backlog
Artikko is AI-native on the inside — the assistant drafts complete tickets with acceptance criteria from your PRD. On the outside, the REST API and webhooks let any OpenAI-powered automation you already run file reports, enrich tickets or pull the queue.
Artikko What you get
- AI drafting built in: title, structured description, acceptance criteria, severity.
- REST endpoints for filing and updating tickets from your own GPT-based tools.
- Webhooks stream ticket events into your automation pipelines.
- Idempotency keys keep retried automations from double-filing.
Built on PostgreSQL, isolated per tenant
Artikko stores every workspace on PostgreSQL with strict tenant isolation — your tickets, captures and audit log live in the most battle-tested open-source database there is, not a proprietary store you can’t reason about.
Artikko What you get
- Tenant-scoped data: workspaces are isolated at the database layer.
- REST API for pulling ticket data into your own reporting and BI.
- 90-day audit log retention on paid plans, queryable through the API.
- Attachments, recordings and console logs stored alongside their tickets.
A mailbox that files tickets by itself
Point a support mailbox at Artikko’s Microsoft Graph integration and inbound email becomes tickets automatically — sender, subject and body mapped into a categorized report, with confirmation flowing back to the reporter.
Artikko What you get
- Email-to-ticket over Microsoft Graph mail subscriptions.
- Reporters get automatic confirmations — no support rota needed for acknowledgments.
- Tickets land in the same backlog as widget reports and MCP-created issues.
- Combine with AI drafting to structure messy email reports on arrival.
Something missing? The REST API and webhooks cover custom pipelines, and the MCP server makes any MCP-compatible agent a client.
Connect your stack in an afternoon
Every integration works from the Free plan up. Create a workspace and wire GitHub, Slack and Claude before the standup ends.