The Confluence connector.
Wiki pages, spaces and comments. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Confluence exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Confluence defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Confluence tool
5 tools, named as the agent sees them.
- search_pagesread
Search Confluence with CQL, e.g. 'type=page AND text ~ "onboarding"' or 'space=ENG AND lastmodified > now("-7d")'. The main entry point — returns page ids to pass to get_page.
- get_pageread
Get one page with its body flattened to plain text. Takes a page id from search_pages, list_child_pages, or a space listing.
- list_spacesread
List Confluence spaces with their keys. Use it to find the space key or id that narrows a search_pages CQL query.
- list_child_pagesread
List the direct children of a page. Use it to walk a documentation tree downward from a parent found via search_pages.
- list_page_commentsread
List a page's footer comments with each body flattened to plain text — the discussion thread on a doc.
Use it from any agent
The same Confluence tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Atlassian API Token in your Confluence account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Confluence once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.