PocketBase MCP Server
@mrwyndham
MCP server for building PocketBase apps really quickly - Need a front end quick consider FastPocket
概要
What is PocketBase MCP Server?
An MCP server that provides tools for interacting with PocketBase databases, enabling advanced database operations, schema management, and data manipulation through the Model Context Protocol. It is designed for developers using AI assistants (like Cursor or Claude) to manage a PocketBase instance.
How to use PocketBase MCP Server?
Set up the server by configuring your MCP settings file (cline_mcp_settings.json or .vscode/mcp.json) with a command (e.g., node or docker), args pointing to build/index.js, and environment variables POCKETBASE_URL (required), POCKETBASE_ADMIN_EMAIL, and POCKETBASE_ADMIN_PASSWORD (optional). Optionally use Docker with docker run or Docker Compose. Tools can be auto‑approved via autoApprove (e.g., create_record, list_collections).
Key features of PocketBase MCP Server
- Collection creation and schema management
- CRUD operations for records
- User authentication and account creation
- Database backup with format options
- Pagination and cursor‑based navigation
- Relationship expansion support
Use cases of PocketBase MCP Server
- Creating and managing PocketBase collections via natural language commands
- Performing record CRUD operations with filters and pagination
- Authenticating users and managing user accounts
- Creating database backups for administration
FAQ from PocketBase MCP Server
How does this compare to alternatives like DynamicsEndpoints?
This server is built from the official JS‑SDK type definitions and has been tested on PocketBase 26.1, whereas the Dynamics one uses incorrect definitions and many of its methods do not work.
What are the runtime requirements?
The server runs on Node.js (using the compiled build/index.js) or inside a Docker container. It communicates with the MCP host over stdio.
Where does the data live?
The server does not store data; all data resides in the external PocketBase instance specified by the POCKETBASE_URL environment variable.
What known limits exist?
This is a work‑in‑progress (the README says “very much in progress”). Local setup is the only supported deployment method for now.
