Is this an official Jira Service Management MCP server?

No. It is Memtro's MCP server with Memtro's Jira Service Management connector behind it: the connector reads Jira Service Management through its API with the credentials you connect on Dashboard → Connections, and Jira Service Management publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Jira Service Management?

Not yet. Today every Jira Service Management tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Support

Jira Service Management MCP server

Jira Service Management in any MCP client, through Memtro: Jira Service Management does not publish this server. Memtro's Jira Service Management connector reads Jira Service Management through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only IT and customer service desk: browse service desks, queues and request types, search and read requests with comments and SLA state, and look up customer organisations.

Reads

jiraservice_desksService desks (projects) with their queues (and issue counts) and request types.
jiraservice_requestsCustomer requests on a desk: open, closed or all, optionally one request type or organisation, with Jira Service Management's text search.
jiraservice_requestOne request by key (e.g. ITS-123): summary, description, status, reporter, participants, SLA cycles…
jiraservice_queueIssues currently in one queue of a desk (queue id or name, e.g. 'Unassigned issues', 'Waiting for support'), with status, priority…
jiraservice_organizationsCustomer organisations on a desk; with organization_id, the people in that organisation.

Connect it

First connect Jira Service Management on Dashboard → Connections, then add Memtro to your client once. The Jira Service Management tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Jira Service Management connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What is waiting for support on the IT desk?
› Has anything breached its SLA today?
› Show me ITS-412 with the latest comments
› Which requests did Acme Ltd raise this month?

Questions

Is this an official Jira Service Management MCP server?: No. It is Memtro's MCP server with Memtro's Jira Service Management connector behind it: the connector reads Jira Service Management through its API with the credentials you connect on Dashboard → Connections, and Jira Service Management publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Jira Service Management?: Not yet. Today every Jira Service Management tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.