MCP Salesforce Lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SALESFORCE_ACCESS_TOKEN | Yes | Your Salesforce access token | |
| SALESFORCE_INSTANCE_URL | Yes | Your Salesforce instance URL (e.g., https://yourcompany.my.salesforce.com) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| soql_queryC | Execute a SOQL query against Salesforce |
| search_recordsC | Search for records across multiple Salesforce objects |
| get_recordC | Retrieve a specific Salesforce record by ID with limit and pagination |
| create_recordC | Create a new Salesforce record |
| update_recordC | Update an existing Salesforce record |
| delete_recordC | Delete a Salesforce record |
| describe_object_definitionC | Get metadata and field information for a Salesforce object with pagination |
| list_avail_objectsC | List available Salesforce objects with limit and pagination (10-20 objects max) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.