PocketBase Cloud

com.pocketbasecloudPublished by pocketbasecloud.comOfficial publisherv1.4.3Updated Oct 24, 2026

Manage PocketBase Cloud projects, instances, deploys, domains, collections and records.

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Official PocketBase Cloud MCP server that lets an assistant manage hosted projects, instances, deploys, domains, collections and records.

What you can do
  • Inspect the account, plan, projects and regions, and create projects
  • List, inspect and create PocketBase instances, frontends and backends, and adjust runtime settings and backups
  • Read deploys and build or runtime logs, diagnose failures, manage hooks and static sites, and get the deploy command
  • Add, verify, check and remove custom domains
  • Work inside an instance: collections, API rules, records, request logs, backups, crons, security and performance checks, TypeScript types
  • Search the PocketBase and PocketBase Cloud documentation for agents
When to use it
Useful when you host PocketBase apps on PocketBase Cloud and want an assistant to inspect what is running, explain failed deploys, set up domains, or design and query collections and records without switching to the portal.
Requirements
A PocketBase Cloud account signed in through OAuth when connecting, and an MCP client that supports remote Streamable HTTP with OAuth. What you can create or deploy depends on your plan. Deploying source code also needs the PocketBase Cloud CLI on your machine. Scripts and CI can send a CLI access token as an Authorization Bearer header instead of signing in.
Before you install
The connection can read and write, so records, collections, domains and deploys can be changed; deleting or restoring needs explicit confirmation and bulk operations are opt-in. Choose read-only or single-project access at sign-in if you want limits. A CLI access token sent as an Authorization Bearer header is forwarded as is, so keep it out of shared configs. Records and logs from your instances are passed to the assistant.

Installation

In SourceWeft

  1. Open PocketBase Cloud in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.pocketbasecloud%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pocketbase-cloud": {
      "type": "http",
      "url": "https://mcp.pocketbasecloud.com/mcp"
    }
  }
}

README

[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.

[Add to Cursor]
Add to Cursor
Build on PocketBase from your editor. 		[Add to VS Code]
Add to VS Code
Use it from GitHub Copilot. 		[Add to Claude]
Add to Claude
Add it as a custom connector. 		[Add to ChatGPT]
Add to ChatGPT
Add it as a custom MCP server.

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

ClientCommand or configuration
Claude Codeclaude 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
ClineMCP 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
Codexcodex mcp add pocketbasecloud --url https://mcp.pocketbasecloud.com/mcp, then codex mcp login pocketbasecloud
CursorThe 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 CopilotThe 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 CLIgemini extensions install https://github.com/pocketbasecloud/mcp, then /mcp auth pocketbasecloud
Any other MCP clientThe 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.

Contents

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:

FormatManifest and configurationShared components
Agent Plugins v1plugin.json and mcp.jsonskills/
Claude plugin (Claude Code, claude.ai, Claude Desktop).claude-plugin/plugin.json and .claude-plugin/marketplace.json.mcp.json and skills/
Cursor plugin.cursor-plugin/plugin.json.mcp.json and skills/
Gemini CLI extensiongemini-extension.jsonMCP server configuration embedded in the manifest, and skills/, which Gemini CLI loads from the extension
MCP Registryserver.jsonRemote server metadata

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.

GroupDefaultWhat 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.
envopt-inEnvironment variables of a resource (build-time for frontends); values are never read back.
database_adminopt-inBulk 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.

OptionDefaultEffect
read_onlyfalseOnly tools that read.
project_refnoneLimit every tool to one project.
featuresaccount,resources,deploy,domains,database,docsThe 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.

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:

sh
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:

SkillUse it for
getting-startedA first project and PocketBase instance.
debug-deployWhy a deploy failed, and the command to deploy again.
review-securityAPI rules that are too open, fixed with your approval.
setup-user-accountsUsers, per-user collections and safe rules.
design-collectionsAn app's collections, relations, indexes and rules.
change-schemaChanging fields that already hold data, without losing records.
investigate-errorsWhy the app gets errors or empty lists, and the fix.
launch-checklistA read-only, scored check before going live.
write-hooksServer code in pb_hooks, read first and deployed with approval.
ship-appA site online from pb_public or a frontend, sent whole.
import-dataRows from CSV or JSON, checked and imported with approval.

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

ProblemWhat to do
"There was a problem connecting"Check the URL ends in /mcp: https://mcp.pocketbasecloud.com/mcp.
The tools don't appearFinish the PocketBase Cloud sign-in, and enable the connector for the chat. If needed, remove and add it again.
Only reading tools appearThe connection is read-only, from the sign-in choice or read_only=true. Reconnect and choose read and write.
Only one project is visibleThe connection is limited to one project. Reconnect and choose all projects, or drop project_ref.
Database tools are missingThey come with the database group, which is on by default; check that features in the URL still includes it.
Asked to sign in againA connection unused for 30 days ends; sign in again.
Cursor sign-in fails with "Invalid redirect URI"Update Cursor. Current versions sign in through http://localhost; older ones used a cursor:// callback, which the server doesn't accept.
Claude asks how it identifies itselfChoose Register automatically.

Security

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

Support and feedback

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.

Source: README.md at commit c1d0827

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

5
  1. v1.4.3LatestOct 18, 2026
  2. v1.4.2Oct 18, 2026
  3. v1.4.0Oct 17, 2026
  4. v1.3.0Oct 17, 2026
  5. v1.1.0Oct 15, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts