pb_healthLABSCO SUMMARY
Your PocketBase, reachable from any client without installing anything locally.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus credentials — 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
USE CASES
01
Getting an agent onto a PocketBase project
Point the connection at your instance URL and pass superuser credentials as headers — there is nothing to install on your machine.
02
Moving between a staging and a production instance
X-PB-URL decides which instance the same endpoint talks to, so the switch is one variable rather than a second server entry.
03
Using PocketBase from a client that only speaks HTTP
The transport is stateless HTTP and must be declared as type http; sse configurations will not connect.
04
Teaching the agent how to drive it
Save the repository's SKILL.md into your project's agent instructions so the tool surface is known before the first call.
19 tools
Listed in project docs. Your client may show a different list.
pb_list_collectionspb_get_collection_schemapb_create_collectionpb_update_collectionpb_delete_collectionpb_import_collectionspb_list_recordspb_get_recordpb_create_recordpb_update_recordpb_delete_recordpb_list_backupspb_create_backuppb_delete_backuppb_get_file_urlpb_get_settingspb_update_settingspb_list_logsBEFORE YOU INSTALL
What to know first
Tools you get
19 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
claude mcp add
TERMINAL
claude mcp add --transport http pocketbase https://pocketbase.tokenscompany.co/mcp \
--header "X-PB-URL: <YOUR_PB_URL>" \
--header "X-PB-Email: <YOUR_PB_EMAIL>" \
--header "X-PB-Password: <YOUR_PB_PASSWORD>"Hosted endpoint
ENDPOINT URL
https://pocketbase.tokenscompany.co/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"pocketbase": {
"type": "http",
"url": "https://pocketbase.tokenscompany.co/mcp",
"headers": {
"X-PB-URL": "${PB_URL}",
"X-PB-Email": "${PB_EMAIL}",
"X-PB-Password": "${PB_PASSWORD}"
}
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"pocketbase": {
"url": "https://pocketbase.tokenscompany.co/mcp",
"headers": {
"X-PB-URL": "<YOUR_PB_URL>",
"X-PB-Email": "<YOUR_PB_EMAIL>",
"X-PB-Password": "<YOUR_PB_PASSWORD>"
}
}
}
}OpenCode
OPENCODE · JSON
{
"mcp": {
"pocketbase": {
"type": "remote",
"url": "https://pocketbase.tokenscompany.co/mcp",
"headers": {
"X-PB-URL": "<YOUR_PB_URL>",
"X-PB-Email": "<YOUR_PB_EMAIL>",
"X-PB-Password": "<YOUR_PB_PASSWORD>"
},
"enabled": true
}
}
}
