AGENSTAB now speaks the Model Context Protocol. Connect Claude Desktop, Claude Code, Cursor — any MCP-compatible host — to a sovereign browser session with one config block. Fifteen tools. Zero glue code.
| SDK (Code) | MCP (Config) | |
|---|---|---|
| Setup | Install SDK, write integration code | Paste one JSON block |
| Who drives | Your application logic | Your AI assistant, directly |
| Languages | Python, Node.js, Go | Any MCP-compatible host |
| First action | Write code | Ask your assistant to browse |
| Auth & limits | Engine-enforced | Engine-enforced — same key, same tiers |
Authenticate and copy your ak_live_ API key from the console
One JSON block in your MCP host's settings
Your assistant navigates, observes, clicks, and extracts — through the sovereign engine
{
"mcpServers": {
"agenstab": {
"command": "npx",
"args": ["-y", "@agens-tab/mcp"],
"env": {
"AGENSTAB_API_KEY": "ak_live_your_key_here"
}
}
}
}
Claude Code: claude mcp add agenstab -e AGENSTAB_API_KEY=ak_live_... -- npx -y @agens-tab/mcp
Each maps directly to the engine's browser control surface. Your assistant calls them by name.
The MCP server authenticates with your standard API key and is bound by the same tier limits, RBAC, and quotas the engine already enforces. It has no capability your key doesn't.
Your key lives only in the host's environment — never in logs, never in the protocol stream. Read-only mode is available for observation-only deployments.
Arbitrary code execution is opt-in twice — a server flag and an engine session setting. The sovereign engine's navigation guard, redaction, and audit logging remain the system of record.
Get an API key and connect in under five minutes.