PocketBase Cloud hosts PocketBase backends, frontends and server apps. Connect your account once, then ask your
assistant in plain words; it picks and runs the right actions.
With the PocketBase Cloud MCP Server, your assistant can:
See what is running: projects, PocketBase instances, frontends and backends with their status, recent
deploys, and the logs of instances and backends.
Find out why something broke: read a failed deploy's build log and explain the fix.
Manage PocketBase Cloud projects, instances, deploys, domains, collections and records.
2026-11-08
ดาว
—
เครื่องมือ
—
อัปไทม์
—
Start an app: create projects and PocketBase instances in the region you choose.
Ship: add and verify custom domains, deploy hooks and static sites, and get the exact pbc command to deploy
your source code.
Work with data: design collections and API rules, and read, create, update and delete records.
Harden an instance: review API rules for security gaps, find slow requests, and back up before risky
changes.
[!IMPORTANT]
You choose the access when you connect: read and write or read only, and all projects or a single one.
Options in the server URL can narrow a connection, never widen it. Deleting needs your explicit
approval of that exact change.
One-click setup
Pick your AI client below. Each button uses your client's native install link, so you don't need to edit any JSON
config by hand.
The server URL, for any other client:
https://mcp.pocketbasecloud.com/mcp
Paste it exactly: the address ends in /mcp.
Let your agent do the setup
Most AI coding agents can add the server and start sign-in themselves. Paste this into your agent:
Add the PocketBase Cloud MCP server https://mcp.pocketbasecloud.com/mcp to this agent
(remote, Streamable HTTP, OAuth), following https://mcp.pocketbasecloud.com/.
Then start the authentication flow so I can sign in to PocketBase Cloud.
Claude and ChatGPT
Claude (claude.ai and Claude Desktop), with the plugin. On a paid plan, the plugin brings the skills too:
Customize → Plugins, then Add → Add marketplace, and enter pocketbasecloud/mcp.
Install PocketBase Cloud.
Open the plugin's Connectors tab and connect pocketbasecloud: sign in to PocketBase Cloud, then choose the
access and the project. Installing alone does not connect it.
A plugin added there is saved to your Claude account, so Claude Code has it too when you sign in with the same
account.
Claude (claude.ai and Claude Desktop), server only
Customize → Connectors, then + Add → Add custom connector.
Name it (for example PocketBase Cloud), paste the server URL, and continue. If asked how Claude identifies
itself, choose Register automatically. Click Add.
Click Connect, sign in to PocketBase Cloud, then choose the access and the project.
On a Team or Enterprise plan, an owner adds it once under Organization settings → Connectors → Add → Custom →
Web; then each member clicks Connect.
ChatGPT
Plugins → + → Add custom MCP server.
Name it, enter the server URL under Connection with OAuth authentication, accept the warning about
custom servers, then Create as a plugin.
Install the plugin, sign in to PocketBase Cloud when ChatGPT asks, then type @ in a chat to use it.
Other clients
Client
Command or configuration
Claude Code
claude mcp add --transport http pocketbasecloud https://mcp.pocketbasecloud.com/mcp, then run /mcp in a session to sign in
Claude Code (plugin, with skills)
/plugin marketplace add pocketbasecloud/mcp, then /plugin install pocketbase-cloud@pocketbase-cloud
Cline
MCP Servers → Remote Servers → Edit Configuration, and add "pocketbasecloud": { "type": "streamableHttp", "url": "https://mcp.pocketbasecloud.com/mcp" } under mcpServers. Sign in when Cline opens the browser. See llms-install.md
The Add to Cursor button above, or "pocketbasecloud": { "url": "https://mcp.pocketbasecloud.com/mcp" } under mcpServers in .cursor/mcp.json
Cursor (plugin, with skills)
PocketBase Cloud in the Cursor Marketplace once it is listed. Until then, copy this repository (a copy, not a symlink) into ~/.cursor/plugins/local/pocketbase-cloud and reload Cursor. Keep only one PocketBase Cloud server: remove the one in .cursor/mcp.json if you added it
VS Code / GitHub Copilot
The Add to VS Code button above, or "pocketbasecloud": { "type": "http", "url": "https://mcp.pocketbasecloud.com/mcp" } under servers in .vscode/mcp.json
Devin Desktop (formerly Windsurf)
In the Cascade panel, … → Open MCP config file, and add "pocketbasecloud": { "url": "https://mcp.pocketbasecloud.com/mcp" } under mcpServers. For the Devin agent: devin mcp add pocketbasecloud https://mcp.pocketbasecloud.com/mcp, then devin mcp login pocketbasecloud
Gemini CLI
gemini extensions install https://github.com/pocketbasecloud/mcp, then /mcp auth pocketbasecloud
Any other MCP client
The server URL, with the Streamable HTTP transport and OAuth
Scripts and CI: instead of signing in, send a PocketBase Cloud CLI access token (portal → Account → CLI access
token) as Authorization: Bearer <token>. See How it works.
This repository publishes the same MCP server and skills in several package formats, so each client can use its
native discovery and installation flow:
Both mcp.json and .mcp.json are intentional: Agent Plugins requires the root mcp.json and its portable
transport vocabulary (streamable-http), while Claude and Cursor read .mcp.json with theirs (http). Gemini
CLI names the Streamable HTTP endpoint httpUrl. Keep the endpoint the same in all of them; npm run validate
checks it.
Tools
The server groups its tools. Groups marked opt-in are added with the features option. The live
list, with every tool, is on the connect page.
Group
Default
What it covers
account
✅
Overview of the account, plan and Free trial, projects, regions; create a project.
resources
✅
PocketBase instances, frontends and backends: list, inspect, create an instance, runtime settings, continuous backup.
deploy
✅
Deploys and their build logs, runtime logs, a one-call diagnosis, hooks, static sites, and the pbc command to deploy source code.
domains
✅
Add, verify, check and remove custom domains.
docs
✅
Search the PocketBase and PocketBase Cloud guide for agents.
database
✅
Inside an instance: collections, API rules, records, request logs, backups, crons, security and performance checks, TypeScript types.
env
opt-in
Environment variables of a resource (build-time for frontends); values are never read back.
database_admin
opt-in
Bulk deletes and restores: truncate or delete a collection, remove fields, restore or delete a backup.
Not available on purpose: deleting projects or resources (use the portal or pbc), and building source code on
the server (it runs on your machine; the server gives you the pbc command).
Options
Add these to the server URL's query string. They can narrow what you approved when signing in, never widen it.
Option
Default
Effect
read_only
false
Only tools that read.
project_ref
none
Limit every tool to one project.
features
account,resources,deploy,domains,database,docs
The tool groups. Add env for environment variables, database_admin for bulk deletes and restores.
For example: https://mcp.pocketbasecloud.com/mcp?read_only=true&project_ref=<project id>.
Before you start
Prerequisites
A PocketBase Cloud account. You sign in on the PocketBase Cloud portal when you connect.
What you can create and deploy depends on your plan; new accounts start with a Free trial.
Deploying source code also needs the PocketBase Cloud CLI, pbc, on your machine; the server tells you the
exact command to run.
An MCP client that supports remote servers (Streamable HTTP) and OAuth. For Claude, adding a custom connector
needs a plan that allows it.
Data and security
Your PocketBase Cloud session stays on the server. Signing in stores the connection you approved, with your
PocketBase Cloud session encrypted inside it. Your assistant gets its own token, valid for an hour and refreshed
automatically; it never sees your PocketBase Cloud credentials.
Connections end when unused. Remove the app in your assistant to disconnect; a connection is deleted after
30 days without use.
No copies of your data. The server never stores records, files or logs from your instances; it passes them
to your assistant and forgets them.
Minimal telemetry. For reliability it records each tool call (the tool, its target, the outcome, a shortened
error and the duration) with a pseudonymous ID, and deletes those records after 90 days. It never records what
you asked.
Guardrails on changes. Tools that delete or restore need explicit confirmation (confirm: true); deleting a
collection also needs its name typed again; bulk deletes and restores back the instance up first and return the
backup's name. Restoring it brings records back, but not a deleted collection or field: instances replay that
change when they restart, so restore the backup into a new instance instead. Changing the type of an existing field
is refused.
Instance credentials are never held. Database tools reach an instance through PocketBase Cloud, and only the
calls those tools make are allowed: no instance settings, no backup downloads, no writes to system collections
such as _superusers.
Untrusted content is fenced. Records and logs come back inside <untrusted-data-…> tags, so the model treats
them as data, not instructions.
Your AI client ──Streamable HTTP──▶ mcp.pocketbasecloud.com/mcp ──▶ PocketBase Cloud API
└─▶ your PocketBase instances (through PocketBase Cloud)
Sign-in (OAuth 2.1)
The server supports OAuth 2.1 with dynamic client registration. When your client connects, it opens the PocketBase
Cloud portal, where you sign in as usual and choose the access (read and write, or read only) and the projects
(all, or one). Each token refresh renews the connection, so it stays valid while you use it.
CLI token (scripts and CI)
For automation, send a PocketBase Cloud CLI access token directly:
PocketBase Cloud is independent of the PocketBase open source project. The server is a
hosted service at mcp.pocketbasecloud.com; this repository holds its documentation, client manifests, MCP
Registry entry and skills, not the server's code. Tool names and behavior may change as the service evolves; the
live list is on the connect page.