pocketbase-mcp-connector

name	pocketbase-mcp-connector
description	MCP connector for PocketBase backend platform – enables AI-assisted collection management, auth configuration, and realtime data operations through Claude
license	MIT
tags	["dev","backend","mcp","pocketbase","baas"]
difficulty	beginner
time_to_master	4-8 weeks
version	1.0.0

Pocketbase MCP Connector

Overview

This skill enables Claude to interact with Pocketbase through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Pocketbase's REST API, allowing natural language control of Pocketbase operations, intelligent automation, and AI-powered assistance for Pocketbase workflows.

When to Use This Skill

• Collection schema design via natural language
• Auth rule and API rule configuration
• Realtime subscription management
• File storage and thumbnail configuration
• Backup and migration management

Architecture

┌─────────────┐     ┌─────────────────┐     ┌──────────────────┐
│   Claude     │────▶│   MCP Server    │────▶│   Pocketbase       │
│   (Client)   │◀────│   (TypeScript)  │◀────│   (REST API      )│
└─────────────┘     └─────────────────┘     └──────────────────┘

Core Concepts

MCP Server Setup

The connector implements an MCP server that exposes Pocketbase operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.

Key Endpoints/Interfaces

/api/collections, /api/records/:collection, /api/admins, /api/files, /api/backups

Implementation

// Pocketbase MCP Server Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({
  name: "pocketbase-mcp-connector",
  version: "1.0.0",
});

// Tool: List/Query Resources
server.tool(
  "list_resources",
  "List and query Pocketbase resources with optional filters",
  {
    query: z.string().optional().describe("Search query or filter"),
    limit: z.number().optional().describe("Max results to return"),
  },
  async ({ query, limit }) => {
    // Call Pocketbase REST API
    const response = await fetch(`${BASE_URL}/api/collections`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      : [{ : , : .(data, , ) }],
    };
  }
);


server.(
  ,
  ,
  {
    : z.().(),
    : z.({}).().().(),
  },
   ({ name, config }) => {
     response =  (, {
      : ,
      : {
        : ,
        : ,
      },
      : .({ name, ...config }),
    });
     data =  response.();
     {
      : [{ : , :  }],
    };
  }
);


server.(
  ,
  ,
  {
    : z.().(),
    : z.().().(),
  },
   ({ , timeframe }) => {
    
     response =  (, {
      : { :  },
    });
     data =  response.();
     {
      : [{ : , : .(data, , ) }],
    };
  }
);


 transport =  ();
 server.(transport);

Claude Desktop Configuration

{
  "mcpServers": {
    "pocketbase-mcp-connector": {
      "command": "node",
      "args": ["path/to/pocketbase-mcp-connector/index.js"],
      "env": {
        "POCKETBASE_API_KEY": "your-api-key",
        "POCKETBASE_BASE_URL": "https://your-instance-url"
      }
    }
  }
}

Best Practices

1. Authentication: Store API keys securely using environment variables; never hardcode credentials
2. Rate Limiting: Implement request throttling to respect Pocketbase API rate limits
3. Error Handling: Provide clear, actionable error messages for common failure scenarios
4. Pagination: Handle paginated responses for large datasets efficiently
5. Caching: Cache frequently accessed read-only data to reduce API calls
6. Security: Validate all inputs before passing to the Pocketbase API; sanitize outputs
7. Logging: Log all API interactions for debugging and audit purposes

Example Prompts

"Create a collection for Tasks with user authentication and file attachments support"

Security Considerations

• All API credentials must be stored as environment variables
• Implement input validation and sanitization for all tool parameters
• Use HTTPS for all API communications
• Follow the principle of least privilege for API token permissions
• Audit log all write operations for compliance tracking

Resources

• Pocketbase Official Documentation
• MCP SDK Documentation: https://modelcontextprotocol.io
• MCP Server Examples: https://github.com/modelcontextprotocol/servers
• SkillGalaxy Repository: https://github.com/Sandeeprdy1729/skill_galaxy

Changelog

Version	Date	Changes
1.0.0	2026-04-01	Initial MCP connector skill

---

Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.