MCP connections
Give your AI client tools to search Jira issues and read Confluence pages.
Model Context Protocol (MCP) connects an AI client to external tools. Use MCP Atlassian to connect your client to UC San Diego's Jira and Confluence.
The client starts one local process that serves both products. You configure the connection once per client, independently of its model-provider configuration.
Start here
- Install the server and create your credentials.
- Add the configuration for your client.
- Check both connections with a search and a page read.
Claude Code
Register the local server from the terminal.
Claude Desktop
Add a local server to the desktop chat app.
Codex
Use the shared app, CLI, and IDE configuration.
OpenCode
Choose the configuration for OpenCode 1.x or 2.x.
Cline
Configure the server in the IDE extension.
What the connection provides
The setup starts with four read-only tools:
| Tool | Purpose |
|---|---|
jira_search | Find issues with Jira Query Language (JQL). |
jira_get_issue | Read an issue by its key. |
confluence_search | Find pages with text or Confluence Query Language (CQL). |
confluence_get_page | Read a page by its ID or URL. |
Jira and Confluence enforce your account's access. Tool results enter the AI client's context, so use an approved client and model for the information you retrieve.
To enable updates, see Allow selected write tools.
How this setup works
These guides use the open-source MCP Atlassian server with local stdio transport. The client launches the process and communicates through standard input and output. No listening port is required.
The examples pin mcp-atlassian==0.23.0, the version checked for this guide. Client configuration examples cover macOS and native Windows. The Windows and WSL notes explain which paths to use for a Linux-based setup.