Data 360 MCP Server

The data/data-360 server exposes Data 360’s Connect API through MCP, so agents can query, transform, and activate customer data programmatically.

Use this server to:

  • Query unified customer profiles, trigger segmentation, and manage identity resolution through MCP
  • Manage unified profiles and calculated insights at runtime via API
  • Ingest, transform, and activate data through API prompting
  • Configure data mappings, identity resolution, and developer environments

The server exposes three meta-tools (tools that manage other tools): search, payload_examples, and execute. These tools discover the correct Connect API at runtime rather than loading all of them up front, which keeps token usage low regardless of how many Data 360 APIs exist.

Use the Data 360 MCP server to create, list, update, and delete:

  • Data lake objects (DLO)
  • Data model objects (DMO)
  • Data streams
  • Transforms
  • Calculated insights
  • Segments
  • Activations and activation targets
  • Data actions and data action targets
  • Data spaces
  • Data kits
  • RAG retrievers and retriever configurations
  • Semantic search indexes
  • Semantic data models (SDM) and SDM entities (data objects, calculated dimensions/measurements, metrics, relationships)
  • DLO-to-DMO mappings (including field mappings)

Note: This MCP server replaces the previous Data 360 server, which is now available as the Data 360 Legacy MCP Server.

The Data 360 MCP is available with API v66.0 and later. MCP server calls count as calls to the underlying Connect API endpoints for limits and Flex Credit usage. See Data Cloud License Billing and Limits.

  • Data 360 license enabled in your org
  • API v66.0 or later
  • Permissions:
    • Manage Data 360 for configuration operations
    • View Data 360 for read-only operations
  • MCP client installed and configured with OAuth authentication

For setup instructions, see Set Up Your Org.

Use these server URLs to access the production, sandbox, and scratch versions of the data-360-mcp server.

  • Production: https://api.salesforce.com/platform/mcp/v1/data/data-360-mcp
  • Sandbox/Scratch: https://api.salesforce.com/platform/mcp/v1/sandbox/data/data-360-mcp
  • “What data is available about {customer name} in Data 360?”
  • “Query the unified customer profile for contacts at Acme Corp — show engagement scores and last interaction dates.”
  • “What are the top 20 accounts by product usage events in the last 30 days?”
  • “Show me all customers who received a marketing email last week but haven’t opened it.”
  • “Pull the behavioral data for customer ID cust_abc123 from Data 360.”

The data/data-360 server provides the following tools. Use them in this order for the best result.

  • search: identifies the correct tool to use
  • payload_examples: provides payload examples
  • execute: executes tool with payload

Describe what you want to do in natural language. The server scores tool families by intent and returns matching tool names.

Params: query (natural-language intent)

Given a tool name, returns its input JSON Schema, an example payload, and a human-readable description.

Params: toolName

Names a tool and passes its arguments as a JSON string. The server dispatches to the underlying Connect API and returns the result.

Params:

  • toolName — the tool to invoke
  • paramsJson — parameters as a JSON string matching the tool’s schema

Long-running queries return a queryId. Poll d360_query_sql_status and page results with d360_query_sql_rows.