Ticket Demo MCP server

Read from the package source without running it. The installed server may list more.

• add_comment

  Add a comment to an existing ticket. You need a real ticket_id from search_tickets or get_ticket — do not invent TCK- ids. Pass author as the human speaking; omitting it attributes the comment to the service account. This is a write tool and may require a credential. To resolve the ticket after commenting, call close_ticket.

• close_ticket

  Resolve and close a support ticket (destructive, idempotent). Sets status to solved and records resolved_at. Optionally appends resolution as the final comment. If the ticket is already solved this is a no-op and returns alreadyClosed=true — do not retry. Use a real ticket_id from search_tickets or get_ticket. Use add_comment first if you want a longer explanation before closing. This is a write t

• create_ticketwrite action

  Open a support ticket on behalf of a customer. ALWAYS pass requester_email as the real customer email. If you omit it the call still succeeds (201) but the service account owns the ticket and every reply is mailed to the bot, not the customer — that is the attribution scar. A tool is not done when the API call succeeds; it is done when the next thing that happens is right. This is a write tool and

• describe_server

  Call this first, and again after any denial or empty tool list: server identity, auth mode, who the server thinks you are, the scopes you hold, your rate-limit budget, and every tool with the scope it needs and whether it is currently available. Discovery stays open in every auth mode. When a call was denied, this tells you which credential is missing — do not guess.

• get_schema

  Return fields and filterable keys for one schema. Call after list_schemas and before run_query so you know which filter keys are valid. name must be tickets, customers, or assets.

• get_ticket

  Fetch one ticket by id, including comments and attribution (customer vs service_account). Use when you already have a ticket_id like TCK-1001. If you do not have an id, call search_tickets first — a missing id is not a reason to invent one. Same data is also at ticket://TCK-1001.

• list_schemas

  List the queryable schemas on this server (tickets, customers, assets). Call this BEFORE run_query. There is no query_tickets, query_assets, or query_with_filter tool — discover the shape here, then get_schema, then run_query. Same list is also at schema://{name} after resources/list.

• lookup_customer

  Look up one customer by email (plan, region, contact). Use this for customer records, not tickets — tickets use search_tickets. Phone is PII: it stays REDACTED unless the caller presents a credential with the pii scope. Known demo emails: ada@example.com, sam@example.com. Do not invent other addresses and retry.

• run_querywrite action

  Run one exact-match query against a schema from list_schemas. Pass schema plus optional filter (keys from get_schema.filterable) and fields. This is the only query tool — do not invent query_tickets, query_assets, or query_with_filter. Empty rows mean no match; loosen the filter, do not retry the identical query.

• search_tickets

  Find support tickets by status, requester email, or a keyword in subject/body. Use this when someone asks to list, find, or search tickets. Default status is open — an empty list means no match for those filters, not that the server is empty; broaden to status=all or drop requester_email. Do not retry the same filters. To fetch one known id use get_ticket or read ticket://TCK-1001. Do not invent q

• Code scan12 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

83/100

higher than 68% of 915 Security servers

Tools

10

the typical Security server has 6

Tools that change things

20%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

1

more than 60% of 587 Security servers

Downloads a week

313

more than 80% of 248 Security servers with a package

Ticket Demo: common questions

Is Ticket Demo MCP server safe?

Mostly: it is graded B (83/100). Read the Ticket Demo safety report

How do I install Ticket Demo?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Ticket Demo need an API key?

Yes. The registry entry asks for MCP_API_KEY, MCP_USERS.

Is Ticket Demo maintained?

The last commit was 33 days ago (2026-10-02). The latest release is v1.9.0.

What can I use instead of Ticket Demo?

Servers from other publishers that do the same job: Md Log MCP server, Kalshi Prediction Markets MCP server and Rede MCP server.

How does Ticket Demo compare with other Security MCP servers?

safety score 83/100 (higher than 68% of 915 Security servers); tools 10 (the typical Security server has 6); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.