The PocketBase MCP Server enables comprehensive interaction with a PocketBase instance for database management:
Record Management: Fetch, list, create, and update records in collections
File Management: Upload and download files associated with records
Collection Management: List collections and retrieve their schemas
Log Management: List, fetch, and analyze API request logs and statistics
Cron Job Management: List and trigger cron jobs
Migration Management: Create, apply, and revert database schema migrations, including creating collections and adding fields
Provides tools for interacting with a PocketBase instance, including record management (fetching, listing, creating, updating), file operations (uploading, downloading), collection management (listing, schema retrieval), log management, and migration management for database schema changes.
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 via Smithery:
Clone the repository (if you haven't already):
Install dependencies:
Build the server:
This compiles the TypeScript code to JavaScript in the build/ directory and makes the entry point executable.
This server requires the following environment variables to be set:
POCKETBASE_API_URL: The URL of your PocketBase instance (e.g., http://127.0.0.1:8090). Defaults to http://127.0.0.1:8090 if 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, see API KEYS.
These variables need to be configured when adding the server to Cline (see Cline Installation section).
The server provides the following tools, organized by category:
fetch_record: Fetch a single record from a PocketBase collection by ID.
Input Schema:
list_records: List records from a PocketBase collection. Supports pagination, filtering, sorting, and expanding relations.
Input Schema:
create_record: Create a new record in a PocketBase collection.
Input Schema:
update_record: Update an existing record in a PocketBase collection.
Input Schema:
get_collection_schema: Get the schema of a PocketBase collection.
Input Schema:
upload_file: Upload a file to a specific field in a PocketBase collection record.
Input Schema:
list_collections: List all collections in the PocketBase instance.
Input Schema:
download_file: Get the download URL for a file stored in a PocketBase collection record.
Input Schema:
Note: This tool returns the file URL. The actual download needs to be performed by the client using this URL.
list_collections: List all collections in the PocketBase instance.
Input Schema:
get_collection_schema: Get the schema of a PocketBase collection.
Input Schema:
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 at https://pocketbase.io/docs/api-logs/.
list_logs: List API request logs from PocketBase with filtering, sorting, and pagination.
Input Schema:
get_log: Get a single API request log by ID.
Input Schema:
get_logs_stats: Get API request logs statistics with optional filtering.
Input Schema:
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:
run_cron_job: Triggers a single cron job by its id.
Input Schema:
set_migrations_directory: Set the directory where migration files will be created and read from.
Input Schema:
create_migration: Create a new, empty PocketBase migration file with a timestamped name.
Input Schema:
create_collection_migration: Create a migration file specifically for creating a new PocketBase collection.
Input Schema:
add_field_migration: Create a migration file for adding a field to an existing collection.
Input Schema:
list_migrations: List all migration files found in the PocketBase migrations directory.
Input Schema:
apply_migration: Apply a specific migration file.
Input Schema:
revert_migration: Revert a specific migration file.
Input Schema:
apply_all_migrations: Apply all pending migrations.
Input Schema:
revert_to_migration: Revert migrations up to a specific target.
Input Schema:
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:
Each migration has an "up" function for applying changes and a "down" function for reverting them.
Setting a custom migrations directory:
Creating a basic migration:
Creating a collection migration:
Adding a field to a collection:
Applying migrations:
Reverting migrations:
To use this server with Cline, you need to add it to your MCP settings file (cline_mcp_settings.json).
Locate your Cline MCP settings file:
Typically found at ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json on Linux/macOS.
Or ~/Library/Application Support/Claude/claude_desktop_config.json if using the Claude desktop app on macOS.
Edit the file and add the following configuration under the Replace /path/to/pocketbase-mcp with 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.
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)
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
MCP server that allows interaction with PocketBase databases, enabling record operations (fetch, list, create, update), file management, and schema migrations through natural language.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mabeldata/pocketbase-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server