Confluence MCP Server for Cursor IDE: Let Your AI Read & Write Docs (2026)
Set up the Confluence MCP server in Cursor so your AI can search, read, and edit Confluence pages without switching apps. Works with Confluence Cloud and Data Center.
Confluence MCP Server Cursor IDE Setup 2026
Confluence is where your team documents everything — architecture decisions, runbooks, project specs. The Confluence MCP server lets Cursor IDE read and write to your Confluence spaces without leaving your editor. This guide covers the full setup for 2026.
What the Confluence MCP Server Does
With the Confluence MCP server connected to Cursor, you can:
This is especially powerful when writing code that needs to match documented architecture — your AI has context, not just your local files.
Prerequisites
Before you start, make sure you have:
Step 1: Generate Your Confluence API Token
1. Log into your Atlassian account at id.atlassian.com
2. Click your profile avatar → Manage account
3. Go to Security → Create and manage API tokens
4. Click Create API token
5. Label it something like cursor-mcp-2026
6. Copy the token — you won't see it again
Your base URL will be your Atlassian domain: https://yourcompany.atlassian.net
Step 2: Install the Confluence MCP Server
The recommended package is @atlassian/mcp-confluence or the community confluence-mcp-server. Install globally:
npm install -g @modelcontextprotocol/server-confluence
Or use the Atlassian-maintained version:
npm install -g confluence-mcp-server
Test the installation:
confluence-mcp-server --help
Step 3: Configure Cursor IDE
Open Cursor's MCP settings. Go to Settings → MCP (or press Cmd+Shift+P → "Open MCP Settings").
Add the Confluence server to your mcp.json config:
{
"mcpServers": {
"confluence": {
"command": "npx",
"args": ["-y", "confluence-mcp-server"],
"env": {
"CONFLUENCE_BASE_URL": "https://yourcompany.atlassian.net",
"CONFLUENCE_USERNAME": "your-email@company.com",
"CONFLUENCE_API_TOKEN": "your-api-token-here",
"CONFLUENCE_SPACE_KEY": "ENG"
}
}
}
}
Replace the values with your actual credentials. CONFLUENCE_SPACE_KEY is optional — omit it to access all spaces.
Step 4: Verify the Connection
Restart Cursor after saving the config. In the chat panel, type:
List my Confluence spaces
Or:
Search Confluence for "deployment process"
If Cursor returns real results from your knowledge base, you're connected.
Step 5: Real-World Usage Patterns
Pull context before writing code
Before I write the authentication module, find the auth architecture doc in Confluence and summarize the key decisions
Generate and push documentation
I just finished building the webhook service. Create a Confluence page in the ENG space called "Webhook Service Architecture" documenting how it works based on the code in /src/webhooks/
Cross-reference specs
Find the product spec for the checkout flow in Confluence and compare it against the current implementation in /src/checkout/
Update runbooks
Update the "Deployment Runbook" page in Confluence to include the new environment variable FEATURE_FLAG_API_KEY that we added today
Troubleshooting Common Issues
"Authentication failed" error
Double-check your API token was copied correctly with no trailing spaces. Also verify your username is the email address tied to your Atlassian account, not a display name.
"Space not found" error
Your space key needs to match exactly. Find it in Confluence under Space Settings → Space Details. It's usually all caps like ENG, PROD, or WIKI.
"Rate limit exceeded"
Confluence Cloud rate limits API calls. If you're hitting limits, add a small delay between bulk operations or upgrade to a higher Atlassian tier.
MCP server not showing in Cursor
Make sure Node.js is in your PATH. Run which node in terminal to verify. If Cursor launched before Node was installed, fully restart it.
Using with Jira MCP Together
Confluence and Jira work best together. If you've already set up the Jira MCP server, you can chain them:
Find the Jira ticket PROJ-1234, read the attached Confluence spec, then implement the feature described
This gives Cursor full context: the ticket requirements plus the detailed spec — exactly what a senior dev would read before coding.
Advanced: Atlassian MCP Bundle
Atlassian maintains a unified MCP server that covers Jira, Confluence, and Bitbucket in one package. See the Atlassian MCP setup guide for instructions on running all three from a single config entry.
Summary
The Confluence MCP integration turns your documentation from a read-only reference into an active part of your development workflow. Cursor can now search, read, and write Confluence pages as part of any coding task — closing the gap between what's documented and what's built.
Setup takes about 10 minutes. The main requirement is an API token with appropriate space permissions. Once connected, the most common use case is having Cursor pull spec docs before writing features — which alone saves significant back-and-forth.