Quickstart
One URL, paste it into your client, done.
There is one URL for every client, every account, every screenshot: https://mcp.protobox.ai/mcp.
No workspace slug to look up first.
Add https://mcp.protobox.ai/mcp as an MCP server in Claude Desktop, Claude Code, Cursor, or any MCP client. The client opens a browser tab to authorize.
Have a workspace already? Sign in - if you're in more than one, pick which to connect. New here? Press Continue: a workspace is created for you on the spot, no email or phone required. Add an email later from inside the assistant to keep it past its 7-day trial window.
Back in your client, the Protobox tools now appear in its tools menu - ask it something that needs one. Every new workspace also ships with 25+ pre-loaded skills (playbooks your client can invoke as MCP prompts) - nothing to write before your assistant is useful. The CLI equivalent:
protobox mcp testThis runs a full protocol handshake: connect, list tools, list resources, list prompts.
Try it without an account
Not ready to sign in at all? Create a throwaway sandbox with one request:
curl -X POST https://mcp.protobox.ai/tryYou get back a URL, https://mcp.protobox.ai/try/<key>/mcp, that works immediately, no browser tab,
no email, no phone. It carries its own memory and knowledge tools, a 100-request daily quota, and no
outbound or integration tools - a scratch space to see the assistant work before you commit to
anything.
It behaves like a normal MCP endpoint from here: initialize, tools/list, and calls to
memory_store / kb_search work right away.
The sandbox expires 24 hours after creation. Nothing to clean up if you never come back to it.
Ask the assistant to call claim with an email. It emails a 6-digit code; call claim again
with that code and the same workspace, with everything you stored, becomes a real account. No
new workspace, nothing copied.
A sandbox is throttled tighter than a real account (5 new sandboxes per hour per network, 100 requests per day per sandbox) and can't reach outbound or third-party integration tools. Claim it to remove both limits.
Prefer the CLI, or need a specific workspace's endpoint?
The global URL always resolves to whichever workspace your token belongs to. For scripted setups, CI, or pointing at one workspace specifically, the per-workspace URL still works and never breaks:
Sign up at app.protobox.ai. Your workspace gets a slug - it becomes its own MCP endpoint: https://your-workspace.protobox.app/mcp.
In the dashboard, open Connect → MCP and create an API key. Keys are scoped to the workspace - a key from one workspace won't authenticate against another's endpoint.
Treat API keys like passwords: never commit them, and revoke any key that leaks (Manage → API Keys).
npm install -g @protoboxai/cli
protobox login --api-key YOUR_API_KEY
protobox mcp connect claude # or: cursor, vscode, windsurf, rawlogin verifies the key against the platform before storing it, so a typo fails here instead of in your client. Paste the JSON into your client's MCP config.