Skip to main content
Enfors exposes a remote Model Context Protocol (MCP) server so external AI clients can query your workspace and render branded views — the read side of Enfors. It’s how the Ask Enfors experience works.

​
Endpoint

The server is mounted at /mcp on the Enfors Data API and speaks streamable HTTP.

​
Authentication

The endpoint is protected by OAuth 2.0 / SSO. Clients that support OAuth (Claude Desktop, Claude Code, Cursor) will run the authorization flow automatically when you add the server — Enfors advertises its OAuth resource metadata at the /mcp path. This is the same SSO sign-in the watcher uses. Programmatic clients can instead present a Personal Access Token as a bearer token:
Every tool call is scoped to your tenant, workspace, and user via Row-Level Security — you can only ever query data you’re entitled to. See Tenancy, Privacy & PII.

​
Connect a client

Enfors connects as a custom connector. Custom connectors are available on all Claude plans (free plans are limited to one custom connector).
1

Open connector settings

Go to Settings → Connectors (under Customize), click Add, and choose Add custom connector.
2

Enter the Enfors server details

Name it enfors and set the URL to:
Leave the OAuth Client ID and secret empty — Enfors advertises its own OAuth metadata. Click Add.
3

Authorize

Claude opens the Enfors OAuth / SSO flow in your browser. Sign in with your Enfors account; the connector shows a checkmark once connected.
4

Set tool permissions

Open the connector to review Tool permissions. Each Enfors tool defaults to Needs approval; since all tools are read-only and RLS-scoped, it’s safe to set them to Allow for a smoother experience.
5

Enable it in a chat

In a conversation, click the + button, hover over Connectors, and toggle enfors on. The Enfors tools are now available to Claude.
Custom connectors reach the MCP server from Anthropic’s cloud, not from your device. The Enfors endpoint is publicly reachable, so no network changes are needed. See Anthropic’s guide: Use connectors to extend Claude’s capabilities.

​
What you can do

Explore the hierarchy

list_agents → list_agent_sessions → list_session_decisions → get_decision.

Query across decisions

list_decisions with time, outcome, intent, cost, and quality filters.

Traverse the graph

query_graph for evidence, subjects, and agent networks.

Semantic search

search_similar_decisions to find decisions like a description.

Delivery & ROI

list_features, get_feature, list_feature_merge_suggestions.

Insights & Pulse

list_insights and get_pulse_report.

​
Rendering results

Whenever a client shows Enfors data to a user, it should call render_ui to present it as a branded, interactive view rather than raw text or HTML in the reply. Next: the full tool reference.