Provides tools for managing Jira issues, comments, workflows, time tracking, and project configuration via the Jira API, with support for multi-instance routing, Atlassian Document Format (ADF) conversion, task caching, and comment templates.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@jira-mcp update task PROJ-123 status to In Progress"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Two MCP servers for Atlassian Cloud: Jira and Confluence. One configuration, one API token, separate tool lists.
Package | What it does | Docs |
Jira: sync, search, comment, transition, log time, reassign, create and delete issues | ||
Confluence Cloud: pages, blog posts, footer and inline comments, labels, attachments, restrictions, whiteboards | ||
| Shared config, ADF conversion, HTTP transport, MCP envelope. Not published — bundled into both servers at build time | — |
Related MCP server: Jira MCP Server
One Atlassian site serves both products from the same host with the same API token, so they share a configuration file and a transport layer. They do not share a tool list.
Merging them would put near-homonyms in one list: search_tasks beside search_pages, get_task_details beside get_page, add_task_comment beside add_page_comment. That measurably worsens tool selection, and the failure is silent — the wrong tool returns a plausible answer about the wrong product. packages/core/tests/tool-name-collisions.test.ts asserts the two lists never overlap.
Install whichever you need, or both.
npm install -g @softspark/jira-mcp @softspark/confluence-mcpjira-mcp config init
jira-mcp config set-credentials # shared by both servers
jira-mcp config add-project KAN https://your-site.atlassian.net
confluence-mcp space add DOCS https://your-site.atlassian.netRegister in an MCP client:
{
"mcpServers": {
"jira": { "command": "jira-mcp" },
"confluence": { "command": "confluence-mcp" }
}
}All state lives in ~/.softspark/jira-mcp/, the standard config directory for SoftSpark tools. The directory keeps its original name: renaming it would orphan every existing installation.
npm install # links the workspace
npm run typecheck # tsc across all packages
npm run lint
npm test # one run across the whole workspace
npm run test:coverage # 70% gate
npm run build # builds both published packagesTests run workspace-wide on purpose. core has no consumers of its own, so a change there is only meaningful if both servers still pass; a per-package run would let a core change break a server with no single command noticing.
Pre-commit gate:
npm run typecheck && npm run lint && npm test && npm run buildCHANGELOG — shared; both packages release together under one version.
kb/reference/ — architecture, api, adf, caching, configuration, templates, confluence.
kb/howto/ — setup, multi-instance, cli-usage.
kb/procedures/ — sop-pre-commit, sop-release, sop-post-release-testing.
See CONTRIBUTING, SECURITY and the Code of Conduct.
This server cannot be deployed
MCP server for Support & Service Management
MCP Server for JFrog, providing tools for development and artifact management.
MCP server for Product Management