salesforce-data-cloud-mcp-server-by-cdata
Provides a read-only Model Context Protocol (MCP) server that exposes Salesforce Data Cloud as relational SQL tables by wrapping CData's JDBC Driver. It runs as a local process using stdio and offers MCP tools for listing tables/columns and running SQL SELECT queries.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security controls are largely inherited from CData JDBC driver and Salesforce. The README describes local stdio operation and provides a .prp configuration that includes a JDBC URL/connection string (which may contain credentials or OAuth parameters depending on setup). No explicit mention of TLS requirements, secret storage/redaction, MCP transport security, or fine-grained authorization/scope enforcement at the MCP layer is included in the provided documentation.
⚡ Reliability
Best When
You need local, interactive read-only access to Salesforce Data Cloud through an MCP client and can provide a working CData JDBC driver connection string/credential setup.
Avoid When
You need a network-accessible service with strong API-level auth controls, or you require guaranteed pagination/streaming, robust structured error handling, and explicit rate-limit guidance at the MCP layer.
Use Cases
- • Query Salesforce Data Cloud data from an MCP-enabled LLM client (e.g., Claude Desktop) without writing SQL
- • Explore available tables/columns and retrieve small/medium result sets via natural-language questions
- • Use SQL SELECT for targeted analytics/reporting over Data Cloud data
Not For
- • Unrestricted write/update/delete operations (server is explicitly read-only in this repo)
- • Centralized multi-tenant API serving over a network (server uses stdio and is intended for local same-machine clients)
- • High-throughput/batch ingestion use cases where pagination/streaming and robust retry semantics are required
Interface
Authentication
Authentication is delegated to the CData JDBC driver. The README notes that if the data source uses OAuth, you must authenticate in a browser during connection-string setup. No explicit MCP-layer scope/permission model is described in the provided README.
Pricing
Pricing is not described for the MCP server in the README; CData JDBC driver licensing is required (trial or license key mentioned).
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it can only be used with clients running on the same machine
- ⚠ Large result sets may be problematic because output format is described as CSV with headers but no pagination/limits are documented
- ⚠ OAuth authentication (if required) happens during connection-string build; failing/expired OAuth credentials may prevent tool use
- ⚠ Tool names are prefixed dynamically via the .prp Prefix property; agents must use the correct servername/tool names
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for salesforce-data-cloud-mcp-server-by-cdata.
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.