MCP

MCP is a surface, not the source of truth.

SiteKit generates MCP tools from reviewed adapter operations. The TypeScript and Python clients remain usable without MCP, which keeps data pipelines first-class.

Only verified operations are exposed as MCP tools by default.

sitekit mcp serve source_portal destination_portal

Tool Names

source_portal_users_list
source_portal_events_list
source_portal_reports_download_csv
destination_portal_records_update
destination_portal_locations_resolve

Tool descriptions come from reviewed operation docs and schema annotations:

destination_portal_records_update

Update a destination record. Reads the current record first and sends the full
editable field set. Notifications are disabled by default. Requires
confirm=true to write.

Write Safety

Write operations can expose a preview mode:

{
  "wouldSend": {
    "status": "scheduled",
    "location_id": 623932,
    "send_notification": false
  },
  "note": "Pass confirm=true to apply."
}

Human approval policy lives above SiteKit. The adapter only provides deterministic preview and apply behavior.

Agent Instructions

Generated MCP servers include source-of-truth notes:

• Source Portal is authoritative for source records in this workspace.
• Destination Portal receives reviewed updates.
• Analytics Portal contributes derived metrics, not source records.

Those notes help downstream agents choose tools correctly, but they are generated from reviewed adapter metadata rather than remembered from a conversation.

The notes are descriptive, not workflow logic. They can tell an agent what a site or connection represents. They should not decide how to reconcile two systems, when to notify someone, or whether a write should be approved.