pocketbase-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POCKETBASE_URL | No | Base URL of your PocketBase instance (e.g. http://127.0.0.1:8090) | |
| POCKETBASE_API_KEY | No | Long-lived API key (alternative to email/password) | |
| POCKETBASE_SUPERUSER_EMAIL | No | Superuser email for admin operations | |
| POCKETBASE_SUPERUSER_PASSWORD | No | Superuser 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_with_passwordB | Authenticate a user or superuser with email and password. |
| get_auth_storeB | Return the current authentication state. Returns: A dict with the active token and all stored sessions. |
| list_collectionsC | List all collections with optional filtering, sorting, and pagination. |
| get_collectionC | Get a collection schema by name or ID. |
| create_collectionC | Create a new collection with fields and API rules. |
| update_collectionC | Update a collection's schema or rules. |
| delete_collectionC | Delete a collection by name or ID. |
| list_recordsB | List records in a collection with filtering, sorting, and pagination. |
| get_recordC | Get a single record by ID. |
| create_recordC | Create a new record in a collection. |
| update_recordC | Update an existing record. |
| delete_recordB | Delete a record by ID. |
| batch_recordsC | Perform multiple create/update/upsert/delete operations in one request. |
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 13 tools
Each tool has a clearly distinct resource and action: collections, records, batch operations, and authentication are cleanly separated. The only overlap is batch_records versus individual record operations, but their boundaries are obvious.
Nearly all tools use snake_case verb_noun naming such as list_collections, create_record, and delete_collection. auth_with_password is a minor deviation, but it remains readable and consistent with the overall verb-led style.
The set has 13 tools, which is well within the appropriate range for a PocketBase CRUD and auth server. Every tool appears to earn its place without excessive surface area.
Core CRUD coverage is strong for both collections and records, including batch operations and authentication. Minor gaps exist around auth lifecycle operations such as logout or token refresh, but the main workflows are covered.