Confluence MCP connector
Connect Confluence to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can search, read, create, and update Confluence pages, spaces, and attachments inside each person's own access, with every action logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
19 tools
How to connect
How to connect Confluence to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Confluence once
-
Open Connections, choose Add connection, and pick Confluence.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Confluence. Confluence's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Confluence MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Confluence MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Confluence MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Confluence to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Confluence through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Find the answer before the customer waits
Ask for the runbook or troubleshooting page that covers a customer's problem and get the relevant section back, without opening five spaces to find it.
-
Product
Draft the spec page after the meeting
Turn meeting notes into a new page in the right Confluence space, with the standard headings and labels the team already uses.
-
Engineering
Keep the runbook current after an incident
Update the on-call page with what actually happened and what changed, so the next engineer reads the fix and not last quarter's version.
-
HR
Answer policy questions from the handbook
Ask what the parental leave or expense policy says and get the answer with a link to the page it came from, instead of forwarding the question to HR.
-
IT
Review who has access to which spaces
List Confluence users and groups, see who belongs where, and remove someone from a group when their role changes.
-
Operations
Pull together what several pages say
Search across spaces for everything written about a vendor, process, or project and get a short summary with the pages it drew from.
Try asking
- “Summarize pages updated in the Engineering space this week.”
- “Which Confluence spaces have no pages created this month?”
- “Draft a release notes page in the Product space.”
Compare
Elaichi vs Zapier MCP vs Composio for Confluence
All three can connect Confluence to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Confluence tools | Allow or restrict single Confluence tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Confluence call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Confluence tools for your AI agents
19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Confluence, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Confluence gets you
6 screens from the product, each doing one job for your Confluence account.
The agent
Ask about Confluence pages, get real answers.
Type a question in plain language and read it back from live Confluence pages.
- pages
- spaces
- groups
- users
Ask Elaichi to work across your apps.
Summarize pages updated in the Engineering space this week.
Which Confluence spaces have no pages created this month?
Draft a release notes page in the Product space.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Confluence.
One governed MCP endpoint for Confluence, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
19 Confluence tools are wired and ready.
Pages, spaces, groups, users and search, with no custom code to write.
- List all Confluence users
- Get single Confluence user by ID
- List all Confluence accessible resources
- List all Confluence groups
ElaichiToolsToolboxes
Every team gets its own Confluence toolbox.
Curate one toolbox per team and scope it to the Confluence work they do.
- Engineering
- Product
- Support
- People Ops
ElaichiToolboxesShared connections
Teammates use Confluence without seeing a token.
See who connected each Confluence account and which teams and members share it.
- Engineering
- Product
- Support EMEA
- People Ops
ElaichiConnectionsAudit log
Every Confluence call is on the record.
When, who, what happened, type and resource for each Confluence page and space touched.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule ships a Confluence digest, not a chat.
Fetch pages, group them, draft a digest, get approval, post back to Confluence.
Confluence digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch pages
Confluence
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Confluence
Queued
Collections and dashboards
Confluence page numbers arrive without being asked.
Four metrics, 14 days of pages created and a team breakdown, refreshed on schedule.
Confluence health
Refreshed 4 minutes ago · every 15 minutes · from the pages collection
Pages
1,284 ↓ 12%
Spaces
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Pages created
Last 14 days
By team
Share of activity
Engineering 34%
Product 27%
Support EMEA 21%
People Ops 18%
FAQ
Frequently asked questions
How do I connect Confluence to Claude?
Two steps. In Elaichi, choose Confluence and sign in with your Atlassian account, which connects over OAuth, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it can work with your Confluence pages and spaces.
Does Confluence work with ChatGPT and Cursor as well as Claude?
Yes. Once Confluence is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Confluence once and every client you use gets it.
What can an AI agent actually do with my Confluence data?
With Confluence connected, an agent can search across your spaces, read pages and their attachments, create new pages, and update existing ones. It can also list spaces, labels, users, and groups, remove someone from a group, and read the Confluence audit log. It cannot delete pages or spaces through this connector.
Does connecting Confluence give the AI access to every space?
No. An agent only sees the Confluence spaces and pages the signed-in person can already open, because every call runs as that person, and Confluence's own space permissions and page restrictions still apply. Elaichi can narrow that further, for example to reading only, but it can never widen what someone is allowed to see in Confluence.
Can I stop an agent from changing pages or groups in Confluence?
Yes. In Elaichi you restrict each Confluence action separately, so you can allow searching and reading while blocking page updates, page creation, or removing members from groups. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can trigger it.
What happens to a Confluence connection when someone leaves?
When you offboard a person in Elaichi, their access to Confluence through every AI client ends at once. If they had shared a Confluence connection with a team, it keeps working for everyone else. If you want to remove Confluence entirely, disconnecting it once in Elaichi removes it from every client at the same time.
Does the Confluence MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Confluence is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Confluence?
Yes. Both let Claude, ChatGPT or Cursor use Confluence. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Confluence call.
How is Elaichi different from Composio for Confluence?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Confluence: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Confluence in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.