SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Salesforce service cloud MCP with Vercel AI SDK v6

Connect Vercel AI SDK v6 to Salesforce service cloud MCP. List all open support cases for today, update case status to resolved for customer, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Salesforce service cloud logoSalesforce service cloud
Oauth2

Salesforce Service Cloud is a customer service platform for case management, omnichannel support, and automation. It enables teams to deliver faster, personalized service experiences with robust workflow tools and a unified workspace.

22 Tools

Introduction

This guide walks you through connecting Salesforce service cloud to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Salesforce service cloud agent that can manage case records, run SOQL queries, read live chat messages, send composite requests, and list Einstein bots through natural language commands.

This guide will help you understand how to give your Vercel AI SDK agent real control over a Salesforce service cloud account through Composio's Salesforce service cloud MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Salesforce service cloud with

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKClaude Agent SDKCodexKimi CodeGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentCLIGoogle ADKLangChainMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • How to set up and configure a Vercel AI SDK agent with Salesforce service cloud integration
  • Using Composio's Tool Router to dynamically load and access Salesforce service cloud tools
  • Creating an MCP client connection using HTTP transport
  • Building an interactive CLI chat interface with conversation history management
  • Handling tool calls and results within the Vercel AI SDK framework

What is Vercel AI SDK?

The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state.

Key features include:

  • streamText: Core function for streaming responses with real-time tool support
  • MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp
  • Step Counting: Control multi-step tool execution with stopWhen: stepCountIs()
  • OpenAI Provider: Native integration with OpenAI models

What is the Salesforce service cloud MCP server, and what's possible with it?

The Salesforce service cloud MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Salesforce Service Cloud account. It provides structured and secure access to your customer service data, so your agent can perform actions like managing cases, retrieving knowledge articles, automating service processes, and tracking customer interactions on your behalf.

  • Case management and triage: Empower your agent to create, update, assign, or close customer service cases, ensuring timely resolution of inquiries and incidents.
  • Knowledge base retrieval: Let your agent search, read, and recommend relevant knowledge articles to assist with customer support and internal troubleshooting.
  • Customer interaction tracking: Have your agent log new interactions, fetch historical communication, and surface recent touchpoints for a full view of customer engagement.
  • Omnichannel support automation: Enable your agent to route cases, escalate issues, and send custom events during active Live Agent chat sessions all from one place.
  • Service workflow automation: Direct your agent to retrieve case details, update case statuses, or execute SOQL queries to streamline repetitive tasks and boost support team productivity.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Node.js and npm installed
  • A Composio account with API key
  • An OpenAI API key
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install required dependencies

bash
npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv

First, install the necessary packages for your project.

What you're installing:

  • @ai-sdk/openai: Vercel AI SDK's OpenAI provider
  • @ai-sdk/mcp: MCP client for Vercel AI SDK
  • @composio/core: Composio SDK for tool integration
  • ai: Core Vercel AI SDK
  • dotenv: Environment variable management
4

Set up environment variables

bash
OPENAI_API_KEY=your_openai_api_key_here
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here

Create a .env file in your project root.

What's needed:

  • OPENAI_API_KEY: Your OpenAI API key for GPT model access
  • COMPOSIO_API_KEY: Your Composio API key for tool access
  • COMPOSIO_USER_ID: A unique identifier for the user session
5

Import required modules and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});
What's happening:
  • We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio
  • The dotenv/config import automatically loads environment variables
  • The MCP client import enables connection to Composio's tool server
6

Create Tool Router session and initialize MCP client

typescript
async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["salesforce_service_cloud"],
  });

  const mcpUrl = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Salesforce service cloud tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned mcp object contains the URL and authentication headers needed to connect to the MCP server
  • This session provides access to all Salesforce service cloud-related tools through the MCP protocol
7

Connect to MCP server and retrieve tools

typescript
const mcpClient = await createMCPClient({
  transport: {
    type: "http",
    url: mcpUrl,
    headers: session.mcp.headers, // Authentication headers for the Composio MCP server
  },
});

const tools = await mcpClient.tools();
What's happening:
  • We're creating an MCP client that connects to our Composio Tool Router session via HTTP
  • The mcp.url provides the endpoint, and mcp.headers contains authentication credentials
  • The type: "http" is important - Composio requires HTTP transport
  • tools() retrieves all available Salesforce service cloud tools that the agent can use
8

Initialize conversation and CLI interface

typescript
let messages: ModelMessage[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log(
  "Ask any questions related to salesforce_service_cloud, like summarize my last 5 emails, send an email, etc... :)))\n",
);

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();
What's happening:
  • We initialize an empty messages array to maintain conversation history
  • A readline interface is created to accept user input from the command line
  • Instructions are displayed to guide the user on how to interact with the agent
9

Handle user input and stream responses with real-time tool feedback

typescript
rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({ role: "user", content: trimmedInput });
  console.log("\nAgent is thinking...\n");

  try {
    const stream = streamText({
      model: openai("gpt-5"),
      messages,
      tools,
      toolChoice: "auto",
      stopWhen: stepCountIs(10),
      onStepFinish: (step) => {
        for (const toolCall of step.toolCalls) {
          console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • We use streamText instead of generateText to stream responses in real-time
  • toolChoice: "auto" allows the model to decide when to use Salesforce service cloud tools
  • stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations
  • onStepFinish callback displays which tools are being used in real-time
  • We iterate through the text stream to create a typewriter effect as the agent responds
  • The complete response is added to conversation history to maintain context
  • Errors are caught and displayed with helpful retry suggestions

Complete Code

Here's the complete code to get you started with Salesforce service cloud and Vercel AI SDK:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Composio } from "@composio/core";
import * as readline from "readline";
import { streamText, type ModelMessage, stepCountIs } from "ai";
import { createMCPClient } from "@ai-sdk/mcp";

const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey,
});

async function main() {
  // Create a tool router session for the user
  const session = await composio.create(composioUserID!, {
    toolkits: ["salesforce_service_cloud"],
  });

  const mcpUrl = session.mcp.url;

  const mcpClient = await createMCPClient({
    transport: {
      type: "http",
      url: mcpUrl,
      headers: session.mcp.headers, // Authentication headers for the Composio MCP server
    },
  });

  const tools = await mcpClient.tools();

  let messages: ModelMessage[] = [];

  console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
  console.log(
    "Ask any questions related to salesforce_service_cloud, like summarize my last 5 emails, send an email, etc... :)))\n",
  );

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
      console.log("\nGoodbye!");
      rl.close();
      process.exit(0);
    }

    if (!trimmedInput) {
      rl.prompt();
      return;
    }

    messages.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    try {
      const stream = streamText({
        model: openai("gpt-5"),
        messages,
        tools,
        toolChoice: "auto",
        stopWhen: stepCountIs(10),
        onStepFinish: (step) => {
          for (const toolCall of step.toolCalls) {
            console.log(`[Using tool: ${toolCall.toolName}]`);
          }
          if (step.toolCalls.length > 0) {
            console.log(""); // Add space after tool calls
          }
        },
      });

      for await (const chunk of stream.textStream) {
        process.stdout.write(chunk);
      }

      console.log("\n\n---\n");

      // Get final result for message history
      const response = await stream.response;
      if (response?.messages?.length) {
        messages.push(...response.messages);
      }
    } catch (error) {
      console.error("\nAn error occurred while talking to the agent:");
      console.error(error);
      console.log(
        "\nYou can try again or restart the app if it keeps happening.\n",
      );
    } finally {
      rl.prompt();
    }
  });

  rl.on("close", async () => {
    await mcpClient.close();
    console.log("\n👋 Session ended.");
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

Conclusion

You've successfully built a Salesforce service cloud agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback.

Key features of this implementation:

  • Real-time streaming responses for a better user experience with typewriter effect
  • Live tool execution feedback showing which tools are being used as the agent works
  • Dynamic tool loading through Composio's Tool Router with secure authentication
  • Multi-step tool execution with configurable step limits (up to 10 steps)
  • Comprehensive error handling for robust agent execution
  • Conversation history maintenance for context-aware responses

You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Salesforce service cloud action and event your agent gets out of the box.

Chasitor Sneak Peek

Send real-time typing indicator (sneak peek) to Live Agent during active chat session.

Composite Batch

Tool to execute multiple independent REST subrequests in one batch call.

Composite Request

Execute up to 25 dependent Salesforce REST subrequests in a single API call.

Composite SObject Tree

Create one or more nested sObject record trees in a single API call.

Create Case Record

Tool to create or upsert a Salesforce Case record.

Delete Case Record

Tool to delete a Salesforce Case record.

Describe SObject

Tool to retrieve metadata of any sObject.

Generate Request ID

Generate a UUIDv4 string to use as an Idempotency-Key header in Salesforce User Interface API requests.

Generate Signed JWT Assertion

Tool to generate a signed JWT assertion for Salesforce JWT bearer OAuth flow.

Get Case Record

Retrieve a Salesforce Case record by its ID.

Get Chat Messages

Tool to long-poll for chat messages/events.

Get Live Agent API Version

Retrieve the highest-numbered Salesforce REST API version available from the instance's versions list, along with its root URL.

List Einstein Bots

List Einstein Bot definitions using the Salesforce Tooling API, returning IDs, labels, developer names and language settings from the first result page.

Query All SOQL

Tool to execute a SOQL query including deleted and archived records.

Query SOQL

Tool to execute a SOQL query.

Reconnect Chat Session

Reconnect a Live Agent chat session after its affinity token changes, using the session key and affinity token.

Resync Chasitor State

Resynchronizes the chat visitor's state after a session reconnection.

Retrieve Salesforce Username

Queries Salesforce for a username using the user ID in connection metadata when available.

Send Custom Event

Send a custom event from a chat visitor to a Live Agent during an active chat session.

Set Breadcrumb

Tool to set a breadcrumb URL for the visitor's current page.

Upload File to S3

Tool to upload a file to managed S3 storage.

Visitor Sensitive Data Rule Triggered

Trigger sensitive data rules for a Live Agent chat visitor after sensitive content is detected, to support masking or handling.

FRAMEWORKS

How to build Salesforce service cloud MCP Agent with another framework

Claude Code logo

Claude Code

Use Salesforce service cloud MCP with Claude Code

Cursor logo

Cursor

Use Salesforce service cloud MCP with Cursor

ChatGPT logo

ChatGPT

Use Salesforce service cloud MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Salesforce service cloud MCP with Claude Cowork

Antigravity logo

Antigravity

Use Salesforce service cloud MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Salesforce service cloud MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Salesforce service cloud MCP with Claude Agent SDK

Codex logo

Codex

Use Salesforce service cloud MCP with Codex

Kimi Code logo

Kimi Code

Use Salesforce service cloud MCP with Kimi Code

Grok Build logo

Grok Build

Use Salesforce service cloud MCP with Grok Build

VS Code logo

VS Code

Use Salesforce service cloud MCP with VS Code

OpenCode logo

OpenCode

Use Salesforce service cloud MCP with OpenCode

OpenClaw logo

OpenClaw

Use Salesforce service cloud MCP with OpenClaw

Hermes logo

Hermes

Use Salesforce service cloud MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Salesforce service cloud MCP with Atomic Agent

CLI logo

CLI

Use Salesforce service cloud MCP with CLI

Google ADK logo

Google ADK

Use Salesforce service cloud MCP with Google ADK

LangChain logo

LangChain

Use Salesforce service cloud MCP with LangChain

Mastra AI logo

Mastra AI

Use Salesforce service cloud MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Salesforce service cloud MCP with LlamaIndex

CrewAI logo

CrewAI

Use Salesforce service cloud MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Salesforce service cloud MCP with Pydantic AI

AutoGen logo

AutoGen

Use Salesforce service cloud MCP with AutoGen

FAQ

Frequently asked questions

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.

Yes, you can. Vercel AI SDK v6 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.

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.

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.

Start with Salesforce service cloud.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Salesforce service cloud tool your agent needs.Free to start.

Start building