Connecting an AI assistant (MCP)
PocketBase Cloud runs an MCP server, so an AI assistant can manage your projects, PocketBase instances, deploys, domains and data for you. You sign in once and choose read-only or read and write access.
The server URL is:
https://mcp.pocketbasecloud.com/mcp
Paste it exactly: the address ends in /mcp. Setup happens in your
assistant.
Connect your assistant
Claude (claude.ai and Claude Desktop)
- Open Settings → Connectors → Add custom connector
- Name it PocketBase Cloud and paste the server URL
- Click Connect, sign in, then choose the access and the project
ChatGPT
- Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode
- Create a connector with the server URL and OAuth authentication
- Sign in when ChatGPT asks
Claude Code
claude mcp add --transport http pocketbasecloud https://mcp.pocketbasecloud.com/mcp
Sign in when Claude Code opens the browser.
Cursor and VS Code
Use the Add to Cursor or Add to VS Code button on the
MCP server page, then sign in when the editor asks. To add it by hand,
create an HTTP MCP server named pocketbasecloud with the server URL.
Narrow what it can touch
Add options to the server URL. They can narrow what you approved when signing in, never widen it.
| Option | What it does |
|---|---|
?read_only=true |
Exposes only the tools that read |
?project_ref=<project id> |
Limits every tool to one project |
?features=<keys> |
Chooses which tool groups the assistant sees, by the comma-separated keys in Tools |
Combine them with &, for example a read-only connection to one project:
https://mcp.pocketbasecloud.com/mcp?read_only=true&project_ref=<project id>
Tools
| Group | Key | Tools |
|---|---|---|
| Account & projects | account |
list_projects, get_project, create_project, get_plan, list_regions, get_overview |
| Resources | resources |
list_resources, get_resource, create_pocketbase, update_pocketbase_config, set_continuous_backup |
| Deploys & logs | deploy |
get_logs, list_deployments, get_deployment, get_deploy_command, list_hooks, deploy_hooks, deploy_public, diagnose_resource |
| Custom domains | domains |
add_domain, verify_domain, check_domain, remove_domain |
| Database (inside an instance) | database |
list_collections, get_collection, list_records, get_request_logs, list_backups, list_crons, count_records, get_record, check_security, generate_types, preview_collections, check_performance, apply_collections, update_api_rules, create_record, create_records, update_record, create_backup, run_cron, delete_record |
| Docs | docs |
search_docs |
| Environment variables (opt-in) | env |
list_env_vars, set_env_vars, delete_env_vars |
| Database admin (opt-in) | database_admin |
truncate_collection, delete_collection, remove_fields, restore_backup, delete_backup |
The two opt-in groups are off until you add their key to features. Database
admin tools take a backup first.
Safety and your data
- Tools that delete or restore ask for your approval first.
- Database tools reach your instance through PocketBase Cloud. System collections and instance settings are never touched.
- Signing in stores an encrypted OAuth grant on Cloudflare, holding your PocketBase Cloud session so the assistant can act for you. Disconnect the app in your assistant to end it.
- The server never stores records, files or logs from your instances. It passes them to your assistant and forgets them.
- For reliability it counts tool calls by tool name, outcome and duration, without your identity or what you asked.