How to Read and Summarize Salesforce Files in Claude Using a Custom MCP Server

Salesforce records often contain important business information inside contracts, proposals, invoices, case documents, technical specifications, and other uploaded files.

To analyze these documents using Claude, users would normally need to download the file from Salesforce, upload it to Claude, and then request a summary.

A custom Salesforce MCP Server removes these manual steps.

By connecting Salesforce with Claude through the Model Context Protocol, Claude can securely retrieve an authorized Salesforce file and use its content to generate summaries, identify important details, and answer document-related questions.

Real-Time Impact: From File Hunting to Instant Answers

The real shift this integration creates isn't that Claude reads documents faster than a human — it's that the entire retrieval chain disappears.

In the manual workflow, a Salesforce file has to leave Salesforce before anyone can analyze it with AI. It gets downloaded, re-uploaded into a separate tool, and re-explained with context the tool doesn't have. Every one of those steps is a place where time — and momentum — leaks.

With the Custom MCP Server, that chain collapses into one motion: the user asks, Claude retrieves the file, Claude answers. No download folder. No second tool. No re-explaining what the document is.

Here's where that actually shows up in the business:

• Faster decision-making, not just faster reading. When a rep or CS agent can ask Claude directly instead of hunting for a file, decisions on that deal or case happen sooner — the bottleneck was never the document itself, it was the detour to reach it.

• Faster onboarding for new hires and partners. New reps or support agents don't need to be trained on where files live or how Salesforce record structures are organized to get answers — they just ask. That shortens ramp-up time and reduces dependency on tribal knowledge about "who knows where that file is."

• One integration, growing value over time. The same foundation built for file summarization today extends to Opportunities, Cases, and Accounts tomorrow — without a new project or a new budget ask. That's a stronger pitch to a decision-maker than "here's what it does now": it's an investment that keeps paying off.

What We Are Building

In this implementation, Claude connects to a custom Salesforce MCP Server that provides access to Salesforce Files.

The complete process works as follows:

1. A user asks Claude to summarize a Salesforce file.
2. Claude identifies the appropriate Salesforce MCP tool.
3. Salesforce authenticates the user.
4. The MCP Server calls an Apex action.
5. The Apex action retrieves the requested Salesforce file.
6. The file information is returned to Claude.
7. Claude analyzes the content and generates the summary.

The overall architecture is: User → Claude → Salesforce MCP Server → Apex Action → Salesforce File → Claude Summary

Salesforce hosts the MCP Server, manages authentication, and controls access to the file. This means the integration does not require a separately hosted MCP Server.

Business Use Case

This integration can help users quickly understand information stored inside Salesforce Files.

For example, users can ask Claude to:

• Summarize a contract attached to an Account
• Identify important terms in a proposal
• Review case documents and highlight the main customer issue
• Extract key details from technical documents
• Summarize meeting notes or project documents
• Identify follow-up actions from an uploaded file

Instead of manually moving documents between Salesforce and Claude, users can work with the files directly through a secure Salesforce connection.

Prerequisites

Before starting, make sure you have:

• A Salesforce org with Hosted MCP Server support
• Permission to create Apex classes
• Permission to configure MCP Servers
• Permission to create an External Client App
• A Claude account that supports custom connectors
• A Salesforce File available for testing

It is recommended to complete the initial setup in a sandbox.

Step 1: Create the Apex Action

The Apex action is responsible for retrieving the Salesforce file.

The action:

• Accepts a Salesforce ContentVersion ID
• Retrieves the file title, type, and content
• Returns the file information to the MCP tool
• Returns an error message when the file cannot be accessed

The Apex action is responsible only for retrieving the file blob and exposing the file content to Claude. The summary itself is generated by Claude, not by the Apex action.  

Claude performs the document analysis and generates the final summary.

After creating the Apex class, provide Apex Class Access through the appropriate Profile or Permission Set.

Step 2: Create the Custom Salesforce MCP Server

Navigate to: Setup → Quick Find → MCP Servers

Open the Salesforce Servers section and create a custom MCP Server.

Use values similar to the following:

The description should clearly explain the business capability provided by the server.

Save the MCP Server.

Step 3: Add the Apex Action as an MCP Tool

Open the newly created Salesforce File Intelligence MCP Server and add a tool.

Configure the tool using values similar to the following:

The tool description is important because Claude uses it to understand when the tool should be called.

Since this tool only retrieves file information, configure it as a read-only and non-destructive tool when those options are available.

Save the tool configuration.

Step 4: Create an External Client App

Claude must authenticate with Salesforce before it can access the MCP Server.

Navigate to: Setup → External Client App Manager → New External Client App

Enter the application details.

Enable OAuth and enter the Claude callback URL: https://claude.ai/api/mcp/auth_callback

Add the OAuth permissions required to:

• Access Salesforce Hosted MCP Servers

• Maintain the authorized connection

Create the External Client App.

After the application is created, open its OAuth settings and copy the Consumer Key.

The Consumer Key will be used as the OAuth Client ID when configuring the connection in Claude.

Step 5: Activate the MCP Server

Return to: Setup → MCP Servers → Salesforce Servers

Open the Salesforce File Intelligence MCP Server and select Activate.

The server must be active before Claude can connect to it.

After activation, copy the generated Server URL from Salesforce.

Always use the URL provided in Salesforce Setup instead of manually creating the URL.

Step 6: Connect the MCP Server to Claude

In Claude:

1. Open Customize or Settings.
2. Select Connectors.
3. Select Add custom connector.
4. Enter a connector name such as Salesforce File Intelligence.
5. Paste the Salesforce MCP Server URL.
6. Open the advanced connection settings.
7. Paste the External Client App Consumer Key as the OAuth Client ID.
8. Add the connector.
9. Select Connect.

Claude redirects the user to Salesforce for authentication.

The user signs in to Salesforce and approves the connection.

After authentication, Claude can access the tools exposed through the custom Salesforce MCP Server.

Confirm that the following tool is available: get_salesforce_file_content

Salesforce Security Still Applies

Claude does not automatically receive access to every Salesforce file.

The integration works using the permissions of the Salesforce user who authorized the connection.

The user must have access to:

• The Apex class
• The requested Salesforce File
• The related Salesforce record
• The custom MCP Server

A dedicated Permission Set can be used to provide only the access required for this integration.

This helps ensure that Claude can retrieve only the files the authenticated Salesforce user is already allowed to access.

Important Considerations

The current implementation retrieves Salesforce Files stored through ContentVersion.

The user or Claude must provide the required ContentVersion ID.

For a more user-friendly experience, another MCP tool can later be added to find files attached to an Account, Opportunity, Case, or another Salesforce record.

For example, a user could ask: Summarize the latest contract attached to the Acme Account.

Claude could first locate the relevant Salesforce file and then call the file retrieval tool to generate the summary.

File size and file format should also be considered when using the integration with large or complex documents.

Business Benefits

This integration provides several practical benefits:

• Reduces manual file downloading and uploading
• Makes Salesforce documents easier to understand
• Helps users find important information faster
• Keeps Salesforce as the controlled source of the file
• Uses existing Salesforce permissions
• Allows Claude to work with Salesforce information through natural-language requests

Conclusion

A custom Salesforce MCP Server provides a secure way to connect Salesforce Files with Claude.

In this implementation, an Apex action retrieves an authorized Salesforce File and exposes the capability through an MCP tool. Claude calls the tool, receives the available file information, and generates a document summary.

This allows business users to work with Salesforce documents through simple natural-language requests, while technical teams continue to control authentication, permissions, and file access through Salesforce.

The result is a more connected experience where users can understand important Salesforce documents without repeatedly downloading and uploading files between systems.