Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Jira Service Management (BYOK) — connector documentation

  • MCP endpoint: https://byok-jira-service-management.connectorbay.com/mcp
  • REST API: POST https://byok-jira-service-management.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-jira-service-management.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Jira Service Management Atlassian account email, sent in the X-Upstream-Key header and the Atlassian API token in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-jira-service-management.connectorbay.com/health · Tool schemas: https://byok-jira-service-management.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-jira-service-management · agent@connectorbay.com

What Jira Service Management (BYOK) is for

Jira Service Management (BYOK) lets an AI assistant read your own Jira Service Management data through the Jira Service Management API with a key you supply (Atlassian account email). Read-only: 10 tools (get_info, list_service_desks, list_queues, list_queue_requests, list_customer_requests, get_customer_request, list_request_comments, list_request_slas, list_request_types, search_knowledge_base). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.atlassian.net. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Jira Service Management. Jira Service Management and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Jira Service Management version does my site run?"
  • "Which service desks do we have in Jira Service Management?"
  • "What queues does service desk 1 have and how many requests are in each?"
  • "Show me the requests in queue 10 of service desk 1"
  • "What open customer requests does service desk 1 have?"
  • "Show me service desk request HELP-42"

What it does

  • get_info: Show the version and build of the Jira Service Management instance and whether it is licensed for use.
  • list_service_desks: List the service desks (help portals) you can access with project key, name and type.
  • list_queues: List the agent queues of one service desk with their JQL; set include_count for the number of requests in each queue.
  • list_queue_requests: List the requests inside one queue of a service desk; only the fields the queue is configured to show are returned.
  • list_customer_requests: List customer requests visible to the key's user, most recent activity first, filtered by service desk, request type, status or summary text.
  • get_customer_request: Get one customer request by issue key or id with its status, request type, reporter and creation date.
  • list_request_comments: List the comments of a customer request (public and internal) with author, text and time.
  • list_request_slas: List the SLA timers of a customer request with ongoing and completed cycles and whether they breached.
  • list_request_types: List the request types (the forms customers can raise) of a service desk with name, description and group ids.
  • search_knowledge_base: Search the knowledge base linked to a service desk; returns title and excerpt of matching articles.

BYOK key

You bring your own Jira Service Management Atlassian account email (https://id.atlassian.com/manage-profile/security/api-tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.atlassian.net over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Jira Service Management API (*.atlassian.net) with a BYOK key; documentation: https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Jira Service Management. Jira Service Management and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Jira Service Management account.

Built for: Worldwide. Languages: English.