Neura Relay MCP
Gate risky agent tool calls by routing proposed Action Cards through Relay for Decision Receipts and an auditable trail before your code executes changes.
Overview
Neura Relay MCP is an MCP server for the Ship phase that governs proposed Action Cards with Decision Receipts before developer-owned execution.
What is this MCP server?
- Optional protected MCP layer on Action Card → Relay → Decision Receipt flow
- Bearer NEURA_RELAY_MCP_TOKEN (sandbox or production after trust review)
- Tags: agent-governance, tool-calling, audit-trail, agent-identity
- Streamable HTTP at www.neurarelay.com/mcp with Authorization header
- Documentation at neurarelay.com/developers/mcp for integration patterns
- Core flow: Action Card → Relay → Decision Receipt → trace/ledger/Registry
- MCP role documented as optional_protected_compatibility_not_core_architecture
- Remote type streamable-http with required secret bearer token
What problem does it solve?
Autonomous agents can fire tool calls that change production systems with no durable record of who proposed what or why it was allowed.
Who is it for?
Builders running agent tool-calling against sensitive APIs who need receipts, identity context, and a review gate.
Skip if: Hobby projects with read-only local tools or teams that only need DNS/JSON utilities without governance overhead.
What do I get? / Deliverables
Proposed actions pass through Relay governance so you get Decision Receipts and audit context before your own execution path runs.
- Governed Action Card proposals via MCP
- Decision Receipts tied to trace/ledger/registry context
- Auditable agent-identity and tool-call policy path before your executor runs
Recommended MCP Servers
Journey fit
Governance and pre-execution review belong in Ship because solo builders harden how agents act on production-adjacent systems before launch. Security fits Neura Relay’s core path—Action Card, Relay, Decision Receipt, trace/ledger—because it is about approving and auditing actions, not writing features.
How it compares
Agent governance and audit MCP, not a generic dev utility or observability query server.
Common Questions / FAQ
Who is Neura Relay MCP for?
Developers and small teams building MCP-connected agents who need Action Card review, Decision Receipts, and audit trails before executing high-impact tools.
When should I use Neura Relay MCP?
Use it in Ship when you are locking down tool-calling—payments, deploy hooks, data writes— and want Relay to govern proposals instead of blind execution.
How do I add Neura Relay MCP to my agent?
Add the streamable HTTP remote https://www.neurarelay.com/mcp with header Authorization: Bearer {NEURA_RELAY_MCP_TOKEN}, using a Relay sandbox or approved production token.