PocketBase MCP Server

This is an MCP server that interacts with a PocketBase instance. It allows you to fetch, list, create, update, and manage records and files in your PocketBase collections.

To install PocketBase MCP Server for Claude Desktop automatically viaSmithery:

npx -y @smithery/cli install @mabeldata/pocketbase-mcp --client claude

git clone <repository_url> cd pocketbase-mcp

- POCKETBASE_API_URL: The URL of your PocketBase instance (e.g.,http://127.0.0.1:8090). Defaults tohttp://127.0.0.1:8090if not set.
- POCKETBASE_ADMIN_TOKEN: An admin authentication token for your PocketBase instance.This is required.You can generate this from your PocketBase admin UI, seeAPI KEYS.

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." }, "id": { "type": "string", "description": "The ID of the record to fetch." } }, "required": [ "collection", "id" ] }

list_records: List records from a PocketBase collection. Supports pagination, filtering, sorting, and expanding relations.

- Input Schema:

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." }, "page": { "type": "number", "description": "Page number (defaults to 1).", "minimum": 1 }, "perPage": { "type": "number", "description": "Items per page (defaults to 25).", "minimum": 1, "maximum": 100 }, "filter": { "type": "string", "description": "Filter string for the PocketBase query." }, "sort": { "type": "string", "description": "Sort string for the PocketBase query (e.g., \\"fieldName,-otherFieldName\\")." }, "expand": { "type": "string", "description": "Expand string for the PocketBase query (e.g., \\"relation1,relation2.subRelation\\")." } }, "required": [ "collection" ] }

create_record: Create a new record in a PocketBase collection.

- Input Schema:

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." }, "data": { "type": "object", "description": "The data for the new record.", "additionalProperties": true } }, "required": [ "collection", "data" ] }

update_record: Update an existing record in a PocketBase collection.

- Input Schema:

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." }, "id": { "type": "string", "description": "The ID of the record to update." }, "data": { "type": "object", "description": "The data to update.", "additionalProperties": true } }, "required": [ "collection", "id", "data" ] }

get_collection_schema: Get the schema of a PocketBase collection.

- Input Schema:

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." } }, "required": [ "collection" ] }

upload_file: Upload a file to a specific field in a PocketBase collection record.

- Input Schema:

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." }, "recordId": { "type": "string", "description": "The ID of the record to upload the file to." }, "fileField": { "type": "string", "description": "The name of the file field in the PocketBase collection." }, "fileContent": { "type": "string", "description": "The content of the file to upload." }, "fileName": { "type": "string", "description": "The name of the file." } }, "required": [ "collection", "recordId", "fileField", "fileContent", "fileName" ] }

list_collections: List all collections in the PocketBase instance.

- Input Schema:

{ "type": "object", "properties": {}, "additionalProperties": false }

download_file: Get the download URL for a file stored in a PocketBase collection record.

- Input Schema:

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." }, "recordId": { "type": "string", "description": "The ID of the record to download the file from." }, "fileField": { "type": "string", "description": "The name of the file field in the PocketBase collection." }, "downloadPath": { "type": "string", "description": "The path where the downloaded file should be saved (Note: This tool currently returns the URL, download must be handled separately)." } }, "required": [ "collection", "recordId", "fileField", "downloadPath" ] }

-

list_collections: List all collections in the PocketBase instance.

- Input Schema:

{ "type": "object", "properties": {}, "additionalProperties": false }

get_collection_schema: Get the schema of a PocketBase collection.

- Input Schema:

{ "type": "object", "properties": { "collection": { "type": "string", "description": "The name of the PocketBase collection." } }, "required": [ "collection" ] }

Note:The Logs API requires admin authentication and may not be available in all PocketBase instances or configurations. These tools interact with the PocketBase Logs API as documented athttps://pocketbase.io/docs/api-logs/.

{ "type": "object", "properties": { "page": { "type": "number", "description": "Page number (defaults to 1).", "minimum": 1 }, "perPage": { "type": "number", "description": "Items per page (defaults to 30, max 500).", "minimum": 1, "maximum": 500 }, "filter": { "type": "string", "description": "PocketBase filter string (e.g., \"method='GET'\")." } }, "required": [] }

get_log: Get a single API request log by ID.

- Input Schema:

{ "type": "object", "properties": { "id": { "type": "string", "description": "The ID of the log to fetch." } }, "required": [ "id" ] }

get_logs_stats: Get API request logs statistics with optional filtering.

- Input Schema:

{ "type": "object", "properties": { "filter": { "type": "string", "description": "PocketBase filter string (e.g., \"method='GET'\")." } }, "required": [] }

Note:The Cron Jobs API requires admin authentication and may not be available in all PocketBase instances or configurations. These tools interact with the PocketBase Cron Jobs API.

-

list_cron_jobs: Returns list with all registered app level cron jobs.

- Input Schema:

{ "type": "object", "properties": { "fields": { "type": "string", "description": "Comma separated string of the fields to return in the JSON response (by default returns all fields). Ex.:?fields=,expand.relField.name" } } }

- Input Schema:

{ "type": "object", "properties": { "jobId": { "type": "string", "description": "The identifier of the cron job to run." } }, "required": [ "jobId" ] }

- Input Schema:

{ "type": "object", "properties": { "customPath": { "type": "string", "description": "Custom path for migrations. If not provided, defaults to 'pb_migrations' in the current working directory." } } }

- Input Schema:

{ "type": "object", "properties": { "description": { "type": "string", "description": "A brief description for the migration filename (e.g., 'add_user_email_index')." } }, "required": ["description"] }

- Input Schema:

{ "type": "object", "properties": { "description": { "type": "string", "description": "Optional description override for the filename." }, "collectionDefinition": { "type": "object", "description": "The full schema definition for the new collection (including name, id, fields, rules, etc.).", "additionalProperties": true } }, "required": ["collectionDefinition"] }

- Input Schema:

{ "type": "object", "properties": { "collectionNameOrId": { "type": "string", "description": "The name or ID of the collection to update." }, "fieldDefinition": { "type": "object", "description": "The schema definition for the new field.", "additionalProperties": true }, "description": { "type": "string", "description": "Optional description override for the filename." } }, "required": ["collectionNameOrId", "fieldDefinition"] }

- Input Schema:

{ "type": "object", "properties": {}, "additionalProperties": false }

- Input Schema:

{ "type": "object", "properties": { "migrationFile": { "type": "string", "description": "Name of the migration file to apply." } }, "required": ["migrationFile"] }

- Input Schema:

{ "type": "object", "properties": { "migrationFile": { "type": "string", "description": "Name of the migration file to revert." } }, "required": ["migrationFile"] }

- Input Schema:

{ "type": "object", "properties": { "appliedMigrations": { "type": "array", "items": { "type": "string" }, "description": "Array of already applied migration filenames." } } }

- Input Schema*:

{ "type": "object", "properties": { "targetMigration": { "type": "string", "description": "Name of the migration to revert to (exclusive). Use empty string to revert all." }, "appliedMigrations": { "type": "array", "items": { "type": "string" }, "description": "Array of already applied migration filenames." } }, "required": ["targetMigration"] }

The PocketBase MCP Server includes a comprehensive migration system for managing database schema changes. This system allows you to:
- Create migration files with timestamped names
- Generate migrations for common operations (creating collections, adding fields)
- Apply and revert migrations individually or in batches
- Track which migrations have been applied

Migration files are JavaScript files with a timestamp prefix and descriptive name:

// 1744005374_update_transactions_add_debt_link.js /// <reference path="../pb_data/types.d.ts" /> migrate((app) => { // Up migration code here return app.save(); }, (app) => { // Down migration code here return app.save(); });

Each migration has an "up" function for applying changes and a "down" function for reverting them.

await setMigrationsDirectory("./my_migrations");

await createNewMigration("add_user_email_index");

await createCollectionMigration({ id: "users", name: "users", fields: [ { name: "email", type: "email", required: true } ] });

await createAddFieldMigration("users", { name: "address", type: "text" });

// Apply a specific migration await applyMigration("1744005374_update_transactions_add_debt_link.js", pocketbaseInstance); // Apply all pending migrations await applyAllMigrations(pocketbaseInstance);

// Revert a specific migration await revertMigration("1744005374_update_transactions_add_debt_link.js", pocketbaseInstance); // Revert to a specific point (exclusive) await revertToMigration("1743958155_update_transactions_add_relation_to_itself.js", pocketbaseInstance); // Revert all migrations await revertToMigration("", pocketbaseInstance);

To use this server with Cline, you need to add it to your MCP settings file (cline_mcp_settings.json).

- Typically found at~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonon Linux/macOS.
- Or~/Library/Application Support/Claude/claude_desktop_config.jsonif using the Claude desktop app on macOS.

Edit the file and add the following configuration under themcpServerskey.Replace/path/to/pocketbase-mcpwith the actual absolute path to this project directory on your system. Also, replace<YOUR_POCKETBASE_API_URL>and<YOUR_POCKETBASE_ADMIN_TOKEN>with your actual PocketBase URL and admin token.

{ "mcpServers": { // ... other servers might be listed here ... "pocketbase-mcp": { "command": "node", "args": ["/path/to/pocketbase-mcp/build/index.js"], "env": { "POCKETBASE_API_URL": "<YOUR_POCKETBASE_API_URL>", // e.g., "http://127.0.0.1:8090" "POCKETBASE_ADMIN_TOKEN": "<YOUR_POCKETBASE_ADMIN_TOKEN>" }, "disabled": false, // Ensure it's enabled "autoApprove": [ "fetch_record", "list_collections", "get_collection_schema", "list_logs", "get_log", "get_logs_stats", "list_cron_jobs", "run_cron_job" ] // Suggested auto-approve settings } // ... other servers might be listed here ... } }

Save the settings file.Cline should automatically detect the changes and connect to the server. You can then use the tools listed above.

- @modelcontextprotocol/sdk
- pocketbase
- typescript
- ts-node(dev dependency)
- @types/node(dev dependency)

Read and write access to your Baserow tables.

An MCP server for Directus CMS, enabling AI clients to interact with the Directus API.

Manage multiple Fireproof JSON document databases with cloud sync capabilities.

Query local CSV, Parquet, JSON and TSV files with real SQL via DuckDB. Gives your AI coding tool ground-truth data access instead of hallucinated answers.