pulsemcp verified Safe content atomic mcp-remote

Salesforce Data Cloud

MCP server implementation by CData Software that provides AI assistants with access to Salesforce Data Cloud through a generic JDBC-based architecture. Built in Java using the Model Context Protocol SDK, the implementation offers three core tools: get_tables for discovering available data objects and collections, get_columns for retrieving field metadata and data types, and run_query for executing SQL SELECT statements with results returned in CSV format. The server uses CData's JDBC driver architecture to connect to Salesforce Data Cloud, supporting dynamic discovery of database metadata including catalogs, schemas, and table structures, with configurable identifier quoting and SQL dialect handling. Designed for data analysts and developers who need programmatic access to Salesforce Data Cloud for querying customer data, building reports, or integrating Salesforce analytics into AI-powered workflows where structured data access through familiar SQL interfaces is preferred over native Salesforce APIs.

Cognium trust score

99%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/cdatasoftware/salesforce-data-cloud-mcp-server-by-cdata
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Salesforce Data Cloud from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"