forcedotcom/d360-mcp-server

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

19 stars 13 forks 品質 71 トレンド 26Apache-2.0

A Model Context Protocol server that exposes the Connect API to MCP-compatible clients such as Claude Code, Cursor, and any other host that speaks MCP over STDIO.

概要

A Model Context Protocol server that exposes the Connect API to MCP-compatible clients such as Claude Code, Cursor, and any other host that speaks MCP over STDIO. The Data 360 MCP server is provided as a developer preview running in a single user/org context per process. We strongly encourage use only via STDIO instead of making this server network-accessible. The generally available version of this MCP server is slated to be provided as a hosted and managed Salesforce Platform MCP server, alongside other existing Product Integration MCP servers. During the developer preview please share feature requests, issues, success stories, or other feedback via github issues on this repo, the R&D team will be actively reviewing these on a regular basis. We're especially interested in feedback about how effective the fascade tools approach works across use cases and clients. Data 360 exposes ~190 distinct REST operations.

README

以下は原文 README の抜粋です。原文を見る。

Data 360 MCP Server

A Model Context Protocol server that exposes the Salesforce Data 360 Connect API to MCP-compatible clients such as Claude Code, Cursor, and any other host that speaks MCP over STDIO.

Built on Spring AI.

Developer Preview

The Data 360 MCP server is provided as a developer preview running in a single user/org context per process. We strongly encourage use only via STDIO instead of making this server network-accessible.

The generally available version of this MCP server is slated to be provided as a hosted and managed Salesforce Platform MCP server, alongside other existing Product Integration MCP servers.

During the developer preview please share feature requests, issues, success stories, or other feedback via github issues on this repo, the R&D team will be actively reviewing these on a regular basis. We’re especially interested in feedback about how effective the fascade tools approach works across use cases and clients.

How it works

Data 360 exposes ~190 distinct REST operations. Rather than registering one MCP tool per endpoint (which quickly overwhelms an LLM’s tool list and context window), this server consolidates everything behind three facade tools:

Tool	Purpose
`search`	Discover tools by intent, keyword, or family
`payload_examples`	Fetch working JSON payloads for complex tools
`execute`	Run any underlying tool by name with parameters

Typical workflow: search → payload_examples → execute.

Under the hood, 201 operations are organized into 22 tool families:

Family	Tools	Description
DLO	5	Data Lake Object CRUD
DMO	5	Data Model Object CRUD
Data Streams	9	Ingestion pipelines — generic, SFDC CRM, Snowflake, AWS S3
Mappings	7	DLO-to-DMO field mappings
Data Transforms	9	SQL transforms — CRUD, run, validate, schedule
Identity Resolution	8	IR rulesets — create, run, publish
Calculated Insights	10	CI CRUD, run, validate, query
Segment	6	Segment CRUD + publish
Dataspace	8	Dataspace + member management
Connection	11	Connector metadata, connection CRUD, Snowflake connections
Query	16	SQL, profile, datagraph, and metadata queries
Activation	10	Activation + target CRUD
SDM	38	Semantic Data Models — dimensions, measures, relationships, queries
Retriever	10	RAG retriever + configuration CRUD
DataKit	9	Bundle deploy / undeploy
Data Action	8	Action + target CRUD
Search Index	7	Vector / hybrid search index lifecycle
Smart Tools	4	AI-assisted mapping suggestions, event-date recommendations
Standard Mappings	2	Pre-configured mapping bundles
Eventing	2	Single + batch event publish

GitHub で README 全文を見る

インストール

This server does not publish a one-line install command.

Open the repository installation guide MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

{
  "mcpServers": {
    "data360": {
      "command": "java",
      "args": [
        "-jar", "/path/to/data360-mcp-server-1.0.0.jar"
      ],
      "env": {
        "DATA360_INSTANCE_URL": "https://your-instance.my.salesforce.com",
        "DATA360_ACCESS_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}