Provider REST API

Knowledge

Connect Claude to Confluence

Search the wiki, read pages, publish and revise documentation. Toolspoke puts 10 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connection
Provider REST API
Authentication
Atlassian API token
Actions exposed
10
Cost per call (typical)
1 credit
Adapter
Maintained by Toolspoke

Connected in three steps

  1. 1

    Install Confluence

    Open the marketplace in your workspace, add Confluence to the project your agents work in, and it appears on the gateway immediately.

  2. 2

    Connect the credential

    Authenticate with atlassian api token. Where to get one, and what it has to be able to reach, is the next section.

  3. 3

    Point your agent at the gateway

    Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json
{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Confluence shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code

Run it in your project, then /mcp to sign in

claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop

Settings, then Connectors, then Add custom connector

https://toolspoke.com/mcp
Cursor

~/.cursor/mcp.json, or .cursor/mcp.json for one project

{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex

~/.codex/config.toml

[mcp_servers.toolspoke]
url = "https://toolspoke.com/mcp"
VS Code

.vscode/mcp.json, or the MCP: Add Server command

{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Confluence asks for

Atlassian API token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Atlassian site nameRequired
Just the subdomain. For https://acme.atlassian.net/wiki this is acme.
acme
Email and API tokenRequired
Your Atlassian account email, a colon, then an API token from id.atlassian.com → Security → API tokens. Sent as HTTP Basic. The token inherits your own Confluence permissions, so create it on an account that can read the spaces this connection should reach.
[email protected]:ATATT3xFfGF0…

What Claude can do in Confluence

10 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads
7Reads
Writes
3Writes
Destructive
0Destructive

Reads

7

Fetches data and changes nothing.

  • search_pages

    Search the whole site with CQL, Confluence's query language, and return matching content with a short excerpt and its id. This is the only full-text search Confluence offers, and the starting point when you know what a page says but not where it lives; use list_pages instead when you already know the space and only want its contents listed. CQL examples: "type = page AND text ~ 'onboarding'", "space = ENG AND lastModified > now('-14d')", "title ~ 'runbook' AND type = page". Take the id from a result and call get_page for the body. This one action reaches the v1 API at /wiki/rest/api/search, because REST v2 has no search endpoint.

  • list_pages

    List pages, newest changes first when you sort that way, optionally restricted to one space. Returns ids, titles and status but no body unless you ask for one. Use it to walk a space you already know - call list_spaces for the space_id first - and search_pages when you need full-text matching instead. Paging is by the opaque cursor returned in the previous response.

  • get_page

    Fetch one page with its body and its current version number. Call this before update_page: the version number it returns is what update_page has to increment, and an update sent with the wrong version is rejected. body_format decides what you get back - storage is Confluence's XHTML storage format and is what create_page and update_page take, while view is rendered HTML that cannot be written back.

  • list_child_pages

    List the direct children of one page, in the order they appear in the sidebar tree. Use it to walk a documentation hierarchy downwards from a known page rather than searching; each result carries an id you can pass to get_page or back into this action. Returns titles and ids only, never bodies.

  • list_attachments

    List the files attached to a page: filename, media type, size, download link and the version that added each one. Use it to find out what supporting material a page carries. This returns metadata only - it does not download file contents.

  • list_spaces

    List the spaces this token can read, with their numeric id, key and name. Call this first for almost anything else: create_page needs the numeric space_id and will not take the key, and CQL queries in search_pages use the key. Takes no required arguments and changes nothing, which is why it is the install-time health check.

  • get_space

    Fetch one space by its numeric id: name, key, type, description, homepage id and author. Use it after list_spaces when you need the homepage id to start walking the tree with list_child_pages, or to read what a space is for before writing into it.

Writes

3

Creates or updates something on the other side.

  • create_page

    Publish a new page in a space. Needs the numeric space_id from list_spaces - the space key such as ENG is not accepted here. Pass parent_id to file the page under an existing one; omit it and the page lands at the top level of the space. The body is sent in the representation you name: storage is Confluence's XHTML storage format (<p>text</p>), wiki is legacy wiki markup, atlas_doc_format is ADF JSON. Returns the new page's id, version and links.

  • update_page

    Replace a page's title and body with a new version. Confluence has no partial edit here: whatever you send becomes the whole page, so read it with get_page first, change what you need, and send the result back. version_number must be exactly the current version plus one - get_page returns the current one, and a stale number is refused rather than silently overwriting someone else's edit. Every version is kept, so this is recoverable through the page history.

  • add_comment

    Post a footer comment on a page - the comment thread at the bottom, not an inline annotation on selected text. Prefer this over update_page when you are commenting on a document rather than changing it, because update_page replaces the body wholesale. The body is sent in the representation you name; storage format is plain XHTML such as <p>Looks right to me.</p>.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else
The 10 actions above are the whole of it. A call to any other name is refused before it reaches Confluence rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
Nothing here deletes
This connector writes to Confluence, but nothing in it deletes or permanently alters anything.
It reaches no further than your credential
Toolspoke holds no access to Confluence of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Confluence
Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Confluence. An agent has to ask.
It does not smooth over provider limits
Toolspoke does not retry, queue or back off around Confluence's own rate limits. A call that Confluence refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Confluence?

10 named actions: 7 that only read and 3 that write. They include search_pages, list_pages and get_page. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Confluence connector need?

Atlassian API token. The connector asks for atlassian site name and email and api token. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Confluence connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 10 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Confluence connector not do?

The 10 actions above are the whole of it. A call to any other name is refused before it reaches Confluence rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. This connector writes to Confluence, but nothing in it deletes or permanently alters anything. Toolspoke holds no access to Confluence of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Confluence. An agent has to ask. Toolspoke does not retry, queue or back off around Confluence's own rate limits. A call that Confluence refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Confluence's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Confluence?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.