How to integrate Salesforce service cloud MCP with Kimi Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Salesforce service cloud logo
Kimi Code logo
divider

How to integrate Salesforce service cloud 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 Salesforce service cloud account to Kimi Code via Composio Connect, so it can list all open support cases for today, update case status to resolved for customer, fetch recent customer interactions for an account, and more without ever putting your account credentials at risk.

Also integrate Salesforce service cloud 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 Salesforce service cloud 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 Salesforce service cloud account

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

For example, ask it to:

  • "List all open support cases for today"
  • "Update case status to resolved for customer"
  • "Fetch recent customer interactions for an account"

It will prompt you to authenticate and authorize access to Salesforce service cloud.

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

Supported Tools & Triggers

Tools
Chasitor Sneak PeekSend real-time typing indicator (sneak peek) to Live Agent during active chat session.
Composite BatchTool to execute multiple independent REST subrequests in one batch call.
Composite RequestExecute up to 25 dependent Salesforce REST subrequests in a single API call.
Composite SObject TreeCreate one or more nested sObject record trees in a single API call.
Create Case RecordTool to create or upsert a Salesforce Case record.
Delete Case RecordTool to delete a Salesforce Case record.
Describe SObjectTool to retrieve metadata of any sObject.
Generate Request IDGenerate a UUIDv4 string to use as an Idempotency-Key header in Salesforce User Interface API requests.
Generate Signed JWT AssertionTool to generate a signed JWT assertion for Salesforce JWT bearer OAuth flow.
Get Case RecordRetrieve a Salesforce Case record by its ID.
Get Chat MessagesTool to long-poll for chat messages/events.
Get Live Agent API VersionTool to retrieve current Live Agent API version.
List Einstein BotsLists all Einstein Bot definitions in the Salesforce organization.
Query All SOQLTool to execute a SOQL query including deleted and archived records.
Query SOQLTool to execute a SOQL query.
Reconnect Chat SessionTool to reconnect a Live Agent chat session after the affinity token changes.
Resync Chasitor StateResynchronizes the chat visitor's state after a session reconnection.
Retrieve Connected App Private KeyTool to retrieve RSA private key PEM for a Salesforce Connected App.
Retrieve Salesforce UsernameTool to retrieve the Salesforce username.
Send Custom EventSend a custom event from a chat visitor to a Live Agent during an active chat session.
Set BreadcrumbTool to set a breadcrumb URL for the visitor's current page.
Upload File to S3Tool to upload a file to managed S3 storage.
Visitor Sensitive Data Rule TriggeredTool to trigger sensitive data rules for the chat visitor.

Conclusion

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

FAQ

What are the differences in Tool Router MCP and Salesforce service cloud MCP?

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

Can I manage the permissions and scopes for Salesforce service cloud while using Tool Router?

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