home / mcp / pocketbase mcp server

PocketBase MCP Server

MCP server for building PocketBase apps really quickly - Need a front end quick consider FastPocket

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "mrwyndham-pocketbase-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "POCKETBASE_URL=http://host.docker.internal:8090",
        "-e",
        "[email protected]",
        "-e",
        "POCKETBASE_ADMIN_PASSWORD=your_admin_password",
        "pocketbase-mcp"
      ],
      "env": {
        "POCKETBASE_URL": "http://host.docker.internal:8090",
        "POCKETBASE_ADMIN_EMAIL": "[email protected]",
        "POCKETBASE_ADMIN_PASSWORD": "your_admin_password"
      }
    }
  }
}

You can run a PocketBase MCP Server to interact with PocketBase databases through the Model Context Protocol. This server enables advanced database operations, schema management, and data manipulation via MCP, giving you programmatic control over collections, records, users, and backups.

How to use

Learn how to connect your MCP client to the PocketBase MCP Server and perform common tasks. Start the server locally or via Docker, then use the available tools to create collections, manage records, handle users, and back up your database. The setup supports both local development and containerized deployment, with environment variables to configure the PocketBase instance you work with.

How to install

Prerequisites you need before installing: Node.js installed on your machine, or Docker if you prefer containerized usage. You also need access to a PocketBase instance running locally or remotely.

Option 1: Local MCP server (Node.js) configuration and startup. Create or edit your MCP settings to include a pocketbase-server entry that starts the MCP server with Node and points to the built MCP server file.

Option 2: Dockerized MCP server. Build and run the Docker image, then configure your MCP settings to connect to the containerized server.

Additional sections

Configuration notes: set POCKETBASE_URL to your PocketBase instance URL. Optionally provide POCKETBASE_ADMIN_EMAIL and POCKETBASE_ADMIN_PASSWORD for administrative operations. You can also specify POCKETBASE_DATA_DIR to choose a custom data directory.

Security: store credentials securely and limit auto-approval to only the operations you truly need. Be mindful of exposing admin credentials in shared environments.

Examples include starting the server with a local Node.js setup, or running a Docker container that exposes POCKETBASE_URL and admin credentials to the MCP server.

Troubleshooting: ensure the MCP server path is correct, environment variables are set, and the specified PocketBase URL is reachable. Check container logs or console output for errors during startup.

Available tools

create_collection

Create a new collection with a custom schema and define the fields, types, and constraints.

get_collection

Retrieve the schema and metadata for a specific collection.

create_record

Create a new record in a specified collection with given field values.

list_records

List records in a collection with optional filters and pagination.

update_record

Update an existing record with new field values.

delete_record

Delete a record from a collection.

authenticate_user

Authenticate a user and obtain an authentication token.

create_user

Create a new user account in the PocketBase instance.

backup_database

Create a backup of the PocketBase database with optional format settings.