salesforce-mcp-server-h
An MCP server package intended to expose Salesforce capabilities to AI agents via the Model Context Protocol, enabling agent-driven actions such as querying and managing Salesforce data (exact tool surface not provided in the prompt).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No implementation details were provided in the prompt. This assessment assumes a self-hosted MCP server that must securely handle Salesforce tokens and enforce least-privilege (scopes/permissions). Verify: HTTPS/TLS enforcement, token storage/logging, least-privilege Salesforce permissions, and how the MCP server sanitizes tool inputs/outputs.
⚡ Reliability
Best When
You want an MCP-native integration so an agent can call Salesforce tools using a standard MCP interface.
Avoid When
You cannot provide/secure Salesforce auth details or you need strong guarantees about data handling, logging, and least-privilege enforcement without reviewing the actual implementation.
Use Cases
- • Letting an AI agent read Salesforce records for support/debugging
- • Automating Salesforce workflows by performing agent-initiated actions (create/update)
- • Building internal agent assistants that need Salesforce CRM context
Not For
- • Directly running without credentials/configuration (Salesforce connection details not provided)
- • Highly regulated production use without verifying the security behavior of the MCP server and Salesforce permissioning
- • Use as a general-purpose Salesforce SDK if you require a full REST/GraphQL client surface
Interface
Authentication
Auth mechanisms are not explicitly provided in the prompt; scoring is based on typical Salesforce integration patterns for MCP/agent servers and should be verified in the package docs/code.
Pricing
Pricing not provided; as a library/server integration it may be self-hosted, but no cost details are included in the prompt.
Agent Metadata
Known Gotchas
- ⚠ Salesforce APIs often have strict rate limits and pagination semantics; without documented retry/pagination behavior, agents may miss/loop.
- ⚠ Agents may attempt writes (create/update) without clear idempotency guarantees unless the MCP tools explicitly enforce safe behavior.
- ⚠ OAuth/token expiration can cause mid-run failures if refresh behavior is not documented/implemented.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for salesforce-mcp-server-h.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.