
Connects Claude to Jira through Pipeworx's gateway with four core operations: JQL search across issues, full issue retrieval by key, project listing, and project details lookup. You get issue metadata like status, assignee, priority, comments, and linked issues. Worth noting the ask_pipeworx wrapper that translates natural language questions into the right tool calls automatically. Uses streamable HTTP transport, so no local server management. Part of a larger 673+ source gateway, but this pack isolates just the Jira functionality if that's all you need. Good fit when you want Claude to query tickets, check sprint status, or pull project context without leaving the conversation.
Jira MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
jira_search | Search Jira issues using JQL queries. Returns issue keys, summaries, status, assignee, and priority. Use to find tasks by project, status, assignee, or custom criteria. |
jira_get_issue | Get full details for a Jira issue by key (e.g., 'PROJ-123'). Returns description, status, assignee, priority, comments, attachments, and linked issues. |
jira_list_projects | List all accessible Jira projects. Returns project keys, names, descriptions, and types. Use before searching to discover available projects. |
jira_get_project | Get details for a specific Jira project by key (e.g., 'PROJ') or ID. Returns name, description, lead, issue types, and custom fields. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"jira": {
"url": "https://gateway.pipeworx.io/jira/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/jira/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Jira data" })
The gateway picks the right tool and fills the arguments automatically.
MIT