salesforce-mcp-jsforce
Related Servers
Alternatives to salesforce-mcp-jsforce
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides read-only access to Salesforce orgs via MCP, enabling SOQL queries, sObject descriptions, and object listing using OAuth 2.0 Client Credentials.-
- 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-
- AlicenseNot gradedqualityCmaintenanceEnables querying and modifying Salesforce data (Accounts, Contacts, Opportunities, Leads, Cases) via MCP tools.42MIT
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Salesforce through MCP, supporting queries, records, metadata, and bulk operations with flexible OAuth authentication.16MIT
- AlicenseNot gradedqualityDmaintenanceConnects any MCP-compatible AI assistant directly to a Salesforce org for querying data, exploring schema, running Apex, and managing deployments.18MIT
- FlicenseBqualityDmaintenanceA customizable MCP server for integrating Salesforce APIs with GenAI applications, supporting SOQL queries, record CRUD, metadata access, and more.136-
TDQS
Scored across 9 tools
Each tool targets a clearly distinct Salesforce operation: authentication, SOQL query, SOSL search, object metadata listing, single-object description, and record CRUD. There is minimal risk of an agent selecting the wrong tool because the boundaries between query/search, list/describe, and get/query are well-defined.
All tools share the salesforce_ prefix and use snake_case, which creates a strong sense of uniformity. However, salesforce_identity, salesforce_query, and salesforce_search are bare verbs/nouns while the rest use a verb_noun pattern like salesforce_get_record, so there is a minor stylistic deviation.
Nine tools is a well-scoped set for a Salesforce MCP server. Each tool covers a distinct core capability without redundancy, and the count is within the ideal range for an agent to discover and use the full surface comfortably.
The server provides a complete lifecycle for records: get, create, update, and delete, plus query, search, and object metadata inspection. This covers the primary workflows an agent would need when interacting with Salesforce, with no obvious dead ends or missing essential operations.