PocketBase MCP Server

Created By
mrwyndhama year ago
MCP server for building PocketBase apps really quickly - Need a front end quick consider FastPocket
Overview

what is PocketBase MCP Server?

PocketBase MCP Server is a tool designed for building PocketBase applications quickly, providing sophisticated tools for interacting with PocketBase databases through the Model Context Protocol (MCP).

how to use PocketBase MCP Server?

To use the MCP server, configure it in your cline_mcp_settings.json file, specifying the server's settings, and then start the server using Node.js.

key features of PocketBase MCP Server?

  • Collection management with custom schemas
  • CRUD operations for records
  • User authentication and management
  • Database backup capabilities

use cases of PocketBase MCP Server?

  1. Creating and managing collections for data storage
  2. Performing CRUD operations on records
  3. Managing user accounts and authentication
  4. Backing up PocketBase databases

FAQ from PocketBase MCP Server?

  • What is the purpose of the MCP server?

The MCP server facilitates advanced database operations and schema management for PocketBase applications.

  • How do I configure the MCP server?

You need to edit the cline_mcp_settings.json file to set up the server configuration.

  • Is there support for user management?

Yes, the MCP server includes features for user authentication and account management.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mrwyndham
Star
1
Language
JavaScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago