Model Context Protocol

The MCP server that puts your bug tracker inside every AI tool

Tiqzen ships its own MCP server on every plan — including Free. Connect Claude, Claude Code, Cursor or any MCP-compatible agent and your backlog stops being a silo: agents can read it, work it and update it, acting as you, with exactly the access you already have.

claude — connected to tiqzen mcp 18 tools

Eighteen tools, the whole ticket lifecycle

The MCP surface covers everything an agent needs to manage a ticket from report to resolved — and to log the work it did along the way:

list_projects

The projects you can see, nothing more.

get_project

One project in full, including its ticket rules.

list_sprints

Sprints and the backlog, so work lands in the right place.

list_tickets

List tickets with filters an agent can reason about.

get_ticket

One ticket, complete: description, links, history.

search_tickets

Free-text search across titles and ticket IDs.

create_ticket

File new tickets with category, severity and description.

update_ticket

Change status, severity and assignee as work progresses.

validate_ticket_description

Check a draft against the project's ticket rules first.

list_ticket_links

See what a ticket blocks, duplicates or relates to.

link_tickets

Connect related tickets.

unlink_tickets

Remove a link that no longer holds.

list_users

Resolve teammates for assignment.

list_tags

The tags a project allows.

create_tag

Add a new tag when none fits.

add_comment

Leave a note on a ticket, in your name.

log_time

Log time against a ticket.

list_my_time

Read back your week of logged time.

Connect Claude in two minutes

Tiqzen runs a hosted MCP server. There is nothing to install and no key to copy: add one URL to your AI tool, sign in to Tiqzen once in the browser, and you are connected.

https://api.tiqzen.com/api/mcp

Claude Code

claude mcp add --transport http tiqzen https://api.tiqzen.com/api/mcp

Then type /mcp in Claude Code and choose Authenticate.

Codex CLI

codex mcp add tiqzen --url https://api.tiqzen.com/api/mcp
codex mcp login tiqzen

The second command opens a browser window to sign in.

Claude Desktop and claude.ai

Open Settings → Connectors → Add custom connector, paste the URL above, then click Connect and sign in.

Cursor

Add a server named tiqzen with the URL above to your mcp.json — no headers needed. Cursor asks you to sign in the first time it connects.

Your permissions, nothing more

Any client in, one governed backlog out

A connected agent acts as you: it sees exactly the projects and tickets you can see, and nothing else. Permissions are enforced at the API layer, not by prompt convention, and you can disconnect any app at any time in Settings → Security → Connected apps. That's what makes it safe to hand an autonomous agent the backlog.

AI chat IDE agent Terminal Any agent

Tiqzen

MCP server

18 tools · your permissions

list search backlog create file tickets update move status CASL-enforced

What teams run over MCP

Create tickets from your AI

Describe a bug to any assistant, get a filed, categorized ticket. How it works →

Give an AI agent the backlog

Agents pick up, work and close tickets end to end. How it works →

Triage bugs with AI

Batch-classify severity and route new reports. How it works →

MCP access is free — on every plan

Unlike trackers that gate agent access behind enterprise tiers, Tiqzen includes the full MCP server in the Free plan. Create a workspace, add one URL, connect Claude — before your coffee cools. See pricing →

Give your agents a backlog they can actually work

Full MCP server on the Free plan. Create a workspace, paste one URL into Claude, sign in — before your coffee cools.