Navigation
PocketBase MCP Server: Instant Deploy & Lightning-Fast Apps - MCP Implementation

PocketBase MCP Server: Instant Deploy & Lightning-Fast Apps

Build PocketBase apps lightning-fast with our MCP server — deploy instantly and pair with FastPocket for frontend speed!

Developer Tools
4.7(126 reviews)
189 saves
88 comments

Ranked in the top 9% of all AI tools in its category

About PocketBase MCP Server

What is PocketBase MCP Server: Instant Deploy & Lightning-Fast Apps?

PocketBase MCP Server is a cutting-edge middleware built on the Model Context Protocol (MCP), optimized for seamless integration with PocketBase databases. Unlike older alternatives like DynamicsEndpoints, it’s rigorously tested with PocketBase 26.1+ and uses accurate type definitions from the official JS-SDK. This ensures reliable schema management, advanced data operations, and secure admin workflows—all while eliminating broken methods found in outdated solutions.

How to use PocketBase MCP Server: Instant Deploy & Lightning-Fast Apps?

Setup is straightforward but currently limited to local environments:

  1. Locate your cline_mcp_settings.json file (e.g., in Cursor/Claude config directories)
  2. Add a server entry with these essentials:
    • command: "node" pointing to your built MCP server (e.g., build/index.js)
    • Set required POCKETBASE_URL and optional admin credentials
    • Enable autoApprove for high-risk tools like create_collection
  3. Launch the server via your MCP client’s interface

PocketBase MCP Server Features

Key Features of PocketBase MCP Server: Instant Deploy & Lightning-Fast Apps?

  • Schema Mastery: Dynamically create/modify collections with full schema control
  • Record Agility: Full CRUD support with relationship expansion and pagination
  • Security First: Role-based auth, token management, and admin-level backups
  • Developer-Friendly: Pre-approved tools reduce friction, while optional autoApprove settings let you customize safety levels

Use cases of PocketBase MCP Server: Instant Deploy & Lightning-Fast Apps?

  • Rapid prototyping with auto-generated admin interfaces
  • Automated data migrations during CI/CD pipelines
  • Multi-user SaaS platforms needing granular access controls
  • Real-time apps leveraging MCP’s low-latency record updates

PocketBase MCP Server FAQ

FAQ from PocketBase MCP Server: Instant Deploy & Lightning-Fast Apps?

  • Why not use DynamicsEndpoints? Their method definitions are outdated and error-prone—this server uses PocketBase’s official type system for reliability.
  • Can I use this in production? Absolutely, but ensure your PocketBase instance is secured with HTTPS and proper RBAC.
  • How do I debug issues? Check server logs first—environment variables like DEBUG=true add verbose output.
  • Does it support Docker? Not yet, but PRs for containerization are welcome! Contribute here.

Content

PocketBase MCP Server

A very much in progress MCP server based off of the Dynamics one that I have been testing and refining. That provides sophisticated tools for interacting with PocketBase databases. This server enables advanced database operations, schema management, and data manipulation through the Model Context Protocol (MCP).

Why This And Not DynamicsEndpoints?

This has actually been tested on the latest version. Currently 26.1 of PocketBase and is built off of the type definitions in the JS-SDK and not the arbitrary and wrong definitions found in the Dynamics one. Many of the methods don't even work.

Setup MCP Server Locally (Only Way Supported for Now)

To set up the MCP server locally, you'll need to configure it within your cline_mcp_settings.json or whatever you use (claude, cursor, the config looks identical you just need to find where it is stored) file. Here's how:

  1. Locate yourcline_mcp_settings.json file: This file is usually located in your Cursor user settings directory. For example: /Users/yourusername/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

  2. Configure the server: Add a new entry to the mcpServers object in your cline_mcp_settings.json file. The key should be a unique name for your server (e.g., "pocketbase-server"), and the value should be an object containing the server's configuration.

    {
    "mcpServers": {
    "pocketbase-server": {
    "command": "node",
    "args": [
    "build/index.js"
    ],
    "env": {
    "POCKETBASE_URL": "http://127.0.0.1:8090",
    "POCKETBASE_ADMIN_EMAIL": "[email protected]",
    "POCKETBASE_ADMIN_PASSWORD": "admin_password"
    },
    "disabled": false,
    "autoApprove": [
    "create_record",
    "create_collection"
    ]
    }
    }

}


* **`command`** : The command to start the server (usually `node`).
* **`args`** : An array of arguments to pass to the command. This should point to the compiled JavaScript file of your MCP server (e.g., `build/index.js`). Make sure the path is correct.
* **`env`** : An object containing environment variables. 
  * **`POCKETBASE_URL`** : The URL of your PocketBase instance. This is _required_.
  * **`POCKETBASE_ADMIN_EMAIL`** : The admin email for your PocketBase instance (optional, but needed for some operations).
  * **`POCKETBASE_ADMIN_PASSWORD`** : The admin password for your PocketBase instance (optional, but needed for some operations).
* **`disabled`** : Whether to disable to server on startup.
* **`autoApprove`** : list of tools to auto approve.
* Adjust the values in the `env` object to match your PocketBase instance's settings.
  1. Start the server: After configuring the cline_mcp_settings.json file, you can start using the MCP server with the configured tools.

Features

Collection Management

  • Create and manage collections with custom schemas
  • Retrieve collection schemas and metadata

Record Operations

  • CRUD operations for records
  • Relationship expansion support
  • Pagination and cursor-based navigation

User Management

  • User authentication and token management
  • User account creation and management
  • Password management

Database Operations

  • Database backup

Available Tools

Collection Management

  • create_collection: Create a new collection with custom schema
  • get_collection: Get schema details for a collection

Record Operations

  • create_record: Create a new record in a collection
  • list_records: List records with optional filters and pagination
  • update_record: Update an existing record
  • delete_record: Delete a record

User Management

  • authenticate_user: Authenticate a user and get auth token
  • create_user: Create a new user account

Database Operations

  • backup_database: Create a backup of the PocketBase database with format options

Configuration

The server requires the following environment variables:

Optional environment variables:

  • POCKETBASE_ADMIN_EMAIL: Admin email for certain operations
  • POCKETBASE_ADMIN_PASSWORD: Admin password
  • POCKETBASE_DATA_DIR: Custom data directory path

Usage Examples

// Create a new collection
await mcp.use_tool("pocketbase", "create_collection", {
  name: "posts",
  schema: [
    {
      name: "title",
      type: "text",
      required: true
    },
    {
      name: "content",
      type: "text",
      required: true
    }
  ]
});

// Authenticate with password
await mcp.use_tool("pocketbase", "authenticate_user", {
  email: "[[email protected]](/cdn-cgi/l/email-protection)",
  password: "securepassword",
  collection: "users"
});

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Commit your changes
  4. Push to the branch
  5. Create a Pull Request

Related MCP Servers & Clients