How to integrate Google cloud vision MCP with Kimi Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Google cloud vision logo
Kimi Code logo
divider

How to integrate Google cloud vision 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 cloud vision account to Kimi Code via Composio Connect, so it can bulk import product images from GCS CSV, list all Vision AI service locations, create a new product for image recognition, and more without ever putting your account credentials at risk.

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

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

For example, ask it to:

  • "Bulk import product images from GCS CSV"
  • "List all Vision AI service locations"
  • "Create a new product for image recognition"

It will prompt you to authenticate and authorize access to Google cloud vision.

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

Supported Tools & Triggers

Tools
Annotate Files with Vision APITool to perform image detection and annotation for batch files in Google Cloud Vision.
Async Batch Annotate FilesTool to run asynchronous image detection and annotation for a list of generic files (PDF, TIFF, GIF).
Annotate ImagesRun image detection and annotation for a batch of images using Google Cloud Vision API.
Annotate Images Async BatchTool to run asynchronous image detection and annotation for a batch of images.
Annotate Location ImagesTool to run image detection and annotation for a batch of images scoped to a specific project and location.
Create Vision ProductCreates a new Product resource in Google Cloud Vision Product Search.
Create Product SetCreates a new ProductSet resource in Google Cloud Vision Product Search.
Create ReferenceImageTool to create a ReferenceImage under a product.
Delete ProductPermanently deletes a Product and its associated reference images from Google Cloud Vision API.
Get ProductTool to get information associated with a Product.
Get Product SetTool to get a ProductSet.
Import Product SetsAsynchronously imports product sets and reference images from a CSV file stored in Google Cloud Storage.
List Vision AI IndexEndpointsLists IndexEndpoints in Vertex AI Vision for a given project and location.
List LocationsTool to list available Vision AI service locations for a project.
List Vision API OperationsTool to list operations that match the specified filter.
Purge ProductsTool to asynchronously delete products in a ProductSet or orphan products.
Update ProductTool to update a Product's mutable fields: displayName, description, and productLabels.
Update Product SetTool to update a ProductSet resource.
Add Product to ProductSetAdd a Product to a ProductSet in Google Cloud Vision Product Search.
Cancel Vision OperationStarts asynchronous cancellation of a long-running Vision API operation.
Delete Vision API OperationTool to delete a long-running Vision API operation.
Delete Product SetTool to permanently delete a ProductSet.
Delete Reference ImagePermanently removes a reference image from a product in Google Cloud Vision Product Search.
Get Vision API OperationRetrieves the latest state of a long-running Vision API operation.
Get Reference ImageTool to get information associated with a ReferenceImage.
List Products in ProductSetTool to list Products in a specified ProductSet.
List ProjectsList Google Cloud projects accessible to the authenticated user via Cloud Resource Manager API.
List Reference ImagesTool to list reference images for a product.
Remove Product from ProductSetRemoves a Product from a specified ProductSet in Google Cloud Vision API.

Conclusion

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

FAQ

What are the differences in Tool Router MCP and Google cloud vision MCP?

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

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

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