Fully Capable Pocketbase Mcp Server

@brynnjocelyn

About Fully Capable Pocketbase Mcp Server

# PocketBase MCP Server

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "pocketbase": {
      "command": "node",
      "args": [
        "/path/to/pocketbase-mcp-server/dist/mcp-server.js"
      ],
      "env": {
        "POCKETBASE_URL": "http://localhost:8090"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Fully Capable Pocketbase Mcp Server?

It is a comprehensive Model Context Protocol (MCP) server that exposes PocketBase database management as tools for any MCP‑compatible client (e.g., Claude Desktop, Cursor). It enables LLMs to perform collection, record, authentication, file, system, backup, and hook operations on PocketBase instances.

How to use Fully Capable Pocketbase Mcp Server?

Install via npm install and build with npm run build. Configure the PocketBase URL through a local .pocketbase-mcp.json file, the POCKETBASE_URL environment variable, or use the default http://127.0.0.1:8090. Add the server to your MCP client’s settings (e.g., Claude Desktop’s mcpServers block) pointing to the built dist/mcp-server.js script.

Key features of Fully Capable Pocketbase Mcp Server

60+ tools covering all major PocketBase operations.
CRUD on collections and records with filtering, sorting, pagination.
Batch create, update, delete, and upsert operations.
Authentication via password, OAuth2, OTP, and token refresh.
File URL generation with thumbnail and private token support.
Backup creation, listing, download, deletion, and restoration.
JavaScript hook management with pre‑built templates.

Use cases of Fully Capable Pocketbase Mcp Server

Manage PocketBase collections and their schemas from an AI assistant.
Automate bulk record imports or updates using batch tools.
Implement user authentication flows (password, OAuth2, OTP) via LLM.
Create, download, and restore database backups for maintenance.
Generate and manage custom JavaScript hooks with templates.

FAQ from Fully Capable Pocketbase Mcp Server

What PocketBase version is required?

PocketBase v0.20.0 or higher, and the PocketBase JavaScript SDK v0.21.0+.

How can I connect to multiple PocketBase instances?

You can configure project‑specific MCP settings, multiple named servers in the MCP config, or use a local .pocketbase-mcp.json file per project.

Which authentication methods are supported?

Email/password, OAuth2 (e.g., Google), OTP via email, plus token refresh, password reset, email verification, and email change.

How does the server handle errors?

Every tool returns descriptive error messages for invalid auth, missing fields, network issues, and permission errors.

Are admin operations secured?

Yes, admin‑level tools (settings, collections, backups) require appropriate authentication, and the server inherits PocketBase’s security model and access rules.

Frequently asked questions