Skip to content
Pocketbase logo

Pocketbase MCP server

Interact with your PocketBase instance using superuser credentials.

Pocketbase is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
6
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
August 2026

About the Pocketbase MCP server

Connect Pocketbase once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Pocketbase and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Pocketbase tools your AI can run

Once connected, your assistant can call any of these Pocketbase actions by asking in plain language.

  • Get Full List

    Gets all the data for a given collection

    5 fields

  • Get List

    Gets a paginated list of records from a collection

    8 fields

  • Get Record

    Gets a single record by ID from a collection

    4 fields

  • Create Record

    Creates a new record in a collection

    4 fields

  • Update Record

    Updates a single record in a collection

    5 fields

  • Delete Record

    Deletes a single record from a collection

    2 fields

Give your assistant Pocketbase

Connect Pocketbase once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Pocketbase MCP, answered.

No. That is the point of it. One Activepieces server exposes Pocketbase alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Pocketbase in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 6 tools, including Get Full List, Get List, Get Record, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.