Core concepts / Connectors

Connectors

Curated toolsets at audience-bound endpoints, each with its own approvals and guardrails.

Connector or endpoint bundle

An endpoint bundle publishes all tools from its selected shared or service connections. A connector is the curated option: choose an allowlist of tools, require approval for selected calls, enable payload recording, and apply response guardrails. Both use a shared /mcp/{slug} URL, and neither accepts personal connections.

Why curate

Every tool definition consumes context and gives the model another possible action. Expose writing tools to a drafting assistant, read-only tools to research, and operational tools only where they are needed. Connector policy can use redact, maxResultBytes, and disableInjectionScan.

Token boundaries

Access tokens are bound to the connector path. A token for /mcp/research cannot call /mcp or /mcp/writing. Deleting a connector changes its token epoch, so recreating the same slug does not revive old credentials.