agent-grid-mcp
v0.2.13
Published
AgentGrid — the governed MCP gateway for AI agents. Runs locally; approvals happen in the hosted AgentGrid console from anywhere.
Readme
agent-grid-mcp
The governed MCP gateway for AI agents. The MCP server, its signing keys, and
the browser all run on your machine. Consequential actions (a payment, a
deploy) pause for a human who approves them in the hosted AgentGrid console
from any device at https://app.agenttag.me.
Install
npm install -g agent-grid-mcpConfigure your IDE / AI agent
{
"mcpServers": {
"agentgrid": { "command": "agent-grid-mcp" }
}
}That's the whole install. Zero env vars, no hardcoded paths, zero per-launch re-download.
On first boot the server:
- connects outbound to
https://api.agenttag.me(the shared hosted relay), - creates
~/.agentgrid/state/and writes a fresh AES key tomaster.keywith mode0600— the key never leaves your machine, - provisions a default agent with fail-closed approval (a
pay()ordeploy()call returnsSTEP_UPuntil you approve it from the console).
Tools exposed to the agent
| Tool | Purpose |
| --- | --- |
| agentgrid_capabilities | List the agent's mandates, allowances, and recent audit entries. |
| agentgrid_browse | Drive a real Chromium browser (Playwright). Step-ups on novel domains / long sessions. |
| agentgrid_read_inbox | Read the agent's mailbox (verification codes, replies). |
| agentgrid_await_email_verification | Park until a verification email arrives. |
| agentgrid_pay | Issue a payment. Always steps up for a new counterparty. |
| agentgrid_deploy | Deploy a project. Step-ups on first-ever deploy. |
Every tool returns a governance verdict (ALLOW / ALLOW_WITH_NOTICE /
STEP_UP / DENY) alongside the result.
Pointing at a different relay (optional)
AGENTGRID_CLOUD_URL=https://my-relay.example.comState, master key, and approval channel stay on your machine — only the relay URL changes.
Real capability backends (optional)
The defaults are safe in-memory fakes (no real emails, no real cards, no real deploys). To wire real backends, set the corresponding env keys from the main AgentGrid docs:
AGENTMAIL_API_KEY— real inbox via AgentMailTWILIO_ACCOUNT_SID/TWILIO_AUTH_TOKEN/TWILIO_FROM_NUMBER— real SMSVERCEL_TOKEN— real deploys to your Vercel accountSTRIPE_*— real cards via Stripe Issuing
None of these are required for a working install.
Browser
Chromium is fetched on first npm install -g (Playwright postinstall). Skip
with AGENTGRID_SKIP_BROWSER_INSTALL=1, then run npx playwright install
chromium later.
Build (maintainers)
npm run build # esbuild-bundles packages/server + all @agent-grid/* into dist/
npm pack # produce the publishable tarball
npm publish # publish to npm (requires your npm account)