Dynamic PocketBase

A dynamic MCP server that exposes and manages PocketBase collections and records via runtime tools.

typescript

1

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "fadlee-dynamic-pocketbase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dynamic-pocketbase-mcp"
      ],
      "env": {
        "POCKETBASE_URL": "http://localhost:8090"
      }
    }
  }
}

You can run a dynamic MCP server for PocketBase that lets you inspect and manipulate collections and records across any PocketBase project using runtime tools. Install once, connect your AI client, and manage schema, data, and authentication through a consistent, collection-agnostic interface.

How to use

You will use an MCP client to interact with the dynamic PocketBase MCP server. Start the MCP server locally, point your client at the correct PocketBase URL, and then perform actions like listing collections, viewing and creating collections, and creating or updating records. Authentication is handled through dedicated tools, so you can sign in as an admin or a user, check your status, and log out when needed. Tools expose live PocketBase collections as resources, so you can work with any existing or newly created collection without regenerating server code.

How to install

npm install dynamic-pocketbase-mcp
# or
bun install dynamic-pocketbase-mcp

Additional notes and setup guidance

Configure your MCP client to connect to the server. The server defaults to a PocketBase URL of http://localhost:8090 if you do not set POCKETBASE_URL. You can also run the server directly with a simple command, and specify a different PocketBase URL if needed.

Example startup commands when you are ready to run the MCP server in standard mode: use the default PocketBase URL or override it with POCKETBASE_URL.

Security and usage notes

Sessions are managed through dedicated authentication tools. You can authenticate as an admin or a regular user, check the current authentication status, and log out to clear the session.

Troubleshooting tips

If you encounter connection issues, verify that PocketBase is reachable at the configured URL, confirm POCKETBASE_URL is set correctly, and ensure your MCP client is pointed at the right server endpoint. Check health status regularly to confirm the PocketBase server is responsive.

Available tools

health

Check PocketBase server health status

set_base_url

Update PocketBase URL for the current MCP session and clear the auth token

get_field_schema_reference

Get field types documentation

get_rules_reference

Get API rules syntax reference

auth_admin

Authenticate as admin/superuser

auth_user

Authenticate as auth collection user (email/username)

get_auth_status

Check current authentication status

logout

Clear authentication session

list_collections

List all collections

view_collection

View collection by name or ID

create_collection

Create a new collection

update_collection

Update collection schema/settings

delete_collection

Delete a collection

update_collection_rules

Update access control rules

list_records

List/search records with filtering, sorting, pagination

view_record

View a single record by ID

create_record

Create a new record

update_record

Update an existing record

delete_record

Delete a record