salesforce-metadata-mcp
Related Servers
Alternatives to salesforce-metadata-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Salesforce organizations through natural language by exposing Salesforce APIs (REST, Bulk v2, GraphQL, Tooling, Auth) as MCP tools for querying data, managing records, and executing SOQL queries.12 npm19MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying and modifying Salesforce data (Accounts, Contacts, Opportunities, Leads, Cases) via MCP tools.60 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables object-agnostic Salesforce operations through 27 invocable Apex MCP tools, covering discovery, reading, writing, intent shortcuts, and flow execution. It allows any standard or custom object to be managed from MCP clients or called from Flow, Agentforce, and REST.5 npm-
- FlicenseAqualityBmaintenanceEnables users to connect to Salesforce and perform CRUD operations, run SOQL/SOSL queries, and manage records through a lightweight MCP server with built-in safety gates for writes.9-
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Salesforce through MCP, supporting queries, records, metadata, and bulk operations with flexible OAuth authentication.16MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive access to Salesforce Tooling API for metadata management, SOQL queries, code analysis, and debugging through Claude and other AI assistants.60 npm5MIT
TDQS
Scored across 20 tools
Each tool targets a distinct metadata operation with clear descriptions, making most boundaries easy to identify. Some ambiguity exists between sf_create_custom_field and sf_create_formula_field, since a formula field is a type of custom field, and several tools say "creates or updates" rather than separating those actions.
All tools share the sf_ prefix and mostly follow a verb_noun pattern such as sf_create_custom_object, sf_retrieve_metadata, and sf_delete_metadata. The main deviation is sf_tool_schema, which lacks a verb, and minor semantic variation among verbs like add, get, and query, but the overall convention is consistent.
Twenty tools is on the heavy side for a single server, though the broad Salesforce metadata domain justifies much of it. The five tool-management tools add overhead, but they serve a clear purpose given the server's 228-tool backend.
The set covers the core metadata lifecycle well: create, retrieve, deploy, check status, and delete, plus object discovery, schema description, SOQL querying, and dependency analysis. Minor gaps exist, such as no explicit update tool for custom objects/fields and no metadata listing beyond object discovery, but the generic deploy and delete tools cover most needs.