pocketbase-mcp-server MCP Server

Name: pocketbase-mcp-server MCP Server
Author: imiborbas

@imiborbas

Repository

About pocketbase-mcp-server MCP Server

Model Context Protocol Server for PocketBase

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "pocketbase-mcp-server": {
      "command": "node",
      "args": [
        "build/index.js",
        "--pb-url=http://localhost:8090",
        "[email protected]",
        "--pb-admin-password=your-secure-password"
      ]
    }
  }
}

Tools

List all collections from a PocketBase instance

Overview

What is pocketbase-mcp-server?

pocketbase-mcp-server is a TypeScript-based Model Context Protocol (MCP) server that provides a tool for listing all collections from a PocketBase instance. It is designed for developers using MCP-compatible hosts like Claude Desktop who need to query PocketBase schemas programmatically.

How to use pocketbase-mcp-server?

Install dependencies with npm install, build with npm run build, then configure the server with your PocketBase instance URL, admin email, and password – either as command-line arguments (--pb-url, --pb-admin-email, --pb-admin-password) or environment variables (PB_URL, PB_ADMIN_EMAIL, PB_ADMIN_PASSWORD). Add the server to your MCP host configuration (e.g., Claude Desktop’s claude_desktop_config.json) or run directly via the command line.

Key features of pocketbase-mcp-server

Lists all collections from a PocketBase instance.
Returns JSON representation of collections.
Configurable via CLI arguments or environment variables.
Built with TypeScript for reliable type safety.
Compatible with MCP‑capable AI assistants and tools.

Use cases of pocketbase-mcp-server

Querying PocketBase schema from an AI assistant like Claude.
Automating collection discovery during development.
Integrating PocketBase data management into MCP workflows.

FAQ from pocketbase-mcp-server

How do I point the server to my PocketBase instance?

Provide the PocketBase URL, admin email, and admin password either as command-line flags (--pb-url, --pb-admin-email, --pb-admin-password) or by setting environment variables (PB_URL, PB_ADMIN_EMAIL, PB_ADMIN_PASSWORD).