AI & MCP connector
Prism exposes a Model Context Protocol (MCP) connector so an AI assistant can read your Prism data and take a few guarded actions — all inside your organization, with your permissions.
The connector lives at mcp.prism.intrasys.ai.
Authentication
The connector uses OAuth 2.1. When you connect an AI client, you sign in and consent for a specific organization — the resulting token is bound to that one org, and every tool call runs in it. Your org must be linked first (a one-time platform-admin step); ask Intrasys if a client reports the org isn't connected.
Every tool call is rate-limited and audited.
Read tools
The assistant can read (never mutating anything):
| Tool | Returns |
|---|---|
list_facets / get_facet | Facets and their detail. |
list_sites | Sites. |
list_refractions / get_refraction | Refractions and their graphs. |
list_capture_sets / query_capture_set | Capture Sets and their rows. |
recent_signals | The recent Signal timeline. |
list_executions / get_execution | Refraction runs and their stage results. |
get_trigger_samples | Real trigger payloads for a Refraction. |
list_approvals | Pending human-approval items. |
get_version | Platform version. |
Write tools
A few actions are allowed, each behind an explicit confirmation gate (the client asks you to approve before it runs, and fails closed if it can't):
| Tool | Action | Role |
|---|---|---|
decide_approval | Approve or reject a paused Refraction. | Operator+ |
enable_refraction | Enable a Refraction. | Admin |
disable_refraction | Disable a Refraction. | Admin |
run_refraction_test | Run a Refraction test — a live run. | Admin |
Prompts
The connector also ships ready-made prompts an assistant can use: diagnose an offline facet, summarize a capture set, and draft a refraction.