Data as of
MCP Atlassian for Cursor: Setup & Config
MCP Atlassian connects Cursor to Jira and Confluence for issue tracking and team documentation.
MCP Atlassian Cursor configuration
Choose Cursor configuration scope
For MCP Atlassian, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.
Add MCP Atlassian to Cursor
Use the mcp-atlassian entry below in mcpServers. Keep MCP Atlassian's documented stdio connection fields and your other Cursor entries.
Check MCP Atlassian in Cursor
MCP Atlassian: Enable in Cursor’s MCP settings; inspect tools.
Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "<your Jira instance URL>",
"JIRA_USERNAME": "<your Jira account email>",
"JIRA_API_TOKEN": "<your Jira Cloud API token>",
"CONFLUENCE_URL": "<your Confluence instance URL>",
"CONFLUENCE_USERNAME": "<your Confluence account email>",
"CONFLUENCE_API_TOKEN": "<your Confluence Cloud API token>"
}
}
}
}MCP Atlassian in Cursor: stdio checks
- Cursor must find uvx mcp-atlassian (from uv, for Python tools) for MCP Atlassian. Enable the project/user entry in MCP settings and inspect its tools.
- Review CONFLUENCE_API_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, JIRA_API_TOKEN, JIRA_URL, JIRA_USERNAME for MCP Atlassian before sharing project .cursor/mcp.json; project scope travels with the repository.
- MCP Atlassian uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Tools
- jira_search, jira_get_issue, jira_create_issue
MCP Atlassian — details. Cursor guide
Frequently asked questions
Cursor's MCP Atlassian entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.
Cursor's mcp-atlassian example uses stdio.
MCP Atlassian's Cursor configuration invokes uvx mcp-atlassian (from uv, for Python tools).
Cursor's MCP Atlassian example references CONFLUENCE_API_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, JIRA_API_TOKEN, JIRA_URL, JIRA_USERNAME. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.
MCP Atlassian's stored list contains 10 tools, including jira_search, jira_get_issue, jira_create_issue. Compare those names with Cursor's connected tool list; the stored list is not a live check.