MCP use case

Create tickets from whichever AI you're already talking to

You're mid-debug — in Claude, in Cursor, in an agent running in your terminal — and find a bug that isn't yours to fix. The old flow: open the tracker, re-describe everything, lose your thread. With Tiqzen connected over MCP, the assistant files the ticket for you — title, structured description, category and severity — while you keep working. Any IDE, any terminal, any AI that speaks MCP.

claude — connected to tiqzen mcp 23 tools

How it works

  1. 1

    Add the Tiqzen MCP server

    Add the Tiqzen MCP server URL to Claude Desktop, claude.ai, Claude Code, Cursor or any MCP-capable client — the exact steps for each are on the MCP server page.

  2. 2

    Sign in once

    Your client opens a browser window: sign in to Tiqzen and approve. No key to copy — the assistant acts as you, never with more than the access you already have.

  3. 3

    Describe the bug in chat

    Tell your assistant what broke. It calls the tickets tool (action create) with a title, structured description, category and severity.

  4. 4

    Review the filed ticket

    The ticket lands in your backlog, categorized and ready to triage — status updates flow back through tickets (action update).

No translation step

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.

STO-495 MAJOR BUG AI draft

Search input resets while typing

screenshot.png

console

✕ TypeError: value is null

⚠ retry fired ×3

last 100 entries attached

recording · 0:14
LF MD
Ready to triage

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 with the category and severity your assistant sets 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.

Your permissions, nothing more

The assistant acts as you: it never sees or touches more projects than you can, and you can disconnect it any time in Settings → Security → Connected apps.

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.