Where bugs become shippable tickets
Artikko is bug tracking built for the AI era — capture bugs with screenshots, console logs and screen recordings, draft the ticket with AI, and plug your backlog into any AI agent over MCP. Issues go from report to resolved without the busywork.
Free to try · Bug tracking for product & engineering teams
Checkout total ignores applied coupon
Empty state flashes before dashboard loads
Login button does nothing on Safari 17
Webhook retries duplicate the ticket
Add MCP key rotation to project settings
SDK report drops large screen recordings
Plays well with your stack
A bug tracking platform that does the heavy lifting
From the first bug report to a closed sprint — capture, triage, collaborate and ship, with the busywork automated.
Real-time ticket chat
Discuss issues where they live. Socket.IO-powered chat scoped to each ticket, with reactions, mentions and presence.
Screen recordings & screenshots
Every report can carry a recording, screenshots and console logs — up to 50MB, stored and attached automatically.
Sprints & boards
Drag-and-drop kanban, sprint folders, subtasks and configurable per-project status workflows.
GitHub PR linking
Link pull requests to tickets via webhooks and watch status flow from code to closed.
Dashboards & reports
Response-time and resolution reporting, personal dashboards and a 90-day audit log.
Roles & isolation
Role-based access for clients, leads and developers — every API and MCP key scoped to its projects.
Drop in a bug report widget. Get reproducible tickets.
Embed the SDK and your users file bugs without leaving your app. Artikko auto-captures a screenshot, the console log, a screen recording and the environment — then files a triaged ticket and emails the reporter a confirmation.
- Screenshot, console log & screen recording captured automatically
- Idempotency keys de-duplicate retries — no double tickets
- Lands as a categorized BUG with severity, ready to triage
// 1. install the SDK
$ npm i artikko-sdk
// 2. report a bug
await fetch("/api/sdk/report", {
method: "POST",
headers: { "x-api-key": KEY },
body: JSON.stringify({
title, description, severity, email,
attachments // screenshot, log, recording
}),
})AI drafts the ticket. Any agent works the backlog.
Describe it once. AI writes the rest.
Type the problem in plain language and the assistant drafts a complete ticket — title, a structured description with acceptance criteria, plus a suggested category, severity and dates — grounded in your project’s PRD documents.
- Structured description with technical requirements & acceptance criteria
- Suggested category, severity and start/due dates
- Reads your PRD documents for project-specific context
Login form fails to submit on Safari
Acceptance criteria
- Login submits on Safari 16+ and dispatches the auth request
- Disabled/loading state shows while the request is in flight
- Regression test covers the Safari form-submit path
Your tickets, inside any AI tool.
Artikko ships its own MCP server. Connect Claude or any MCP-compatible agent and it can list and search tickets, create them, and update status, severity and assignee — scoped to exactly the projects an API key can see.
- Five tools: list_projects, list_tickets, create_ticket, update_ticket, list_users
- Per-key project scoping keeps access isolated
- Works with Claude and any MCP-compatible client
// agent calls the MCP server
create_ticket({
projectSlug: "acme-web",
title: "Login fails on Safari",
severity: "Critical",
category: "Bug"
})
// → { ticketId: "ACME-245", status: "Backlog" }Ticket statuses, fully configurable
Per-report capture: video, logs, shots
MCP tools for any AI agent
Audit-log retention out of the box
An SDK and an MCP server, not just a UI
Artikko is built API-first. Ship the widget, automate from the terminal, or hand the backlog to an agent.
Typed SDK
Shared Zod schemas, enums and types so client and server never drift.
MCP server
A first-class Model Context Protocol surface for AI agents.
REST & webhooks
Report endpoint, GitHub PR webhooks and inbound email-to-ticket.
# install the shared SDK & types
npm i artikko-sdk
import { TicketSeverity, TicketCategory } from
'artikko-sdk/enums';Trusted where the work happens
Product, engineering and QA teams use Artikko to turn noisy bug reports into a clean, shippable backlog.
“The embeddable widget turned vague “it’s broken” messages into reproducible tickets with a recording attached. Our triage time dropped off a cliff.”
“Our agents create and update tickets straight through the MCP server. It feels like the backlog finally lives where the work happens.”
“AI drafts the description with acceptance criteria from our PRD. Engineers tweak instead of writing from scratch.”
“Sprints, screen recordings and GitHub PR links in one place. We retired two tools the week we switched.”
“Real-time chat scoped to each ticket keeps the context with the bug, not lost in a channel.”
“The embeddable widget turned vague “it’s broken” messages into reproducible tickets with a recording attached. Our triage time dropped off a cliff.”
“Our agents create and update tickets straight through the MCP server. It feels like the backlog finally lives where the work happens.”
“AI drafts the description with acceptance criteria from our PRD. Engineers tweak instead of writing from scratch.”
“Sprints, screen recordings and GitHub PR links in one place. We retired two tools the week we switched.”
“Real-time chat scoped to each ticket keeps the context with the bug, not lost in a channel.”
“The embeddable widget turned vague “it’s broken” messages into reproducible tickets with a recording attached. Our triage time dropped off a cliff.”
“Our agents create and update tickets straight through the MCP server. It feels like the backlog finally lives where the work happens.”
“AI drafts the description with acceptance criteria from our PRD. Engineers tweak instead of writing from scratch.”
“Sprints, screen recordings and GitHub PR links in one place. We retired two tools the week we switched.”
“Real-time chat scoped to each ticket keeps the context with the bug, not lost in a channel.”
“The embeddable widget turned vague “it’s broken” messages into reproducible tickets with a recording attached. Our triage time dropped off a cliff.”
“Our agents create and update tickets straight through the MCP server. It feels like the backlog finally lives where the work happens.”
“AI drafts the description with acceptance criteria from our PRD. Engineers tweak instead of writing from scratch.”
“Sprints, screen recordings and GitHub PR links in one place. We retired two tools the week we switched.”
“Real-time chat scoped to each ticket keeps the context with the bug, not lost in a channel.”
Questions, answered
Still curious? Create a workspace and see for yourself.
Click "Try now", pick a workspace name and your own URL, and verify your email — your Artikko workspace is ready in minutes, no invitation needed.
Start turning bug reports into shipped fixes
Create a workspace for your team — capture, AI-draft, and automate your backlog from day one.