Jira & Confluence MCP Server
Provides tools for searching, creating, updating Confluence pages, adding comments, and checking permissions.
Provides tools for searching, creating, updating, and transitioning Jira issues, as well as managing comments and workflow transitions.
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 & Confluence MCP Server Find open issues assigned to me in Jira."
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.
Jira & Confluence MCP Server
A Model Context Protocol (MCP) server that connects AI assistants to Jira and Confluence.
Features
π Search & View - Query Jira issues with JQL and Confluence pages with CQL
βοΈ Create & Edit - Add new issues and pages, update existing content
π¨ Rich Formatting - Automatically converts AI-generated Markdown to ADF (Atlassian Document Format) for beautiful, native-looking content in Jira and Confluence
π Safe Operations - No delete operationsβread-heavy with controlled write access
π Easy Setup - One-command integration with OpenCode, GitHub Copilot, Claude Desktop, and more
π Secure - Uses Atlassian API tokens with optional TLS configuration for corporate networks
Related MCP server: MCP Atlassian
AI Agent Skill
Installation
Copy and paste this prompt to your LLM agent (Claude Code, AmpCode, Cursor, etc.):
Install and configure the Jira & Confluence CLI agent skill by following the instructions here:
https://raw.githubusercontent.com/thamaraiselvam/mcp-jira-confluence/main/docs/agent-skill-setup.mdMCP Server
Add to OpenCode CLI
Quick Add (Interactive - Recommended)
Use OpenCode's interactive MCP add command:
opencode mcp addThen follow the prompts:
β Add MCP server
β
β Enter MCP server name
β jira-confluence
β
β Select MCP server type
β Local
β
β Enter command to run
β npx mcp-jira-confluenceAfter adding, edit ~/.config/opencode/opencode.json to add your credentials:
{
"mcp": {
"jira-confluence": {
"type": "local",
"command": ["npx", "mcp-jira-confluence"],
"environment": {
"ATLASSIAN_URL": "https://your-org.atlassian.net",
"ATLASSIAN_EMAIL": "your.email@example.com",
"ATLASSIAN_API_TOKEN": "your-api-token",
"IGNORE_TLS_ERRORS": "true"
}
}
}
}Get your API token from Atlassian API Tokens.
Manual Configuration
Create or edit ~/.config/opencode/opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jira-confluence": {
"type": "local",
"command": ["npx", "mcp-jira-confluence"],
"environment": {
"ATLASSIAN_URL": "https://your-org.atlassian.net",
"ATLASSIAN_EMAIL": "your.email@example.com",
"ATLASSIAN_API_TOKEN": "your-api-token",
"IGNORE_TLS_ERRORS": "true"
}
}
}
}Get your API token from Atlassian API Tokens.
Usage in OpenCode
After configuration, use natural prompts to interact with Jira and Confluence:
Search and Query:
Show me all high-priority bugs in the AUTH project
What are the open issues assigned to me in Jira?
Search Confluence for API documentation in the DEV spaceView and Analyze:
Get details of issue PROJ-123
Show me the latest comments on PROJ-456
What's in the "Architecture Decisions" Confluence page?Create and Update:
Create a new bug in Jira: The login page shows a 500 error when...
Update PROJ-789 to mark it as in progress
Add a comment to PROJ-101: "Fixed in latest deployment"Workflow:
What transitions are available for PROJ-234?
Move PROJ-567 to Done statusThe AI will automatically use the Jira and Confluence tools when it detects you're asking about issues, projects, or documentation.
Other MCP Clients
GitHub Copilot CLI
Create or edit ~/.config/github-copilot/mcp.json:
{
"mcpServers": {
"jira-confluence": {
"command": "npx",
"args": ["mcp-jira-confluence"],
"env": {
"ATLASSIAN_URL": "https://your-org.atlassian.net",
"ATLASSIAN_EMAIL": "your.email@example.com",
"ATLASSIAN_API_TOKEN": "your-api-token",
"IGNORE_TLS_ERRORS": "true"
}
}
}
}Claude Desktop & VS Code
Same configuration format. For Claude Desktop, edit your Claude config file. For VS Code, add to .vscode/mcp.json.
Connect to Running Server
If you prefer to run the server manually, use this configuration:
{
"mcpServers": {
"jira-confluence": {
"type": "http",
"url": "http://127.0.0.1:9339/mcp"
}
}
}Quick Start (Manual Usage)
If you prefer to run the server manually instead of auto-starting:
Create
.envfile in your home directory or project root:
# ~/.env or current directory
ATLASSIAN_URL=https://your-org.atlassian.net
ATLASSIAN_EMAIL=your.email@example.com
ATLASSIAN_API_TOKEN=your-api-token
IGNORE_TLS_ERRORS=trueGet your API token from Atlassian API Tokens.
Run with npx:
npx mcp-jira-confluenceServer runs on http://127.0.0.1:9339 by default.
Available Tools
Confluence
search_confluence- Search pages with CQLget_confluence_page- Read page contentcreate_confluence_page- Create pages from Markdownupdate_confluence_page- Update pages from Markdownadd_confluence_comment- Add commentsget_confluence_page_versions- Read version historycheck_confluence_permissions- Check permissions
Jira
jira_search- Search issues with JQLjira_get_issue- Read issue detailsjira_create_issue- Create issues from Markdownjira_update_issue- Update issue fieldsjira_transition_issue- Change workflow statusjira_get_transitions- List available transitionsjira_add_comment- Add a Markdown comment to an issuejira_update_comment- Update an existing comment on an issue
CLI Usage
The same package also ships a command-line interface, so you can drive Jira and Confluence straight from a terminal, a shell script, or a Claude skill β without an MCP client. Every MCP tool above has a matching CLI command, grouped under jira and confluence.
The CLI shares the single mcp-jira-confluence entry point β there is no separate executable. Invoke it as <entry> <group> <command>, where <group> is jira or confluence. With no group, the same entry point starts the MCP server instead.
It reads the same environment variables as the server (ATLASSIAN_*, or service-specific JIRA_* / CONFLUENCE_*). Set them in your shell or a .env file.
Run it with npx (no install needed):
npx -y mcp-jira-confluence@latest --helpInstalled the package globally (
npm install -g mcp-jira-confluence@latest)? Drop thenpx -y β¦@latestprefix and callmcp-jira-confluence <group> <command>directly. The examples below use the npx form.
# List all command groups and commands
npx -y mcp-jira-confluence@latest --help
# Per-command help (shows required/optional arguments)
npx -y mcp-jira-confluence@latest jira create-issue --help
# --- Jira ---
npx -y mcp-jira-confluence@latest jira search --jql "status = 'In Progress'" --limit 10
npx -y mcp-jira-confluence@latest jira get-issue PROJ-123
npx -y mcp-jira-confluence@latest jira create-issue \
--projectKey PROJ --issueType Story \
--summary "New story" --description ./description.md \
--priority High --labels "backend,urgent"
# Update plain fields as JSON, and/or the description from a Markdown file:
npx -y mcp-jira-confluence@latest jira update-issue PROJ-123 --fields '{"summary":"Updated title"}'
npx -y mcp-jira-confluence@latest jira update-issue PROJ-123 --descriptionFile ./description.md
npx -y mcp-jira-confluence@latest jira transition-issue PROJ-123 "In Progress"
npx -y mcp-jira-confluence@latest jira get-transitions PROJ-123
npx -y mcp-jira-confluence@latest jira add-comment PROJ-123 ./comment.md
npx -y mcp-jira-confluence@latest jira update-comment PROJ-123 100042 ./comment.md
# --- Confluence ---
npx -y mcp-jira-confluence@latest confluence search --cql "type=page AND title~'Roadmap'"
npx -y mcp-jira-confluence@latest confluence get-page 12345
npx -y mcp-jira-confluence@latest confluence create-page \
--spaceKey ENG --title "Design Notes" --markdownContent ./notes.md
npx -y mcp-jira-confluence@latest confluence update-page 12345 "New Title" ./notes.md
npx -y mcp-jira-confluence@latest confluence add-comment 12345 ./comment.md
npx -y mcp-jira-confluence@latest confluence get-page-versions 12345 --limit 5
npx -y mcp-jira-confluence@latest confluence check-permissionsNotes:
Arguments can be passed as named flags (
--summary "...") or as positionals in the order shown by--help.Markdown rich-text content is supplied as a path to a Markdown file, not as an inline string β this keeps multi-line content reliable across shells. This applies to: Confluence
create-page/update-pagebodies andadd-comment; Jiracreate-issuedescription,add-comment/update-comment, andupdate-issue --descriptionFile. (BREAKING: inline Markdown for these arguments is no longer accepted.)update-issuetakes a JSON--fieldsobject for plain fields and/or a--descriptionFilefor the description (the file wins if both set a description); at least one is required.Markdown is converted exactly as the MCP server does β to HTML for Confluence and to ADF for Jira. The file's raw Markdown is passed to the API layer, which performs the conversion.
Add
--jsonto any command to print the raw result as JSON for scripting; the default is a human-readable summary.Commands exit
0on success and non-zero on any failure (missing argument, missing config, or API error).Like the MCP server, the CLI has no delete operations.
Configuration
Optional Variables
# Custom port (default: 9339)
MCP_PORT=8080
# Service-specific credentials (overrides ATLASSIAN_*)
CONFLUENCE_URL=https://your-confluence.atlassian.net
CONFLUENCE_API_TOKEN=confluence-token
JIRA_URL=https://your-jira.atlassian.net
JIRA_API_TOKEN=jira-token
# Project/Space scoping
CONFLUENCE_SPACE_KEY=MYSPACE
JIRA_PROJECT_KEY=PROJ
# Corporate network
IGNORE_TLS_ERRORS=true
# Debug logging
VERBOSE=trueNote: When using the command configuration approach, set variables in the env object. When running manually with npx, use a .env file.
Troubleshooting
Manual Testing
Run the server manually to test your configuration:
npx mcp-jira-confluenceCheck server health:
curl http://127.0.0.1:9339/healthCommon Issues
Connection refused: Check VPN/proxy and URLs in your configuration
TLS errors: Add
"IGNORE_TLS_ERRORS": "true"to theenvobjectAuthentication errors: Verify your API token at Atlassian API Tokens
Development
Clone and validate:
git clone https://github.com/thamaraiselvam/mcp-jira-confluence
cd mcp-jira-confluence
npm install
npm run build
npm run validateLicense
MIT
Available Tools
15 toolsadd_confluence_commentB
Add an inline comment to an existing Confluence page. REQUIRED: Always provide Markdown content. Supports bold, italic, links, and basic formatting. Content is automatically converted to Confluence storage format (HTML).
Inputs: pageId (required), markdownContent (required).
check_confluence_permissionsA
Check whether the configured API token is valid and has the required permissions. Validates authentication, read/search access, and optionally write access to a specific page.
Inputs: pageId.
create_confluence_pageA
Create a new Confluence page in a given space. REQUIRED: Always provide Markdown content. Supports headers, lists, bold, italic, code blocks, tables, links, images, and more. Content is automatically converted to Confluence storage format (HTML). Optionally nest the page under a parent page.
Inputs: title (required), spaceKey (required), markdownContent (required), parentPageId.
get_confluence_pageB
Read a Confluence page by its ID. Returns the page title, space, version, URL, and full body content in Confluence storage format (HTML).
Inputs: pageId (required).
get_confluence_page_versionsB
Get the version history of a Confluence page. Returns a list of versions with author, timestamp, and optional version message.
Inputs: pageId (required), limit.
jira_add_commentB
Add a new comment to a Jira issue (Story, Bug, Task, etc.) by its key or numeric ID. REQUIRED: Always provide a Markdown-formatted comment body. Use headers (# ## ###), lists (*, -), bold (text), italic (text), code (code), links (text), tables, blockquotes (>), and horizontal rules (---). Automatically converted to Atlassian Document Format (ADF) for Jira Cloud.
Inputs: issueIdOrKey (required), markdownBody (required).
jira_create_issueA
Create a new Jira issue (Story, Bug, Task, etc.) in a given project. New issues are created unassigned by default. REQUIRED: Always provide a markdown-formatted description.
Inputs: summary (required), issueType (required), projectKey (required), description (required), +3 more.
jira_get_issueA
Get full details of a single Jira issue by its key (e.g. 'PROJ-123') or numeric ID. Returns summary, status, type, priority, assignee, reporter, description, labels, and timestamps.
Inputs: issueIdOrKey (required).
jira_get_transitionsA
List all available workflow transitions for a Jira issue. Use this to discover valid transition names before calling jira_transition_issue.
Inputs: issueIdOrKey (required).
jira_searchB
Search Jira issues using a JQL (Jira Query Language) query string. Returns a list of matching issues with key details including status, assignee, priority, and description.
Inputs: jql (required), limit, startAt.
jira_transition_issueA
Change the status of a Jira issue by performing a workflow transition. Accepts either a transition name (e.g. 'In Progress', 'Done') or a numeric transition ID. Use jira_get_issue to see the current status first.
Inputs: transition (required), issueIdOrKey (required).
jira_update_commentA
Update the body of an existing comment on a Jira issue. Identify the comment by the issue key/ID and the comment ID (returned by jira_add_comment). REQUIRED: Always provide the new Markdown-formatted comment body. Automatically converted to Atlassian Document Format (ADF) for Jira Cloud. Note: comments cannot be deleted through this server.
Inputs: commentId (required), issueIdOrKey (required), markdownBody (required).
jira_update_issueA
Update one or more fields on an existing Jira issue. Provide only the fields you want to change. When updating description, ALWAYS use Markdown format. Supports summary, description (Markdown format), assignee (accountId), priority, labels, and any other valid Jira field.
Inputs: fields (required), issueIdOrKey (required).
search_confluenceC
Search Confluence pages using a CQL (Confluence Query Language) query string.
Inputs: cql (required), limit.
update_confluence_pageB
Update an existing Confluence page. REQUIRED: Always provide Markdown content. Supports headers, lists, bold, italic, code blocks, tables, links, images, and more. Content is automatically converted to Confluence storage format (HTML). Automatically handles version bumping.
Inputs: title (required), pageId (required), markdownContent (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 15 tools
Every tool has a clearly distinct resource+action target, and the Confluence/Jira split is reinforced by consistent naming. The only mild adjacency is jira_update_issue vs jira_transition_issue, but the descriptions make the workflow-transition distinction explicit.
Jira tools use a uniform 'jira_verb_noun' prefix pattern, but Confluence tools use a suffix form (search_confluence, get_confluence_page, add_confluence_comment), so the two families follow different conventions. Each family is internally readable, but the set as a whole mixes styles.
15 tools split cleanly across two products (8 Jira, 7 Confluence) is well-scoped for a combined server. Each tool covers a distinct operation with no filler.
Core lifecycle is covered for both domains: search/get/create/update plus comments and transitions for Jira, and search/get/create/update/comments/versions/permissions for Confluence. Gaps remain around deletes (no Jira or Confluence delete, and comments explicitly cannot be deleted) and Jira attachment/sprint operations, but these are workable omissions.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yoβ¦
Official Fibery MCP server: query and update your workspace from any AI client via OAuth.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseAqualityFmaintenanceA Model Context Protocol server that enables AI assistants to interact with Confluence content, supporting operations like retrieving, searching, creating, and updating pages and spaces.913MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that integrates with Atlassian Confluence and Jira, enabling AI assistants to search, create, and update content in these platforms through natural language interactions.1MIT
- -licenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables interaction with Atlassian products (Confluence and Jira), supporting both Cloud and Server/Data Center deployments for searching, creating, and managing content through natural language.-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that integrates with Atlassian's Jira and Confluence, enabling AI assistants to interact with these tools directly through features like issue management, page creation, and content search.131MIT