pocketbase_mcp_server

This PocketBase MCP Server exposes PocketBase functionality as a suite of MCP tools that allow LLMs and other clients to manage PocketBase instances through a standardized interface. The server offers 60+ tools across collections, records, authentication, files, system operations, backups, and hooks, enabling you to list, create, update, and delete collections, perform advanced record queries with pagination and filtering, manage authentication methods, generate file access URLs, monitor health and settings, run cron jobs, manage backups, and interact with JavaScript hooks. To use it, deploy the MCP server with your PocketBase URL configured via POCKETBASE_URL or a project-specific configuration, then call the desired tool by name with the required arguments. Common usage patterns include listing records with filters, batch creating records, authenticating users via password or OTP, and managing backups or hooks through the provided tools.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your machine
• A running PocketBase instance you want to connect to

Install:

npm install

Build (if applicable for your setup):

npm run build

Configure the MCP server to point at your PocketBase instance. Example environment variable:

POCKETBASE_URL=http://localhost:8090

Run the MCP server (adjust the path to your built server file as needed):

node /path/to/pocketbase-mcp-server/dist/mcp-server.js

Optionally, for multi-project or multi-instance setups, create per-project configurations and reference them in Claude or your MCP client using the appropriate commands described in the README (e.g., claude mcp add-json pocketbase '{"command": "node", "args": ["/path/to/pocketbase-mcp-server/dist/mcp-server.js"], "env": {"POCKETBASE_URL": "http://localhost:8091"}}' --scope project).

Tips and common issues:

• Ensure POCKETBASE_URL is reachable from the MCP server host. Use the exact URL and port used by your PocketBase instance.
• If you switch PocketBase instances, update POCKETBASE_URL in your environment or per-project config to avoid cross-instance data access.
• When using multiple servers, keep distinct server names (e.g., pocketbase-local, pocketbase-prod) to avoid confusion in your MCP client configuration.
• Some operations may require admin authentication in PocketBase; configure your admin credentials or provide appropriate tokens when needed by your client workflow.
• Monitor health and logs via get_health and list_logs tools to troubleshoot connectivity or permission issues.
• If you upgrade PocketBase, verify compatibility with the MCP server version and update any necessary client tooling accordingly.