PocketBase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POCKETBASE_URL | No | URL of your PocketBase server | http://127.0.0.1:8090 |
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 |
| delete_collectionB | Delete a collection from PocketBase |
| get_collection_schemaC | Get schema details for a collection |
| list_collectionsC | List all collections with optional sorting |
| truncate_collectionB | Delete all records associated with the specified collection |
| create_recordC | Create a new record in a collection |
| list_recordsC | List records from a collection with optional filters |
| update_recordC | Update an existing record |
| delete_recordC | Delete a record |
| authenticate_userC | Authenticate a user and get auth token |
| create_userC | Create a new user account |
| analyze_collection_dataC | Analyze data patterns and provide insights about a collection |
| query_collectionC | Advanced query with filtering, sorting, and aggregation |
| migrate_collectionC | Add, remove, or modify fields from a collection |
| backup_databaseC | Create a backup of the PocketBase database |
| import_dataC | Import data into a collection |
| manage_indexesC | Manage collection indexes |
| generate_pb_schemaB | Generate a PocketBase schema based on TypeScript interfaces or database diagram |
| generate_typescript_interfacesB | Generate TypeScript interfaces from PocketBase collections |
| upload_fileB | Upload a file to a record in PocketBase |
| download_fileC | Download a file from a record in PocketBase |
| upload_file_from_urlC | Upload a file from URL to a record in PocketBase |
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 22 tools
Most tools have distinct purposes targeting specific resources and actions, but some potential confusion exists: 'list_records' and 'query_collection' both retrieve records, though 'query_collection' offers advanced features; 'upload_file' and 'upload_file_from_url' are closely related but differentiated by source. Overall, descriptions help clarify boundaries, but minor overlaps could cause occasional misselection.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_collection', 'delete_record', and 'list_records'. All tools use snake_case with clear, descriptive verbs aligned with their actions, making the set predictable and easy to navigate without any deviations in style.
With 22 tools, the count is slightly high for a typical MCP server scope, but it is reasonable given the comprehensive coverage of PocketBase operations. It includes CRUD, schema management, data handling, and utilities, which justifies the number, though it might feel heavy compared to more focused servers.
The tool set provides complete coverage for PocketBase operations, including full CRUD for collections and records, user authentication, schema management, data import/export, file handling, and utilities like backup and analysis. There are no obvious gaps, ensuring agents can handle all core workflows without dead ends.