PocketBase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POCKETBASE_URL | Yes | URL of your PocketBase instance (e.g., "http://127.0.0.1:8090") | |
| POCKETBASE_DATA_DIR | No | Custom data directory path | |
| POCKETBASE_ADMIN_EMAIL | No | Admin email for certain operations | |
| POCKETBASE_ADMIN_PASSWORD | No | Admin password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_collectionC | Create a new collection in PocketBase note never use created and updated because these are already created |
| update_collectionC | Update an existing collection in PocketBase (admin only) |
| create_recordC | Create a new record in a collection |
| list_recordsB | List records from a collection with optional filters |
| update_recordC | Update an existing record |
| delete_recordC | Delete a record |
| list_auth_methodsC | List all available authentication methods |
| authenticate_userC | Authenticate a user with email and password |
| authenticate_with_oauth2C | Authenticate a user with OAuth2 |
| authenticate_with_otpC | Authenticate a user with one-time password |
| auth_refreshC | Refresh authentication token |
| request_verificationC | Request email verification |
| confirm_verificationC | Confirm email verification with token |
| request_password_resetC | Request password reset |
| confirm_password_resetC | Confirm password reset with token |
| request_email_changeC | Request email change |
| confirm_email_changeC | Confirm email change with token |
| impersonate_userC | Impersonate another user (admin only) |
| create_userC | Create a new user account |
| get_collectionC | Get details for a collection |
| backup_databaseC | Create a backup of the PocketBase database |
| import_dataC | Import data into a collection |
| list_collectionsB | List all collections in PocketBase |
| delete_collectionB | Delete a collection from PocketBase (admin only) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Most tools have distinct purposes, but there is some overlap between authentication tools (authenticate_user, authenticate_with_oauth2, authenticate_with_otp) that could cause confusion, though their descriptions clarify the methods. Other tools like create_record and update_record are clearly differentiated by their actions on records.
Tool names follow a consistent verb_noun pattern throughout, such as authenticate_user, create_collection, list_records, and update_record. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 24 tools, the count is on the higher side for a typical MCP server, which might feel heavy and could overwhelm agents. However, given PocketBase's scope covering authentication, collections, records, and admin functions, it is borderline but still within a reasonable range for the domain.
The tool set provides comprehensive coverage for PocketBase operations, including full CRUD for collections and records, authentication methods (user, OAuth2, OTP), user management, and admin functions like backup and impersonation. No obvious gaps are present, ensuring agents can handle complete workflows.