PocketBase Cloud

[PocketBase Cloud]

PocketBase Cloud MCP Server

The official Model Context Protocol (MCP) server for PocketBase Cloud: a hosted bridge that lets your AI assistant work in your PocketBase Cloud account — projects, PocketBase instances, frontends and backends, deploys and logs, custom domains, and the collections and records inside each instance.

[Model Context Protocol compatible] [MCP Registry: com.pocketbasecloud] [Auth: OAuth 2.1 or CLI token] [License: Apache 2.0]

Connect page · Tools · Data and security · PocketBase Cloud

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.
• 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:

1. Customize → Plugins, then Add → Add marketplace, and enter pocketbasecloud/mcp.
2. Install PocketBase Cloud.
3. 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

1. Customize → Connectors, then + Add → Add custom connector.
2. Name it (for example PocketBase Cloud), paste the server URL, and continue. If asked how Claude identifies itself, choose Register automatically. Click Add.
3. 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

1. Plugins → + → Add custom MCP server.
2. Name it, enter the server URL under Connection with OAuth authentication, accept the warning about custom servers, then Create as a plugin.
3. Install the plugin, sign in to PocketBase Cloud when ChatGPT asks, then type @ in a chat to use it.

Other clients

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.

Contents

• One-click setup
• Plugin packaging and compatibility
• Tools
• Options
• Before you start
• Data and security
• How it works
• Example prompts
• Skills
• Troubleshooting
• Security
• Support and feedback
• Disclaimer

Plugin packaging and compatibility

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.

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.

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.

See the privacy policy and terms.

How it works

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:

claude mcp add --transport http pocketbasecloud \  "https://mcp.pocketbasecloud.com/mcp?project_ref=<project id>&read_only=true" \  --header "Authorization: Bearer <token>"

This forwards your token to PocketBase Cloud as is (token passthrough); interactive clients should use OAuth.

Example prompts

• "What's running in my PocketBase Cloud account right now?"
• "Why did the last deploy of my frontend fail?"
• "Create a new PocketBase instance called shop-db in my Demo shop project."
• "Add the domain api.example.com to my backend and tell me which DNS record to create."
• "Give me the command to deploy this folder as a new backend."
• "Check the API rules of shop-db for security problems."
• "In shop-db, how many orders are paid, pending and refunded? Then show me the five newest."
• "Set up user accounts in shop-db so each user only sees their own orders."

Skills

skills/ holds workflows that every plugin in this repository installs:

With a plain MCP setup (no plugin), copy a skill's folder into your client's skills directory, or ask your assistant to read the SKILL.md.

Troubleshooting

Security

Found a security issue? Please don't open a public issue; see SECURITY.md.

Support and feedback

• Bugs and ideas: open an issue.
• Account, billing and platform questions: PocketBase Cloud.
• Contributing: see CONTRIBUTING.md.

Disclaimer

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.