Can I search the Knowledge Base?

Yes! Searches published Knowledge articles by keyword and returns title, summary, and direct link.

Can I add comments to cases?

Yes — add internal notes or customer-visible comments to any case.

Salesforce Service Cloud MCP Server for Claude Desktop 8 tools — connect in under 2 minutes

Name: Salesforce Service Cloud
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 8 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Salesforce Service Cloud and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "salesforce-service-cloud": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Salesforce Service Cloud MCP Server

Connect Salesforce Service Cloud to any AI agent.

Claude Desktop is the definitive way to connect Salesforce Service Cloud to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Cases — Search, create, update, and filter by status or priority
Comments — Read and add internal/public case comments
Knowledge — Search published knowledge articles for instant answers
Metrics — Aggregate case counts by status and priority

The Salesforce Service Cloud MCP Server exposes 8 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Salesforce Service Cloud to Claude Desktop via MCP

Follow these steps to integrate the Salesforce Service Cloud MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Salesforce Service Cloud

Look for the 🔌 icon in the chat — your 8 tools are now available

Why Use Claude Desktop with the Salesforce Service Cloud MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Salesforce Service Cloud through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Salesforce Service Cloud + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Salesforce Service Cloud MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Salesforce Service Cloud MCP Tools for Claude Desktop (8)

These 8 tools become available when you connect Salesforce Service Cloud to Claude Desktop via MCP:

sf_add_case_comment

Set isPublished to true if the comment should be visible to the customer (e.g., in a customer portal). Default is internal-only. Use to log agent responses, internal notes, or resolution steps on a support case. Add a comment to a Salesforce case — internal note or customer-visible response

sf_case_comments

Returns comment body, whether it is published (customer-visible), creator name, and creation date. Comments provide the full conversation history of a support case. Use to review case discussions or get context before responding. Get all comments (internal and customer-visible) on a specific Salesforce case for case history review

sf_case_metrics

Returns summary data: how many cases at each status × priority intersection. Perfect for support team dashboards, capacity planning, and identifying volume trends. Use when the user asks "how many open cases do we have?" or "what is the case breakdown by priority?" Get aggregate support case metrics — case counts grouped by status and priority for a team dashboard view

sf_cases_by_status

Returns cases sorted by priority then creation date. Use for support queue management: "how many new cases are there?", "show escalated cases", or for case workload analysis by status. Get all Salesforce cases at a specific status for queue analysis — New, Working, Escalated, or Closed

sf_create_case

Subject is required. Status defaults to "New". Priority: High, Medium, Low. Origin: Web, Phone, Email. Link to a customer via contactId and their company via accountId (both use 18-char Salesforce IDs). Cases track the complete lifecycle of a customer support issue. Create a new support case in Salesforce Service Cloud with subject, description, priority, origin, and linked contact/account

sf_search_cases

Returns case number, subject, status (New/Working/Escalated/Closed), priority (High/Medium/Low), origin channel (Web/Phone/Email), case owner, and description. Use when the user wants to find a specific support case, look up a case number, or review customer issues. Search Salesforce Service Cloud cases by subject or case number to find customer support issues

sf_search_knowledge

Returns article title, summary, URL, and article type. Salesforce Knowledge is the built-in KB for self-service and agent-assist. Use when the user asks for help articles, documented solutions, or wants to check if an issue has been addressed in the knowledge base. Search the Salesforce Knowledge Base for published articles to find documented solutions and answers

sf_update_case

Common operations: advance Status from "New" to "Working" to "Closed", escalate Priority to "High", or append to Description. Only specified fields change. Update a Salesforce case — change status, escalate priority, or add description to reflect case progress

Example Prompts for Salesforce Service Cloud in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Salesforce Service Cloud immediately.

"How many open P1 cases do we have?"

"Find a knowledge article about password reset"

"Create a high-priority case: Login page returning 500 error"

Troubleshooting Salesforce Service Cloud MCP Server with Claude Desktop

Common issues when connecting Salesforce Service Cloud to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Salesforce Service Cloud + Claude Desktop FAQ

Common questions about integrating Salesforce Service Cloud MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.