NerveMCP
Bring more tools to Nerve with MCP
MCP-compatible servers can extend what Nerve works with, while Nerve continues to govern how every capability is used.
NerveMCP
Bring more tools to Nerve with MCP
Nerve can discover what an MCP server offers without automatically handing those capabilities to every Agent. A person reviews each one, then grants it to the Agents that should have it.
- 1The server lists its tools. Nerve stores them as inert information.
- 2A person reviews a tool and how risky it is.
- 3Only then can it be granted, to specific Agents, and revoked at any time.
Orders server · example MCP server
search_ordersReads data
Find an order by customer or number
Discovered
get_customerReads data
Read a customer's profile
Discovered
create_refundChanges data
Refund part or all of an order
Discovered
delete_customerChanges data
Remove a customer record
Discovered
The server offers 4 tools. None is available to any Agent yet.
Example server with sample tools
How Nerve treats MCP
- 01Discovered is not executable
- When you connect an MCP server, Nerve lists what it offers and stores that as information. Nothing it lists can run until a person has reviewed it.
- 02Reviewed, then granted
- A person checks each tool and how risky it is, then grants it to the Agents that should have it. Grants can be revoked at any time.
- 03Changes need review again
- If a server changes a tool after it was reviewed, that tool stops running until it is reviewed again. A server cannot widen what a tool does on its own.
- 04The same controls as everything else
- MCP tools pass the same checks as any other capability: identity, current permissions, connection, grant, risk and approval, and every call is recorded.
- 05Private to your organization
- The MCP servers you connect belong to you. They are never listed publicly and are never visible to other organizations.
- 06Nerve works as a server too
- You can share chosen capabilities with compatible AI clients. It is off by default, shared one capability at a time, and the client acts as the person who approved it, with their current permissions.
Setting it up
- 1Add the server's address under Integrations, and choose how Nerve signs in: nothing, an access token, an API key, custom headers or OAuth.
- 2Nerve connects over secure streamable HTTP, checks where the address really points, and lists the server's tools.
- 3Review the tools you want and their risk, then grant them to specific Agents.
Deploy your first Nerve Agent
Start with one conversation your team handles every day. Give the Agent what it needs to know, connect the tools it should use, and decide where a person steps in.