PocketBase MCP Server

Created By
brynnjocelyna year ago
Overview

what is PocketBase MCP Server?

PocketBase MCP Server is a comprehensive Model Context Protocol (MCP) server designed to manage PocketBase instances, allowing LLMs to interact with PocketBase databases through a standardized protocol.

how to use PocketBase MCP Server?

To use the PocketBase MCP Server, install it via npm, configure it to connect to your PocketBase instance, and utilize the provided tools for managing collections, records, authentication, and more.

key features of PocketBase MCP Server?

  • Collection management with CRUD operations and schema support.
  • Record operations including filtering, sorting, and pagination.
  • Authentication and user management with multiple auth methods.
  • File management with URL generation and private token support.
  • System operations for health monitoring and settings management.
  • Backup and restore functionalities.
  • Hook management for JavaScript hooks.

use cases of PocketBase MCP Server?

  1. Managing database collections and records efficiently.
  2. Implementing user authentication flows in applications.
  3. Automating backup and restore processes for data safety.
  4. Integrating with LLM applications for enhanced data interaction.

FAQ from PocketBase MCP Server?

  • What is the purpose of the MCP Server?

The MCP Server facilitates interaction between LLMs and PocketBase databases using a standardized protocol.

  • How do I install the MCP Server?

You can install it using npm with the command npm install followed by npm run build.

  • What authentication methods are supported?

The server supports password, OAuth2, and OTP authentication methods.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
brynnjocelyn
Star
0
Language
JavaScript
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.

11 hours ago
Voyei

an hour ago