{"id":"cdatasoftware-salesforce-data-cloud-mcp-server-by-cdata","name":"salesforce-data-cloud-mcp-server-by-cdata","homepage":null,"repo_url":"https://github.com/CDataSoftware/salesforce-data-cloud-mcp-server-by-cdata","category":"ai-ml","subcategories":[],"tags":["mcp","data-warehouse","salesforce","jdbc","cdata","read-only","stdio","claude-desktop"],"what_it_does":"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.","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"],"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.","alternatives":["CData’s non-MCP JDBC usage directly from your own app","CData’s (referenced) MCP Server for Salesforce Data Cloud with fuller CRUD capabilities","Salesforce-native query/data access methods (e.g., APIs for Data Cloud) wrapped by your own service","Other MCP-to-database bridge solutions (if available)"],"af_score":48.0,"security_score":37.8,"reliability_score":15.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:58:23.582511+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["CData JDBC driver connection string (including optional OAuth flow via browser)","CData JDBC driver licensing step (trial/license key)"],"oauth":true,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing is not described for the MCP server in the README; CData JDBC driver licensing is required (trial or license key mentioned)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":48.0,"security_score":37.8,"reliability_score":15.0,"mcp_server_quality":70.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":60.0,"rate_limit_clarity":5.0,"tls_enforcement":20.0,"auth_strength":55.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":50.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":0.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"Tools include SELECT-only queries, which are typically safe to retry, but the README does not define idempotency semantics for MCP tool calls.","pagination_style":"none","retry_guidance_documented":false,"known_agent_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"]}}