How to integrate Confluence MCP with Kimi Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Confluence logo
Kimi Code logo
divider

How to integrate Confluence MCP with Kimi Code

Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools.

In this guide, I will explain the easiest and most secure way to connect your Confluence account to Kimi Code via Composio Connect, so it can create a project documentation page in Marketing space, add 'urgent' label to Q3 planning page, publish team meeting summary as a blog post, and more without ever putting your account credentials at risk.

Also integrate Confluence with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Managed OAuth. You do not have to worry about authentication and authorization flows for every app.
  • Programmatic tool calling. Allows LLMs to write code in a remote workbench to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Connect Confluence to Kimi Code

Kimi Code is a TypeScript agent distributed through npm. It acts as an MCP client and reads server definitions from an mcp.json file, and it can also add and authenticate servers conversationally through /mcp-config. Composio is a remote HTTP server that authenticates with OAuth, so no API key is stored anywhere.

1. Install Kimi Code

The quickest way is the official install script, which requires no pre-installed Node.js and places the kimi executable on your PATH.

bash
# macOS or Linux
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

# Windows PowerShell
irm https://code.kimi.com/kimi-code/install.ps1 | iex

# Confirm the installation
kimi --version

2. Log in

Start Kimi Code in your project directory, then sign in from the interactive UI:

bash
kimi

Run /login and choose Kimi Code OAuth using the device-code flow, or use a Moonshot API key.

3. Add Composio with /mcp-config

In current versions of Kimi Code, MCP servers are managed inside the app, not with a shell subcommand. From the interactive UI, run:

bash
/mcp-config
Kimi Code MCP config flow for adding the Composio MCP server

Tell it the server name and URL in plain language. For example:

Server name is Composio, and here is the server URL: https://connect.composio.dev/mcp

Kimi Code asks whether to add it globally, at ~/.kimi-code/mcp.json, or project-local for the current checkout, then writes the entry for you:

bash
{
  "mcpServers": {
    "Composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

There is no transport field to set. Kimi Code infers HTTP from the url.

4. Restart the session

The new server is picked up on a fresh session, not the current one. Start a new session:

bash
/new

On the new session, Kimi Code detects that the server needs authorization and prompts you to run:

bash
/mcp-config login Composio

5. Authorize with OAuth

Run the command Kimi suggests:

bash
/mcp-config login composio

Kimi Code opens Composio's authorization page or surfaces a URL. Approve access, then return to the session. You should see confirmation that the Composio MCP server is connected.

Composio authorization page for Kimi Code MCP setup

Check the connection status any time with /mcp. Composio should appear as connected with its tools listed.

Kimi Code showing Composio connected after OAuth authorization

Connect your Confluence account

Back in a Kimi Code session, ask the agent to connect to Confluence or give it any Confluence-related task.

For example, ask it to:

  • "Create a project documentation page in Marketing space"
  • "Add 'urgent' label to Q3 planning page"
  • "Publish team meeting summary as a blog post"

It will prompt you to authenticate and authorize access to Confluence.

That is it. Composio tools are now available in Kimi Code, and your Confluence account is ready to use.

Supported Tools & Triggers

Tools
Triggers
Add Content LabelTool to add labels to a piece of content.
CQL SearchSearches for content in Confluence using Confluence Query Language (CQL).
Create BlogpostTool to create a new Confluence blog post.
Create Blogpost PropertyTool to create a property on a specified blog post.
Create Whiteboard PropertyTool to create a new content property on a whiteboard.
Create Footer CommentTool to create a footer comment on a Confluence page, blog post, attachment, or custom content.
Create PageTool to create a new Confluence page in a specified space.
Create Page PropertyTool to create a property on a Confluence page.
Create Private SpaceTool to create a private Confluence space.
Create SpaceTool to create a new Confluence space.
Create Space PropertyTool to create a new property on a Confluence space.
Create WhiteboardTool to create a new Confluence whiteboard.
Delete Blogpost PropertyTool to delete a blog post property.
Delete Page Content PropertyTool to delete a content property from a page by property ID.
Delete Whiteboard Content PropertyTool to delete a content property from a whiteboard by property ID.
Delete PageTool to delete a Confluence page.
Delete SpaceTool to delete a Confluence space by its key.
Delete Space PropertyTool to delete a space property.
Download AttachmentDownloads an attachment from a Confluence page and returns a publicly accessible S3 URL.
Get Attachment LabelsTool to list labels on an attachment.
Get AttachmentsTool to retrieve attachments of a Confluence page.
Get Audit LogsTool to retrieve Confluence audit records.
Get Blogpost by IDTool to retrieve a specific Confluence blog post by its ID.
Get Blogpost LabelsTool to retrieve labels of a specific Confluence blog post by ID.
Get Blogpost Like CountTool to get like count for a Confluence blog post.
Get Blogpost OperationsTool to retrieve permitted operations for a Confluence blog post.
Get Blog PostsTool to retrieve a list of blog posts.
Get Blog Posts For LabelTool to list all blog posts under a specific label.
Get Blogpost Version DetailsTool to retrieve details for a specific version of a blog post.
Get Blogpost VersionsTool to retrieve all versions of a specific blog post.
Get Child PagesTool to list all direct child pages of a given Confluence page.
Get Blog Post Content PropertiesTool to retrieve all content properties on a blog post.
Get Page Content PropertiesTool to retrieve all content properties on a page.
Get Content RestrictionsTool to retrieve restrictions on a Confluence content item.
Get Current UserTool to get information about the currently authenticated user — always scoped to the account tied to the configured connection, not arbitrary users.
Get Inline Comments for Blog PostTool to retrieve inline comments for a Confluence blog post.
Get LabelsTool to retrieve all labels in a Confluence site; use for label discovery when you need to list or page through labels.
Get Page LabelsTool to retrieve labels of a specific Confluence page by ID.
Get Labels for SpaceTool to list labels on a space.
Get Labels for Space ContentTool to list labels on all content in a space.
Get Page AncestorsTool to retrieve all ancestors for a given Confluence page by its ID.
Get Page by IDTool to retrieve a Confluence page by its ID.
Get Page Footer CommentsTool to retrieve footer (non-inline) comments for a Confluence page.
Get Page Inline CommentsTool to retrieve inline comments for a Confluence page.
Get Page Like CountTool to get like count for a Confluence page.
Get PagesTool to retrieve a paginated list of Confluence pages.
Get Page VersionsTool to retrieve all versions of a specific Confluence page.
Get Space by IDTool to retrieve a Confluence space by its ID.
Get Space ContentsTool to retrieve content in a Confluence space.
Get Space PropertiesTool to get properties of a Confluence space.
Get SpacesTool to retrieve a paginated list of Confluence spaces with optional filtering.
Get TasksTool to list Confluence tasks (action items) with filtering by assignee, creator, space, page, blog post, status, and dates.
Get Anonymous UserTool to retrieve information about the anonymous user.
Search ContentSearches for content by filtering pages from the Confluence v2 API with intelligent ranking.
Search UsersSearches for users using user-specific queries from the Confluence Query Language (CQL).
Update BlogpostTool to update a Confluence blog post's title or content.
Update Blogpost PropertyTool to update a property of a specified blog post.
Update Page Content PropertyTool to update a content property on a Confluence page.
Update Whiteboard Content PropertyTool to update a content property on a whiteboard.
Update PageTool to update an existing Confluence page, replacing the entire page content.
Update Space PropertyTool to update a space property.
Update TaskTool to update a Confluence task status.

Conclusion

You have successfully connected Confluence to Kimi Code using Composio Connect. Your agent can now manage Confluence from the terminal with natural language, without exposing credentials in prompts or local scripts.

Since the same Composio endpoint exposes 1,000+ apps, you can add Slack, Calendar, Linear, and more to the same server and chain them into cross-app workflows.

How to build Confluence MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Confluence MCP?

With a standalone Confluence MCP server, the agents and LLMs can only access a fixed set of Confluence tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Confluence and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Kimi Code?

Yes, you can. Kimi Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Confluence tools.

Can I manage the permissions and scopes for Confluence while using Tool Router?

Yes, absolutely. You can configure which Confluence scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Confluence data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.