Salesforce Object MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SF_REPO_PATH | Yes | Path to the Salesforce repository containing `.object-meta.xml` and `.field-meta.xml` files |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_objectsA | List all Salesforce objects found in the repository. Optionally filter by pattern or exclude standard objects. |
| get_object_detailsA | Get comprehensive details about a specific Salesforce object including all fields, validation rules, and metadata. |
| list_fieldsB | List all fields for a specific Salesforce object. Optionally filter by field type. |
| get_field_detailsA | Get detailed information about a specific field including type, length, formula, picklist values, and relationship information. |
| find_relationshipsA | Find all relationships for an object. Can show outgoing relationships (lookups from this object), incoming relationships (lookups to this object), or both. |
| search_metadataA | Search across all metadata by keyword. Searches object names, labels, field names, descriptions, and formulas. |
| get_validation_rulesA | Get all validation rules for an object including formulas, error messages, and active status. |
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 7 tools
Most tools have clear, distinct purposes, but get_object_details overlaps with list_fields and get_validation_rules by returning fields and validation rules as part of its comprehensive output. This creates minor boundary ambiguity, though descriptions help an agent choose between a targeted call and a comprehensive call.
Every tool follows a consistent verb_noun snake_case pattern: list_, get_, find_, search_. The naming is predictable and makes the purpose of each tool immediately clear.
Seven tools is well-scoped for a Salesforce metadata exploration server. Each tool covers a meaningful part of the domain without unnecessary bloat or obvious redundancy.
The surface covers the core metadata discovery workflow: listing objects, listing fields, getting field details, finding relationships, accessing validation rules, and searching metadata. For a read-only metadata exploration server, there are no significant gaps.