Which integrations are available for this server?

Provides secure access to Salesforce data and operations through OAuth 2.0, enabling SOQL query execution, CRUD operations on records (Accounts, Contacts, Opportunities, etc.), and object metadata retrieval with built-in security and rate limiting.

How do I use MCP Salesforce Lite?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Salesforce Lite show me the last 10 opportunities created this month" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP Salesforce Lite

by luvl

Overview Schema Related Servers Score Discussions

Python

Remote

mcp-salesforce-lite

Simple and lightweight Salesforce MCP server for connecting AI assistants to Salesforce data. Ideal for prototyping and small projects.

PyPI version Python License: MIT GitHub stars

📦 Install from PyPI: pip install mcp-salesforce-lite

🔗 PyPI Package: https://pypi.org/project/mcp-salesforce-lite/

📚 GitHub Repository: https://github.com/luvl/mcp-salesforce-lite

Demo

See the MCP Salesforce Lite server in action with Claude Desktop:

Salesforce MCP Demo

The demo shows Claude Desktop using the MCP server to interact with Salesforce data - querying objects, retrieving records, and performing CRUD operations seamlessly.

Related MCP server: MCP Salesforce Server

Overview

This MCP (Model Context Protocol) server provides AI assistants like Claude with secure access to Salesforce data and operations. It implements the MCP standard to enable seamless integration between AI applications and Salesforce CRM.

Features

🔐 Secure Salesforce authentication via OAuth 2.0
📊 Access to Salesforce objects (Accounts, Contacts, Opportunities, etc.)
🔍 SOQL query execution
📝 CRUD operations on Salesforce records
🛡️ Built-in security and rate limiting
🚀 Easy setup and configuration

Quick Usage

# Install the package
pip install mcp-salesforce-lite

# Use with Claude Desktop (recommended)
uvx --from mcp-salesforce-lite mcp-salesforce-lite

# Or run directly
mcp-salesforce-lite

Works with: Claude Desktop, any MCP-compatible AI assistant

Quick Start with Claude Desktop

Production Usage (Recommended)

The easiest way to use this MCP server is to install it directly from PyPI and configure it with Claude Desktop.

Step 1: Configure Claude Desktop

Add the following configuration to your Claude Desktop settings file:

Configuration File Location:

macOS/Linux: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Configuration:

{
  "mcpServers": {
    "salesforce-lite": {
      "command": "uvx",
      "args": [
        "--from",
        "mcp-salesforce-lite",
        "mcp-salesforce-lite"
      ],
      "env": {
        "SALESFORCE_ACCESS_TOKEN": "your_access_token",
        "SALESFORCE_INSTANCE_URL": "your_instance_url"
      }
    }
  }
}

Step 2: Set Up Salesforce Credentials

Replace the environment variables in the configuration:

SALESFORCE_ACCESS_TOKEN: Your Salesforce access token
SALESFORCE_INSTANCE_URL: Your Salesforce instance URL (e.g., https://yourcompany.my.salesforce.com)

Step 3: Restart Claude Desktop

After saving the configuration, restart Claude Desktop. You should see a hammer icon indicating that tools are available.

Step 4: Test the Integration

Try asking Claude:

"List available Salesforce objects"
"Describe the Account object"
"Execute a SOQL query to get recent leads"

Prerequisites

Python 3.10 or higher
Salesforce Developer/Production org
Connected App configured in Salesforce

Development Setup

If you want to modify or contribute to this MCP server, follow these development setup instructions.

Installation

Option 1: Using uv (Recommended for development)

# Install uv if you haven't already
brew install uv  # macOS
# or
curl -LsSf https://astral.sh/uv/install.sh | sh  # Linux/macOS

# Clone and install the server
git clone https://github.com/luvl/mcp-salesforce-lite.git
cd mcp-salesforce-lite
uv sync

Option 2: Using Poetry

git clone https://github.com/luvl/mcp-salesforce-lite.git
cd mcp-salesforce-lite
poetry install

Salesforce Development Setup

Create a .env file in the project root:

SALESFORCE_ACCESS_TOKEN=your_access_token
SALESFORCE_INSTANCE_URL=your_instance_url

Usage

Development Mode

First, make sure you have your Salesforce credentials configured in your .env file.

Method 1: Direct Python Execution

# Run the server directly
python src/mcp_salesforce_lite/server.py

Method 2: Using Poetry

# Run with Poetry
poetry run python src/mcp_salesforce_lite/server.py

Method 3: Using UV (Recommended)

# Run with UV
uv run python src/mcp_salesforce_lite/server.py

Testing with MCP Inspector

If you have the MCP CLI installed, you can test your server:

# Test with MCP Inspector
mcp inspector

# Or run in development mode
mcp dev src/mcp_salesforce_lite/server.py

How to Release the Server as a Pip Package

The server can be packaged and distributed via PyPI using the included pyproject.toml configuration.

Available Tools

The server provides the following tools that AI assistants can use:

Query Tools

soql_query: Execute SOQL queries (schema must be defined to carefully ask for confirmation of UPDATE and DELETE operations)
search_records: Search records across multiple objects with limit and pagination
get_record: Retrieve a specific record by ID with limit and pagination

CRUD Operations

create_record: Create new records (make sure to describe_object first, and find the reference fields of the objects)
update_record: Update existing records
delete_record: Delete records

Metadata Tools

describe_object_definition: Get object metadata and field information with pagination
list_avail_objects: List available Salesforce objects with limit and pagination

Development Claude Desktop Integration

If you're developing or running the server from source, you can use these alternative configurations:

💡 Tip: Example configuration files are provided in the examples/ directory:

examples/claude_config_direct.json - Direct Python execution
examples/claude_config_poetry.json - Poetry execution
examples/claude_config_uv.json - UV execution (recommended)

Option 1: Direct Python Execution

{
  "mcpServers": {
    "salesforce-lite": {
      "command": "python",
      "args": ["/ABSOLUTE/PATH/TO/mcp-salesforce-lite/src/mcp_salesforce_lite/server.py"],
      "env": {
        "SALESFORCE_ACCESS_TOKEN": "your_access_token",
        "SALESFORCE_INSTANCE_URL": "your_instance_url"
      }
    }
  }
}

Option 2: Poetry Execution

{
  "mcpServers": {
    "salesforce-lite": {
      "command": "poetry",
      "args": [
        "--directory",
        "/ABSOLUTE/PATH/TO/mcp-salesforce-lite",
        "run",
        "python",
        "src/mcp_salesforce_lite/server.py"
      ],
      "env": {
        "SALESFORCE_ACCESS_TOKEN": "your_access_token",
        "SALESFORCE_INSTANCE_URL": "your_instance_url"
      }
    }
  }
}

Option 3: UV Execution (Recommended for Development)

{
  "mcpServers": {
    "salesforce-lite": {
      "command": "uv",
      "args": [
        "--directory",
        "/ABSOLUTE/PATH/TO/mcp-salesforce-lite",
        "run",
        "python",
        "src/mcp_salesforce_lite/server.py"
      ],
      "env": {
        "SALESFORCE_ACCESS_TOKEN": "your_access_token",
        "SALESFORCE_INSTANCE_URL": "your_instance_url"
      }
    }
  }
}

Project Structure

mcp-salesforce-lite/
├── src/
│   └── mcp_salesforce_lite/
│       ├── __init__.py
│       ├── server.py          # Main MCP server
│       ├── client.py          # Salesforce client wrapper
│       ├── config.py          # Configuration management
│       └── tools/
│           ├── __init__.py
│           ├── query.py       # SOQL query tools
│           ├── crud.py        # Create, Read, Update, Delete tools
│           └── metadata.py    # Object metadata tools
├── examples/
│   ├── basic_usage.py
│   └── claude_config.json
├── assets/
│   └── sf-demo.gif           # Demo GIF showing usage
├── .env.example
├── pyproject.toml
├── poetry.lock
└── uv.lock

Release

Prerequisites

Register for PyPI Production: Go to https://pypi.org/account/register/
Enable 2FA: Set up two-factor authentication in your account settings
Create API Token: Go to https://pypi.org/manage/account/token/ and create a token
Update .pypirc: Replace pypi-YOUR_PRODUCTION_TOKEN_FROM_PYPI_ORG_HERE with your actual token

Publishing Process

Test on TestPyPI first:

# Build the package
uv build
# or: poetry build

# Upload to TestPyPI
twine upload --repository testpypi --config-file .pypirc dist/*

# Test install from TestPyPI
pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ mcp-salesforce-lite

Publish to Production PyPI:

# Upload to production PyPI
twine upload --repository pypi --config-file .pypirc dist/*

# Test install from production PyPI
pip install mcp-salesforce-lite

Version Management

To publish a new version:

Update the version in pyproject.toml
Rebuild: uv build or poetry build
Upload: twine upload --repository pypi --config-file .pypirc dist/*

Available Tools

8 tools

create_recordC

Create a new Salesforce record

ParametersJSON Schema

Name	Required	Description	Default
`object_type`	Yes	The Salesforce object type (e.g., 'Account', 'Contact')
`record_data`	Yes	Dictionary containing the field values for the new record

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this requires specific permissions, if it's idempotent, what happens on failure, or any rate limits, leaving significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste, front-loading the core purpose. It's appropriately sized for a simple tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on return values, error handling, or behavioral context, which are critical for safe and effective use in a Salesforce environment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning beyond the schema, such as examples of 'object_type' or 'record_data' usage, but doesn't need to compensate for gaps, resulting in a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and resource ('new Salesforce record'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'update_record' or specify what constitutes a 'record' in Salesforce context, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'update_record' or 'delete_record', nor does it mention prerequisites such as object type availability or permissions. The description lacks context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_recordC

Delete a Salesforce record

ParametersJSON Schema

Name	Required	Description	Default
`object_type`	Yes	The Salesforce object type (e.g., 'Account', 'Contact')
`record_id`	Yes	The ID of the record to delete

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't specify whether deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., cascading deletions). It also doesn't mention error conditions or what happens on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context like what the tool returns (success confirmation, error details), whether deletion affects related records, or security requirements, leaving significant gaps for agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents both parameters (object_type and record_id). The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate but no extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and target resource ('a Salesforce record'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'create_record' or 'update_record' in terms of what makes deletion unique versus other record operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'update_record' or 'get_record'. There's no mention of prerequisites (e.g., needing record ID), consequences of deletion, or when not to use it (e.g., for soft deletion scenarios).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

describe_object_definitionC

Get metadata and field information for a Salesforce object with pagination

ParametersJSON Schema

Name	Required	Description
`object_type`	Yes	The Salesforce object type to describe
`limit`	No	Maximum number of fields to return
`offset`	No	Number of fields to skip for pagination

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'pagination', which is a useful behavioral trait, but fails to cover other critical aspects such as whether this is a read-only operation, potential rate limits, authentication needs, or error handling. The description is minimal and does not compensate for the lack of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Get metadata and field information') and includes a key behavioral trait ('with pagination') without any wasted words. It is appropriately sized and structured for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a Salesforce object description tool with 3 parameters and no output schema, the description is incomplete. It lacks details on return values, error cases, or how pagination works in practice. Without annotations or an output schema, the description does not provide enough context for effective tool use, leaving significant gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the schema fully documents the parameters. The description adds no additional meaning beyond what the schema provides, as it does not explain parameter interactions or usage nuances. This meets the baseline of 3 for high schema coverage without extra value from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'metadata and field information for a Salesforce object', making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'list_avail_objects', which might list objects rather than describe them, leaving room for slight ambiguity in sibling context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'list_avail_objects' or 'get_record'. It mentions pagination, which hints at usage for large datasets, but lacks explicit when-to-use or when-not-to-use instructions, leaving the agent to infer context without clear direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_recordC

Retrieve a specific Salesforce record by ID with limit and pagination

ParametersJSON Schema

Name	Required	Description
`object_type`	Yes	The Salesforce object type (e.g., 'Account', 'Contact')
`record_id`	Yes	The record ID to retrieve
`limit`	No	Maximum number of records to return

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions 'limit and pagination', which adds some behavioral context beyond basic retrieval, but it doesn't disclose critical details like authentication requirements, rate limits, error handling, or what the return format looks like (especially without an output schema). This leaves significant gaps for a tool with mutation siblings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Retrieve a specific Salesforce record by ID') and adds a concise note on 'limit and pagination'. There is no wasted verbiage, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (3 parameters, no annotations, no output schema, and siblings include mutations), the description is incomplete. It lacks details on return values, error cases, and how it fits into the broader toolset (e.g., vs. 'search_records'). Without annotations or output schema, more context is needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters well. The description adds minimal value by implying 'limit and pagination' relate to the 'limit' parameter, but it doesn't provide additional semantics beyond what's in the schema (e.g., how pagination works with a single 'record_id'). Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Retrieve') and resource ('specific Salesforce record by ID'), making the purpose unambiguous. However, it doesn't explicitly distinguish this tool from sibling tools like 'search_records' or 'soql_query', which might also retrieve records, so it misses full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'search_records' or 'soql_query' from the sibling list. It mentions 'limit and pagination' but doesn't clarify if this is the preferred method for single-record lookups or when other tools might be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_avail_objectsC

List available Salesforce objects with limit and pagination (10-20 objects max)

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of objects to return (max: 20)
`offset`	No	Number of objects to skip for pagination
`custom_only`	No	If true, return only custom objects

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination and a max limit (10-20 objects), which adds some context, but fails to cover critical aspects like whether this is a read-only operation, potential rate limits, authentication requirements, or what the output format looks like. This is inadequate for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose. However, it could be slightly more structured by separating the purpose from the constraints (e.g., 'List available Salesforce objects. Supports pagination with a limit of 10-20 objects max.'), but it's still very concise with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of listing Salesforce objects, no annotations, and no output schema, the description is incomplete. It lacks details on output format, error handling, authentication needs, and how it differs from siblings. The pagination hint is helpful but insufficient for a tool with rich contextual requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all three parameters (limit, offset, custom_only). The description adds no additional parameter semantics beyond what's in the schema, such as explaining how 'custom_only' interacts with Salesforce object types. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('available Salesforce objects'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'describe_object_definition' or 'search_records' that might also provide object information, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'describe_object_definition' or 'search_records' from the sibling list. It mentions pagination and limits but doesn't specify use cases or prerequisites, leaving the agent with minimal context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_recordsC

Search for records across multiple Salesforce objects

ParametersJSON Schema

Name	Required	Description
`search_term`	Yes	The term to search for
`object_types`	Yes	List of object types to search in
`limit`	No	Maximum number of results per object type

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Search for') but lacks details on permissions needed, rate limits, pagination behavior, error handling, or what the search encompasses (e.g., fields searched). This is inadequate for a tool with potential complexity in Salesforce environments.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of searching across multiple Salesforce objects, no annotations, and no output schema, the description is insufficient. It doesn't explain return values, search scope limitations, or behavioral traits like authentication needs, leaving significant gaps for an AI agent to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear parameter descriptions in the schema. The description adds no additional meaning about parameters beyond implying a cross-object search scope, which is already suggested by the schema's 'object_types' array. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Search for') and resource ('records across multiple Salesforce objects'), providing a specific purpose. However, it doesn't differentiate from sibling tools like 'soql_query' or 'get_record', which might offer alternative search approaches, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'soql_query' (likely for structured queries) and 'get_record' (likely for single-record retrieval), there's no indication of appropriate contexts, exclusions, or prerequisites for this multi-object search tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

soql_queryC

Execute a SOQL query against Salesforce

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	The SOQL query string to execute

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action ('Execute') but doesn't cover critical aspects like authentication requirements, rate limits, query result limitations, error handling, or whether this is a read-only or mutating operation. For a query tool with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of executing SOQL queries against Salesforce (which involves syntax, permissions, result handling, etc.), no output schema, and zero annotations, the description is insufficient. It doesn't explain what the tool returns, error conditions, or important constraints, leaving the agent with inadequate context for proper usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description doesn't add any parameter information beyond what's in the schema. However, with 100% schema description coverage (the single 'query' parameter is fully documented in the schema), the baseline is 3. The description doesn't compensate but doesn't need to since the schema adequately covers the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Execute') and target ('a SOQL query against Salesforce'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'search_records' or 'get_record' which might also query Salesforce data, leaving room for ambiguity about when to use this versus those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'search_records', 'get_record', and 'list_avail_objects' that likely handle Salesforce data queries, the description offers no context about when SOQL queries are preferred over these other methods, leaving the agent without usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update_recordC

Update an existing Salesforce record

ParametersJSON Schema

Name	Required	Description
`object_type`	Yes	The Salesforce object type (e.g., 'Account', 'Contact')
`record_id`	Yes	The ID of the record to update
`update_data`	Yes	Dictionary containing the field values to update

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Update' implies mutation, it doesn't specify permission requirements, whether updates are reversible, what happens to unspecified fields, or error handling. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core purpose, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't address behavioral aspects like authentication needs, rate limits, or what the response contains. Given the complexity of updating Salesforce records, more contextual information is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and resource ('existing Salesforce record'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'create_record' beyond the 'existing' qualifier, which is insufficient for full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create_record' or 'delete_record'. It doesn't mention prerequisites, error conditions, or contextual constraints, leaving the agent with minimal usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

8 tool updatesv0.1.1Feb 9, 2026
- First observedcreate_record
- First observeddelete_record
- First observeddescribe_object_definition
- First observedget_record
- First observedlist_avail_objects
- First observedsearch_records
- First observedsoql_query
- First observedupdate_record

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. For example, create_record, get_record, update_record, and delete_record cover distinct CRUD operations, while describe_object_definition, list_avail_objects, search_records, and soql_query handle metadata, listing, searching, and querying respectively. There is no overlap that would cause misselection.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, such as create_record, delete_record, and describe_object_definition. This predictability makes it easy for agents to understand and use the tools without confusion from mixed conventions.

Tool Count5/5

With 8 tools, the server is well-scoped for Salesforce operations. Each tool earns its place by covering essential functions like CRUD, metadata access, listing, searching, and querying, without being overly sparse or bloated. This count is ideal for the domain's typical needs.

Completeness5/5

The tool surface provides complete coverage for core Salesforce interactions. It includes full CRUD operations (create, get, update, delete), metadata handling (describe_object_definition, list_avail_objects), and flexible data access (search_records, soql_query). There are no obvious gaps that would hinder agent workflows in this domain.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

kodey-ai-salesforce-mcp-minimal
ai.smithery
Run SOQL queries to explore and retrieve Salesforce data. Access accounts, contacts, opportunities…
Databases Customer Data Platforms ERP Systems
2
salesforce-devopsOAuth
cloud.serpent
Plan Salesforce deploys, open pull requests and trigger pipelines from your AI client.
CI/CD & DevOps Version Control CRM
2
kodey-ai-salesforce-mcp-server
ai.smithery
Run SOQL queries against your Salesforce org to retrieve records and insights. Explore objects, fi…
Databases Customer Data Platforms ERP Systems
2
kodey-ai-salesforce-mcp
ai.smithery
Run SOQL queries to explore and retrieve Salesforce data. Inspect records, fields, and relationshi…
Databases Customer Data Platforms ERP Systems
2

Related MCP Servers

Salesforce Basic MCP Server
Databases Customer Data Platforms ERP Systems
Luis-E-Dev
F
license
Not graded
quality
C
maintenance
Enables AI assistants to query Salesforce data including retrieving accounts by ID, searching accounts by name, and fetching recent opportunities through authenticated API access.
Updated 8 months ago (2026-01-08 03:56 UTC)
-
MCP Salesforce Server
Databases Customer Data Platforms App Automation
AiondaDotCom
A
license
A
quality
C
maintenance
Enables AI assistants to interact with Salesforce through a secure interface for performing CRUD operations, executing SOQL queries, and managing schema discovery. It features a smart learning system that analyzes custom objects and fields to provide intelligent assistance tailored to specific Salesforce configurations.
Updated 5 months ago (2026-04-06 11:14 UTC)
14
19
17
BSD 2-Clause "Simplified"
Salesforce MCP Server
Customer Data Platforms Databases App Automation
tweiss777
F
license
Not graded
quality
D
maintenance
Enables AI assistants to interact with Salesforce CRM by executing SOQL queries and performing CRUD operations on records such as Leads. It supports secure OAuth 2.0 authentication and provides management for both standard and custom Salesforce fields.
Updated 5 months ago (2026-04-18 18:17 UTC)
-
realfastAI Salesforce MCP
CRM Databases
realfastAI
A
license
Not graded
quality
D
maintenance
Enables AI models to interactively explore, analyze, and manage Salesforce organizations through OAuth2 authentication and standardized tools.
Updated a year ago (2025-05-29 09:39 UTC)
37
3
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/luvl/mcp-salesforce-lite'

If you have feedback or need assistance with the MCP directory API, please join our Discord server