How to integrate Google Docs MCP with Kimi Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Google Docs logo
Kimi Code logo
divider

How to integrate Google Docs 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 Google Docs account to Kimi Code via Composio Connect, so it can create a new meeting notes document, copy last week's project summary template, add bullet points to the action items section, and more without ever putting your account credentials at risk.

Also integrate Google Docs 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 Google Docs 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 Google Docs account

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

For example, ask it to:

  • "Create a new meeting notes document"
  • "Copy last week's project summary template"
  • "Add bullet points to the action items section"

It will prompt you to authenticate and authorize access to Google Docs.

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

Supported Tools & Triggers

Tools
Triggers
Copy Google DocumentTool to create a copy of an existing Google Document.
Create a documentCreates a new Google Docs document using the provided title as filename and inserts the initial text at the beginning if non-empty, returning the document's ID and metadata (excluding body content).
Create Document MarkdownCreates a new Google Docs document, optionally initializing it with a title and content provided as Markdown text.
Create FooterTool to create a new footer in a Google Document.
Create FootnoteTool to create a new footnote in a Google Document.
Create HeaderTool to create a new header in a Google Document, optionally with text content.
Create Named RangeTool to create a new named range in a Google Document.
Create Paragraph BulletsTool to add bullets to paragraphs within a specified range in a Google Document.
Delete Content Range in DocumentTool to delete a range of content from a Google Document.
Delete FooterTool to delete a footer from a Google Document.
Delete HeaderDeletes the header from the specified section or the default header if no section is specified.
Delete Named RangeTool to delete a named range from a Google Document.
Delete Paragraph BulletsTool to remove bullets from paragraphs within a specified range in a Google Document.
Delete Table ColumnTool to delete a column from a table in a Google Document.
Delete Table RowTool to delete a row from a table in a Google Document.
Export Google Doc as PDFTool to export a Google Docs file as PDF using the Google Drive API.
Get document by idRetrieves an existing Google Document by its ID; will error if the document is not found.
Get document plain textRetrieve a Google Doc by ID and return a best-effort plain-text rendering.
Insert Inline ImageTool to insert an image from a given URI at a specified location in a Google Document as an inline image.
Insert Page BreakTool to insert a page break into a Google Document.
Insert Table in Google DocTool to insert a table into a Google Document.
Insert Table ColumnTool to insert a new column into a table in a Google Document.
Insert Text into DocumentTool to insert a string of text at a specified location within a Google Document.
Get Charts from SpreadsheetTool to retrieve a list of all charts from a specified Google Sheets spreadsheet.
Replace All Text in DocumentTool to replace all occurrences of a specified text string with another text string throughout a Google Document.
Replace Image in DocumentTool to replace a specific image in a document with a new image from a URI.
Search DocumentsSearch for Google Documents using various filters including name, content, date ranges, and more.
Unmerge Table CellsTool to unmerge previously merged cells in a table.
Update Document MarkdownReplaces the entire content of an existing Google Docs document with new Markdown text; requires edit permissions for the document.
Update Document Section MarkdownTool to insert or replace a section of a Google Docs document with Markdown content.
Update Document StyleTool to update the overall document style, such as page size, margins, and default text direction.
Update existing documentApplies programmatic edits, such as text insertion, deletion, or formatting, to a specified Google Doc using the `batchUpdate` API method.
Update Table Row StyleTool to update the style of a table row in a Google Document.

Conclusion

You have successfully connected Google Docs to Kimi Code using Composio Connect. Your agent can now manage Google Docs 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 Google Docs MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Google Docs MCP?

With a standalone Google Docs MCP server, the agents and LLMs can only access a fixed set of Google Docs tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Docs 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 Google Docs tools.

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

Yes, absolutely. You can configure which Google Docs 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 Google Docs 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.