Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

Live 34 Actions

Salesforce Service Cloud MCP Server
for AI Agents

Connect your AI agent to StackOne's Salesforce Service Cloud MCP server and give it 34 MCP tools out of the box. Auth, tool execution, and security all managed.

Salesforce Service Cloud logo
Salesforce Service Cloud MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

34 Agent Actions

Create, read, update, and delete across Salesforce Service Cloud — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Salesforce Service Cloud MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Salesforce Service Cloud tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Salesforce Service Cloud call.

Tools Discovery →

What is the Salesforce Service Cloud MCP Server?

A Salesforce Service Cloud MCP server lets AI agents read and write Salesforce Service Cloud data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Salesforce Service Cloud MCP server ships with 34 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Salesforce Service Cloud MCP Tools

Every action from Salesforce Service Cloud's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Case Comments

  • Create Case Comment

    Add a new comment to a Case.

  • List Case Comments

    List comments for a specific Case via SOQL.

  • Get Case Comment

    Retrieve a single CaseComment record by ID.

  • Update Case Comment

    Update an existing CaseComment.

  • Delete Case Comment

    Soft-delete a CaseComment (moves to the Recycle Bin).

Cases

  • Create Case

    Create a new Case record in Salesforce Service Cloud.

  • List Cases

    Retrieve a paginated list of Case records from Salesforce Service Cloud via SOQL.

  • Get Case

    Retrieve a single Case record by its Salesforce ID.

  • Search Cases

    Full-text search across Case fields using SOSL.

  • Update Case

    Update an existing Case record.

  • Delete Case

    Soft-delete a Case (moves to the org's Recycle Bin).

Entitlements

  • Create Entitlement

    Create a new Entitlement record.

  • List Entitlements

    Retrieve a paginated list of Entitlement records via SOQL.

  • Get Entitlement

    Retrieve a single Entitlement by ID.

  • Update Entitlement

    Update an existing Entitlement.

  • Delete Entitlement

    Soft-delete an Entitlement.

Knowledge Articles

  • Create Knowledge Article

    Create a new Knowledge article in Draft state.

  • Publish Knowledge Article

    Transition a Knowledge article between Draft, Online (published), and Archived.

  • List Knowledge Articles

    List published Knowledge articles via the Connect REST API.

  • Get Knowledge Article

    Retrieve a single published Knowledge article via the Connect REST API.

  • Search Knowledge Articles

    Search published Knowledge articles by keyword via the Connect REST API.

  • Update Knowledge Article

    Update a Draft Knowledge article version.

  • Delete Knowledge Article

    Delete a Knowledge article version.

Service Contracts

  • Create Service Contract

    Create a new ServiceContract record.

  • List Service Contracts

    Retrieve a paginated list of ServiceContract records via SOQL.

  • Get Service Contract

    Retrieve a single ServiceContract by ID.

  • Update Service Contract

    Update an existing ServiceContract.

  • Delete Service Contract

    Soft-delete a ServiceContract.

Work Orders

  • Create Work Order

    Create a new WorkOrder record.

  • List Work Orders

    Retrieve a paginated list of WorkOrder records via SOQL.

  • Get Work Order

    Retrieve a single WorkOrder by ID.

  • Search Work Orders

    Full-text search across WorkOrder fields using SOSL.

  • Update Work Order

    Update an existing WorkOrder.

  • Delete Work Order

    Soft-delete a WorkOrder.

Set Up Your Salesforce Service Cloud MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Salesforce Service Cloud in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More support-ticketing MCP Servers

Salesforce Service Cloud MCP Server FAQ

Does StackOne have a Salesforce Service Cloud MCP server?
Yes. StackOne offers a hosted Salesforce Service Cloud MCP server with 34 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Salesforce Service Cloud MCP server vs direct API integration — what's the difference?
A Salesforce Service Cloud MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Salesforce Service Cloud. A Salesforce Service Cloud MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Salesforce Service Cloud at runtime. StackOne provides both.
How does Salesforce Service Cloud authentication work for AI agents?
Salesforce Service Cloud authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Salesforce Service Cloud account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Salesforce Service Cloud MCP tools vulnerable to prompt injection?
Yes — Salesforce Service Cloud MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Salesforce Service Cloud agent and how do I avoid it?
Context bloat happens when Salesforce Service Cloud tool schemas and API responses eat your Salesforce Service Cloud agent's memory, preventing it from reasoning effectively. A single Salesforce Service Cloud query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Salesforce Service Cloud agent can access?
Yes — you can limit which actions your Salesforce Service Cloud agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Salesforce Service Cloud MCP server?
Yes — you can create custom agent actions for your Salesforce Service Cloud MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Salesforce Service Cloud's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Salesforce Service Cloud MCP server?
Skip a Salesforce Service Cloud MCP server if your integration is purely software-to-software — direct Salesforce Service Cloud API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Salesforce Service Cloud actions at runtime.
What AI frameworks and AI clients does the StackOne Salesforce Service Cloud MCP server support?
The StackOne Salesforce Service Cloud MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.