connect your ai
nervurd carries an MCP host: it lets a model client act for you the same way you would yourself — reading what your seats can see, composing a mutation, and asking your plain-words yes before anything executes.
The model is the driver, not a person. It composes tool calls and reads what comes back, but every one of those calls acts under your own voice, on your own machine — the model holds no voice, no seat, and no key of its own. No new authority is created by adding this connector, and removing it removes the surface whole.
A being is an entity with a handler — a key that can be talked to. The host mints one identity for you, once, and projects whatever seats your beings hold on other Nervur grounds as tools the model can call. You sign; the model drives.
Works with any stdio MCP client — Claude Desktop, Claude Code, or your own.
npm install -g nervurdnervur mcpThe full set of subcommands, flags, and what each one binds lives in nervurd’s own README — read it before wiring the connector into a client, and before standing anything on the public internet.
A handful of tools, generic over any Quo implementation. A mutation is composed, never executed sight-unseen: the model puts a plain-words summary in front of you first, one way or another.
groundsopenreadactconfirmNo mutation ever executes without your explicit yes. A being’s own silence — no seat, no visible door, an unreachable endpoint — is surfaced as the refusal it is, never papered over or retried.
claude.ai and ChatGPT cannot spawn a local program on your machine, so a remote client calls a served address instead. Whoever runs a ground can stand its own MCP host at their own domain — the convention the whole tree keeps is that mcp.<your-domain> names an endpoint, never a brochure.
The face admits nobody by password, owner-auth, or challenge ceremony: a valid invitation is the whole admission story. Whoever arrives through one is minted a fresh voice on first contact, and every act that voice takes afterward is signed as itself — provably separate from anything you did yourself.
The transport details — binding, the OAuth envelope remote clients speak, honest scope and limits — are documented in nervurd’s own README, not repeated here.