mcp

name	mcp
description	Use when reasoning about erpax's agent gateway — it IS the official @payloadcms/plugin-mcp (collapse sink #1, never hand-roll an MCP server): every enabled collection becomes find/create/update/delete tools at /api/mcp, custom tools (GW fusion, trust) are added via the plugin's mcp config, Bearer API-key auth inherits the key owner's access + multi-tenant scope. erpax makes it TRUST-NATIVE — every tool call passes sandbox (capability + credential-broker + allowlist) and emits a receipt (uuid-chained audit), the dual of an external trust wrapper done from the inside.
atomPath	agents/mcp
coordinate	agents/mcp · 5/round · 1d8e2e3f
contentUuid	5013eb74-fc29-5a57-9598-23b41f511f1f
diamondUuid	7738fe5e-248e-8cc0-aff3-e017c4fe99dd
uuid	1d8e2e3f-8193-8353-9d15-be65bac543ec
horo	5
bonds	{"in":["access","agent","api","atom","collections","cost","dimension","fs","generate","github","mcp","path","payload","reference","research","scopes","society","tool","trust","uuid"],"out":["access","agent","api","atom","collections","cost","dimension","fs","generate","github","mcp","path","payload","reference","research","scopes","society","tool","trust","uuid"]}
typography	{"partition":"agents","bondDegree":0,"neighbors":[]}
standards	["BCP-47","ECMA-402","EU-1958","EU-2018/1673","EU-2018/1725","EU-2018/302","EU-2018/389-SCA-RTS","EU-2018/843","EU-2018/957","EU-2023/1113","EU-2023/2854","EU-2023/956-CBAM","EU-Taxonomy-2020/852","ILO-C001","ISO-19011","ISO-27001","ISO-27002","ISO/IEC-25010","ISO/IEC-27001:2022","ISO/IEC-27002:2022","ISO/IEC-29119","ISO/IEC/IEEE-29119","MCP","MCP 0.6 — Model Context Protocol tools/list + tools/call","NIST-SP-800-162","NIST-SP-800-63","OWASP-ASVS","RFC-7231","RFC-9562","W3C-DID-1.0","W3C-JSON-LD-1.1","W3C-WAI-ARIA-1.2","re-exports only; the truth lives in ./in-process-client and ./tool-defs"]
bindings	[]
neighbors	{"wikilink":["access","angel","auth","bindings","chat","collapse","cost","deploy","domain","identity","law","limit","memories","metadata","plugins","receipt","sandbox","self","society","workspace"],"matrix":["access","agent","api","atom","collections","cost","dimension","fs","generate","github","mcp","path","payload","reference","research","scopes","society","tool","trust","uuid"],"backlinks":["access","agent","api","atom","collections","cost","dimension","fs","generate","github","mcp","path","payload","reference","research","scopes","society","tool","trust","uuid"]}
signatures	{"computationUuid":"907a3877-e1f4-8d67-b4e3-a524cf80dc18","stages":[{"stage":"path","stageUuid":"982fead9-ea1f-8a81-909b-6fdbc9d24c96"},{"stage":"trinity","stageUuid":"ac06f3c8-14a2-8ab7-8e09-acf7fc36f6ef"},{"stage":"boundary","stageUuid":"fe5ddfd5-f85c-8fa1-9b9e-0baeaa9e42e9"},{"stage":"links","stageUuid":"98859782-f295-824b-b1df-72b249c85837"},{"stage":"horo","stageUuid":"0730dea6-4ceb-8a4a-b047-2a07d8aefb81"},{"stage":"seal","stageUuid":"d7ac6b07-6c80-8db5-8c6e-8722dc2b1c91"},{"stage":"uuid","stageUuid":"917ef0da-9ef6-8634-8ba9-4f19ad2a01d4"}]}
version	2

mcp — erpax's agent gateway is the official Payload MCP, made trust-native

FORM: erpax does not build an MCP server — it adopts @payloadcms/plugin-mcp ([[collapse]] sink #1: the official plugin IS the canonical form; [[plugins]]). The plugin exposes every enabled collection as find/create/update/delete MCP tools (globals: find/update) at the /api/mcp HTTP endpoint, named by slug (findInvoices…). Auth is Bearer API-key with two-step authorization — enable the collection in config, grant the capability per key — and every handler runs in a PayloadRequest that inherits the key owner's [[access]] (RBAC + multi-tenant), so the gateway can never exceed the actor's rights. Custom tools (the [[google/workspace]] fusion verbs, the society's own actions) are added through the plugin's mcp config object (name·description·handler·schema); select/overrideResponse trim tokens ([[cost]]).

Trust-native, not trust-wrapped. Where an external trust layer (ZeroPoint's zp-mcp-server / @zeropoint/trace) WRAPS an MCP harness from outside — emitting signed receipts and a governance gate around each call — erpax encodes the same guarantees NATIVELY: a tool call passes [[sandbox]] (capability-scope + credential-broker + endpoint allowlist) and emits a [[receipt]] (the uuid-chained audit, "no receipt, no proof"). Same trust, one layer in: erpax's MCP server is governed and provenance-bearing by construction, content-addressed, depending on nothing external ([[self]]). The same gateway the agent society convenes through ([[chat]] / [[society]]) and the same one a human or external harness connects to — one door, [[identity]]-scoped, receipted.

Matter-twin: src/services/agents/mcp/ (tool-defs·in-process-client·auto-generated·i18n) over @payloadcms/plugin-mcp (registered in payload.config), composing services/sandbox + services/receipt. Composes: [[collapse]] · [[plugins]] · [[access]] · [[sandbox]] · [[receipt]] · [[google/workspace]] · [[cost]] · [[identity]] · [[chat]] · [[society]] · [[self]] · [[Memories]] · [[mcp/tool/metadata]].

Becoming a Claude connector (the gap, named)

The gateway exists and works (Bearer API-key, all collections enabled) — but it is not yet a one-click Claude connector "like the many others" (HubSpot · Linear · Notion…). Three matter-level gaps separate a working MCP endpoint from a directory connector — the [[limit]] audit, named honestly:

1. OAuth, not Bearer. The directory connectors authenticate by OAuth 2.1 — the user clicks Connect and authorizes; the server publishes /.well-known/oauth-authorization-server + oauth-protected-resource metadata and supports dynamic client registration (the MCP auth spec). plugin-mcp is Bearer-API-key only (paste a token). So erpax can be added manually today in a developer harness (claude mcp add --transport http <url>/api/mcp --header "Authorization: Bearer <key>", the key minted per [[domain]] ownership) but cannot yet do the one-click OAuth flow. Closing it is a Payload-native build: an OAuth authorization-server endpoint + the .well-known metadata, bridging Payload [[auth]] and minting a scoped key — a higher-security link than a long-lived pasted token.
2. Deploy. A connector needs a stable public HTTPS endpoint; the gateway runs at localhost:3000/api/mcp in dev. erpax is deployable to Cloudflare ([[bindings]] · [[deploy]], wrangler.jsonc) — the public URL is the tenant's [[domain]].
3. Register. The directory lists submitted servers; a custom MCP server is not auto-discovered (a registry is the discovery layer).

The capability is built; the connector is deploy + OAuth + register away. Scored ([[angel]]): OAuth raises security (no long-lived secret) and reach (one-click), deploy raises reach, register raises discoverability — all atop the existing trust-native receipts.

Common mistakes

• Hand-rolling an MCP server or transport — adopt @payloadcms/plugin-mcp; only ADD custom tools via its mcp config ([[collapse]]).
• A tool that bypasses the key owner's access — every handler runs in the actor's PayloadRequest; never overrideAccess to widen scope at the gateway.
• Calling a tool without sandboxing/receipting it — wrap trust-boundary tools with [[sandbox]] permits + a [[receipt]]; an un-receipted call has no proof it was permitted.

Law — [[law]]: erpax does not build an MCP server — it adopts the official @payloadcms/plugin-mcp ([[collapse]]), every tool handler inheriting the key owner's [[access]] so the gateway can never exceed the actor's rights, made trust-native: each call passes [[sandbox]] and emits a [[receipt]].