Connection details ride in headers instead of being baked into the server, so one endpoint serves whichever instance you point it at and switching projects is a variable change. Access is superuser-level — the credentials are the admin login, and should be handled as such.
A remote server that sits in front of a PocketBase instance you already run and speaks stateless HTTP to any MCP client. Use the hosted endpoint, or self-host the same server.
- Whichever PocketBase instance you name — the target lives in the X-PB-URL header, not in the server
- Superuser access by email and password, or by an auth token
- Stateless HTTP transport, declared as type http rather than sse
- A hosted endpoint at https://pocketbase.tokenscompany.co/mcp, or the same code on your own infrastructure
- A published SKILL.md you can drop into your project instructions so the agent knows the tool surface
A PocketBase instance the server can reach, and superuser credentials for it: X-PB-URL plus either X-PB-Email and X-PB-Password, or X-PB-Token. They travel as headers, so client configs can expand them from environment variables rather than storing them in the file.
One command plus a key — claude mcp add --transport http pocketbase https://pocketbase.tokenscompany.co/mcp \ --header "X-PB-URL: https://your-pocketbase.example.com" \ --header "X-PB-Email: admin@example.com" \ --header "X-PB-Password: your-password", then supply credentials