How it works
- 1
Mint a project API key
In Tiqzen, create an API key scoped to the projects your assistant should see. Per-key scoping keeps every other project invisible.
- 2
Add Tiqzen to your MCP config
Register the Tiqzen MCP server in Claude Desktop, Claude Code, .cursor/mcp.json or any MCP-capable client with the key as a bearer token.
- 3
Describe the bug in chat
Tell your assistant 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 by hand means translating a debugging session into prose, switching tools, and re-finding your place. Through the conversation you were already having, the discussion itself becomes the record — filed where the whole team can see it.
Search input resets while typing
console
✕ TypeError: value is null
⚠ retry fired ×3
last 200 lines attached
Context comes free
Your assistant 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 the assistant search existing tickets first, so duplicates get caught before they're filed.
Scoped by key
Everything is scoped: the key your assistant 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 your assistant to a real backlog today, upgrade only when the team grows.