MCP Ticket Demo vs MCP Atlassian

MCP Ticket Demo tools 19

• create_ticketOpen 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 may require a credential.
• add_commentAdd a comment to an existing ticket. You need a real ticket_id from run_query schema=tickets — 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_ticketResolve 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 run_query schema=tickets. Use add_comment first if you want a longer explanation before closing. This is a write tool and may require a credential.
• get_schemaDiscover names and shapes. With no name: lists every name with its kind (data = object shape: ticket, customer, server; query = tickets, customers, assets, timers, system, settings, events, users, api_keys, trace, errors or counters, the only names run_query accepts; tool = that tool's arguments). With a name from that list: the shape of that one. This does not perform the task. kind=query: the filterable keys are for run_query. kind=tool: these are the arguments, call that tool next and do not pass the tool name to run_query. kind=data: an object shape, call the tool named in next. An unknown name is an error. There is no list_schemas tool and no query_tickets tool.
• run_queryExact-match rows for schema tickets, customers, assets, timers, system, settings, events, users, api_keys, trace, errors or counters only. Timers are read here (there is no get_timer): state, elapsed_ms and remaining_ms are worked out when you query. system is one row about this machine: memory, CPU, disk and whether it is in a container (inside Docker those are the container limits); there is no system_info tool. settings is one row: the saved settings, with no API keys or passwords (there is no get_settings tool); change them with update_settings (MQTT: set_mqtt). events are the events already announced, newest first; filter type takes a name or a group such as ticket.*. users and api_keys need an admin credential and never contain a password or a key secret; there is no list_users or list_api_keys tool. trace (the call trace, only while audit is on), errors (failed calls) and counters (success, error and denied per tool) also need an admin credential; there is no export_log tool. tickets: this is how tickets are found and read (there is no search_tickets or get_ticket tool). filter status (open, pending, solved), requester_email, attribution, query (a keyword in subject or body), or id for one ticket with its body and comments. A list returns the short fields; pass fields to choose others. customers: filter email for one customer (there is no lookup_customer tool). phone is the text REDACTED unless you present a credential with the pii scope. Do not pass a tool name or a singular data name. Do not invent query_tickets or query_with_filter. Empty rows mean no match; loosen the filter, do not retry the same query.
• describe_serverCall 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. The tools list is the set of actions — call a tool to do the work, do not get_schema it first. Discovery stays open in every auth mode. When a call was denied, this tells you which credential is missing — do not guess.
• update_settingsChange settings in one call. The argument has the shape of the settings row that run_query schema=settings returns, and every field is optional: authMode (off, write or all); rateLimit {enabled, limit, windowSeconds}; audit (record the call trace); uiAuth (hide the desk pages until sign-in); protocols {stdio, streamableHttp, sse} (at least one stays on); events {enabled, types, autoTimer, autoSystem} (which events the server announces; types are names, groups such as ticket.* or *); toolGates {tool: true|false} (false disables a tool, not describe_server); toolAuthOverrides {tool: true|false} (true requires a credential for that tool even while auth is off); toolScopeOverrides {tool: read|write|pii|admin|default} (default restores the tool's own scope; admin tools, describe_server and generate_traffic cannot change). Only the fields you send change. Everything is checked first, and if any part is refused nothing is changed. MQTT has its own tool, set_mqtt. Requires admin even when auth mode is off, because it can change auth mode, the rate limit, the call trace, the page lock and who may call what. Then call run_query with schema=settings, or describe_server for the scopes and gates in force.
• set_mqttPublish the events to an MQTT broker. Publish only: the server does not subscribe. Send url (mqtt://host:1883 or mqtts://host:8883), enabled, topic_prefix, username, password, qos 0 or 1, retain. Anything left out stays. Events must be on (update_settings with events.enabled=true) and only the kinds meant for everyday listeners are published, never settings, users or keys. The password is kept in memory and never shown again. test=true publishes one message to <prefix>/test. Requires admin. Then call run_query with schema=settings and read mqtt.status.
• create_userCreate a user. The password is stored as a hash and is never listed. The built-in admin cannot be replaced. Requires admin.
• delete_userDelete a user by username. The built-in admin cannot be removed. Requires admin.
• issue_api_keyIssue an API key. The secret is returned once in key and is not stored. Requires admin. Then call run_query with schema=api_keys and confirm the secret is absent.
• revoke_api_keyRevoke an API key by id from run_query schema=api_keys or issue_api_key. Requires admin.
• +7 more on the listing page

MCP Atlassian tools

No tool names declared yet. Check the project README from the listing page.