PocketBase MCP Server
PocketBase MCP server enabling AI agents to interact with PocketBase — the popular single-file open-source backend (BaaS) built with Go and SQLite. Enables querying and modifying collections, managing records, handling file attachments, managing authentication, and integrating PocketBase's real-time database and API into agent workflows for rapid application development and data management.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
API key auth. Use collection-scoped tokens not admin tokens. HTTPS for network deployment. Protect SQLite DB file. Self-hosted data stays local.
⚡ Reliability
Best When
A developer using PocketBase as their application backend needs AI assistance managing data — PocketBase's simple REST API makes it easy to expose via MCP for agent-driven data management.
Avoid When
You need distributed database capabilities, are already on a production database system, or need advanced SQL features beyond SQLite.
Use Cases
- • Reading and writing records in PocketBase collections from data management agents
- • Querying PocketBase data with filters and sorting from search agents
- • Managing PocketBase users and authentication from identity management agents
- • Handling file uploads and attachments from media management agents
- • Administering PocketBase collections and schema from DevOps agents
- • Building agent-backed applications using PocketBase as data store from app development agents
Not For
- • High-scale production databases requiring distributed architecture (PocketBase is single-node SQLite)
- • Teams already using PostgreSQL, MongoDB, or other dedicated databases
- • Multi-region/high-availability requirements
Interface
Authentication
PocketBase API key (admin token) or user credentials. Admin API key for full access; user tokens for collection-level access. Configure POCKETBASE_URL and POCKETBASE_ADMIN_TOKEN as env vars. Self-hosted: PocketBase must be running.
Pricing
PocketBase is completely free and open source. MCP server is free. Self-host on any server (single Go binary).
Agent Metadata
Known Gotchas
- ⚠ PocketBase must be running locally or on accessible server — not a managed cloud service
- ⚠ SQLite write throughput limits (concurrent writes serialize) — agents should avoid write-heavy parallel operations
- ⚠ Collection schema changes (adding fields) require admin access — be careful with schema migrations
- ⚠ PocketBase is evolving quickly — API may change between versions; pin PocketBase version
- ⚠ Admin token grants full access — create collection-specific user tokens for agent access to specific collections
- ⚠ File/attachment operations require multipart form upload — verify MCP handles file upload correctly
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for PocketBase MCP Server.
Scores are editorial opinions as of 2026-03-06.