MCP access
Review MCP actions before execution
Run example
Clone relay-action-card
Request access
Use Workspace or private token
Connect MCP
Send POST /mcp
Runtime acts
Execution stays with you
Connect MCP to Relay
Use Workspace access for POST /mcp
{ "server_url": "https://www.neurarelay.com/mcp", "transport": "streamable_http", "headers": { "Authorization": "Bearer <RELAY_MCP_TOKEN>" }}Expand full example
{ "server_url": "https://www.neurarelay.com/mcp", "transport": "streamable_http", "headers": { "Authorization": "Bearer <RELAY_MCP_TOKEN>" }, "allowed_tools": ["validate_action_card", "resolve_action_card"], "require_approval": "always"}Five protected tools
Each tool checks or returns safe review information; none executes the action
validate_action_card
Check proposed action shape
Read-only
resolve_action_card
Return review result and trace refs
Review write
get_decision_receipt
Fetch a safe decision summary
Read-only
get_trace_replay
Fetch redacted trace replay
Read-only
lookup_agent_passport
Read Registry standing
Read-only
Troubleshooting
Keep debugging inside safe refs and status codes
A 401 response means the MCP client needs a valid Workspace token or controlled private access tied to Registry identity. Unauthenticated requests return discovery metadata for compatible clients.
A 405 response means the method is unsupported for the protected MCP endpoint. Use Streamable HTTP with POST /mcp and the bearer header.
For support, share decision refs, trace refs, transaction refs, and Registry refs only. Do not share token values, passwords, private payloads, or secret keys.