Confluence MCP Server

How to use

Configure your MCP client to connect to the Confluence Tools server via a local MCP runtime. This server runs as an MCP stdio process, allowing you to execute Confluence operations directly from your editor or IDE. Use the provided configuration examples to enable space browsing, page details, hierarchy navigation, and full CRUD actions on pages.

Once configured, you can ask your MCP client to browse Confluence spaces, fetch page details with content, explore child pages for navigation, and create, update, or delete pages. You can also perform searches using plain text or advanced Confluence Query Language (CQL) to filter by space, content type, and sort results. All results render with readable markdown and direct links to Confluence when supported by your client.

With the server running, you can start experimenting by asking for Confluence spaces and pages, then expanding into page creation or updates as your workflow requires. Your MCP client will route requests to the Confluence MCP server and present the results in your editor alongside your code.

How to install

Prerequisites: you need a running MCP-capable client and a runtime that can host MCP servers. The Confluence MCP Server provided here uses Bun and the bunx command for quick start.

1) Install Bun (the runtime used to run bunx commands): install Bun from https://bun.sh and follow the on-screen instructions.

2) Add the Confluence Tools MCP server to your editor or MCP client configuration. Use the Bunx-based command shown to start the server via MCP.

3) Start using the server by loading your MCP client and ensuring the environment variables are set for Confluence access.

Below are configuration examples you can paste into your MCP client settings. Use the host URL for your Confluence instance, your Atlassian account email, and a generated API token.

Configuration examples for MCP clients

{
  "mcpServers": {
    "Confluence Tools": {
      "command": "bunx",
      "args": ["-y", "@dsazz/mcp-confluence@latest"],
      "env": {
        "CONFLUENCE_HOST_URL": "https://your-domain.atlassian.net",
        "CONFLUENCE_USER_EMAIL": "[email protected]",
        "CONFLUENCE_API_TOKEN": "your-confluence-api-token"
      }
    }
  }
}

Alternative: Using npx instead of bunx

{
  "mcpServers": {
    "Confluence Tools": {
      "command": "npx",
      "args": ["-y", "@dsazz/mcp-confluence@latest"],
      "env": {
        "CONFLUENCE_HOST_URL": "https://your-domain.atlassian.net",
        "CONFLUENCE_USER_EMAIL": "[email protected]",
        "CONFLUENCE_API_TOKEN": "your-confluence-api-token"
      }
    }
  }
}

Testing your setup

After adding the configuration, restart your MCP client and test the connection by asking to show your Confluence spaces. For example, say or type a request like “Show me my Confluence spaces.” If the server is running, you will receive a list of accessible spaces with links to each space.

Development and troubleshooting notes

If you are developing or customizing this MCP server, you can run the inspector to test capabilities and inspect JSON traffic. Start the inspector and visit its UI to verify routes and responses.

Common issues include incorrect Confluence host URL, invalid API token, or mismatched user email. Double-check these values in your environment or MCP configuration. If you encounter port conflicts during testing, ensure your editor’s MCP inspector and the Confluence server are not occupying the same port.

Security and best practices

Store Confluence credentials securely. Do not hard-code tokens in shared configurations. Use environment variables or secret management features provided by your development environment. Rotate API tokens regularly and limit token permissions to the minimum required for your use case.

Troubleshooting

NPM Installation Issues
If you encounter a package-not-found error, ensure you are using the exact package name and try installing via the preferred package manager shown in your setup. If needed, install directly from the npm registry.

Environment Variables Not Found If the server fails to start due to missing environment variables, create a local environment file or provide the variables in your MCP client configuration. Ensure CONFLUENCE_HOST_URL, CONFLUENCE_USER_EMAIL, and CONFLUENCE_API_TOKEN are set correctly.

API Connection Issues Invalid credentials or URL can prevent connections. Verify the API token and email, and ensure the host URL includes https://. If network policies restrict outbound access, adjust firewall or VPN settings accordingly.

confluence_get_spaces

List accessible Confluence spaces with optional filtering and pagination.

confluence_get_space_by_key

Retrieve detailed information about a specific space by its key.

confluence_get_pages_by_space

Fetch all pages within a given space, with optional pagination.

confluence_get_page

Get detailed information about a page, including content when requested.

confluence_get_child_pages

Obtain child pages for a page to navigate the hierarchy.

confluence_search

Search pages using text queries or advanced CQL with optional filtering and ordering.

confluence_create_page

Create a new page in a specified space with given content.

confluence_update_page

Update an existing page with new content and metadata.

confluence_delete_page

Delete a page by its ID and return a confirmation.