asset-health-mcp

asset-health-mcp

Provides data-quality validation and anomaly scoring tools so an AI agent can decide whether to dispatch a field technician, while refusing to act on untrusted data.

Category
访问服务器

README

asset-health-mcp

An AI agent that decides whether to dispatch a field technician — and refuses to act on data it can't trust.

Agentforce agent grounded on Salesforce Data Cloud, calling a custom MCP server for data-quality validation (Great Expectations) and anomaly scoring (Databricks), with a guarded Apex write-back that creates the WorkOrder.

🎥 2-minute demo video — watch the agent validate, score, create a work order, then refuse a corrupted batch.

Why this exists

Most agent demos let the LLM act on whatever data it retrieves. In field service, acting on a corrupted meter reading means dispatching a technician for nothing — or worse, missing a failing asset. This project puts a data-trust gate in front of every agent decision:

readings ──▶ Ingestion API ──▶ Data Cloud (zero-copy grounding)
                                     │
                                     ▼
                          Agentforce agent
                          │ 1. check_reading_quality   MCP / Great Expectations
                          │ 2. score_asset_anomaly     MCP / Databricks
                          │ 3. create work order       Apex (guarded write-back)
                                     │
                                     ▼
                            Salesforce WorkOrder

Design decisions

  • Two curated MCP tools, not a data dump. The agent gets judgment (trust + severity); raw history reaches it separately through Data Cloud zero-copy grounding. Stays far inside Agentforce's tool budget.
  • Guards live server-side. The Apex action refuses untrusted data and normal-severity requests even if the agent asks — agent instructions are not a security boundary (OWASP LLM07).
  • Idempotent write-back. Agents retry; duplicate field dispatches cost real money. One open Asset Health WorkOrder per asset, enforced in Apex.
  • Runs with zero credentials. Deterministic Databricks mock + GX ephemeral context mean pytest is green on a fresh clone with no external services.

Stack

Python 3.11 · FastMCP (mcp 1.x) · Great Expectations 1.18 · Databricks (Unity Catalog) · Salesforce Data Cloud (Ingestion API, DMO grounding) · Agentforce · Apex

Repository layout

src/asset_health_mcp/    FastMCP server: tools, GX validation, Databricks client
pipeline/                Ingestion API pipeline → Meter Reading DMO (fallback path)
force-app/               Apex write-back action + tests
databricks/              PySpark scoring job → Unity Catalog Delta table with
                         UniForm (Iceberg) — zero-copy File Federation ready
snowflake/               readings warehouse DDL + least-privilege key-pair
                         integration user for Query Federation
datacloud/               ZERO_COPY.md — federation-mode decisions and setup
docs/                    AGENT_BUILD.md (Agentforce wiring), demo script
tests/                   smoke suite, green with zero external services

Zero-copy design in one line: readings stay in Snowflake (Query Federation, JDBC pushdown to an isolated XS warehouse), scores stay in Databricks (File Federation via UniForm/Iceberg, zero external compute) — mode chosen per table on cost, not by default. Details: datacloud/ZERO_COPY.md.

Run it

pip install -e ".[dev]" && pytest          # zero-credential smoke suite
python -m asset_health_mcp.server          # stdio, for Claude Desktop
MCP_TRANSPORT=streamable-http \
  python -m asset_health_mcp.server        # HTTP, for Agentforce registry
sf project deploy start                    # Apex action + tests

Full build runbook: docs/SETUP.md (step by step, ordered around trial-licence constraints) · agent wiring: docs/AGENT_BUILD.md · what runs on which edition and what is documented rather than demonstrated: docs/ENVIRONMENTS.md.

Known limits

Demo-grade auth (PAT, not OAuth service principal), precomputed scores rather than real-time model serving, single-org. Listed deliberately — the point of the project is the architecture, not production hardening.


Built by Yamyle — Senior Salesforce Architect & Data/AI Engineer. 20+ Salesforce certifications · integration frameworks for utilities and financial services.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选