PocketBase MCP Server
PocketBase MCP server enabling AI agents to interact with PocketBase backend-as-a-service — querying and managing collections and records, handling authentication and users, accessing real-time subscriptions, and integrating PocketBase's lightweight self-hosted backend into agent-driven application data management and backend automation workflows.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS requires reverse proxy. Admin email/password. Collection-level access rules. Community MCP server. Configure HTTPS. Use scoped auth where possible. Protect admin credentials.
⚡ Reliability
Best When
An agent needs to interact with a PocketBase backend — for small application data management, rapid prototyping, or lightweight self-hosted backend automation.
Avoid When
You're running at scale or using Supabase, Firebase, or another BaaS — or if you need a distributed database with high concurrency.
Use Cases
- • Querying and managing PocketBase collections from application data agents
- • Creating and updating records from content management agents
- • Managing users and authentication from admin agents
- • Exploring collection schema and relationships from data discovery agents
- • Building CRUD automation for small application backends from development agents
- • Inspecting application data for debugging from troubleshooting agents
Not For
- • Large-scale production backends (PocketBase is designed for small-to-medium projects)
- • Teams using Supabase, Firebase, or other BaaS platforms
- • High-concurrency applications (PocketBase SQLite backend has concurrency limits)
Interface
Authentication
PocketBase admin credentials (email/password) for admin API access. Collection-level auth rules control access. Admin token or user token depending on operation. Simple single-file deployment.
Pricing
PocketBase is completely open source and free. Single binary with embedded SQLite. No managed cloud offering — self-hosted only. MCP server is community open source and free.
Agent Metadata
Known Gotchas
- ⚠ Admin credentials give full access — agents should use collection-scoped auth where possible
- ⚠ PocketBase API requires knowing collection names — no automatic schema discovery
- ⚠ SQLite backend means no concurrent writes — agents must not parallelize write operations
- ⚠ Collection rules (filter, sort, expand) must be understood for correct queries
- ⚠ Community MCP server — PocketBase is evolving; API may change between versions
- ⚠ Self-hosted: no TLS by default — must configure reverse proxy (nginx/caddy) for HTTPS
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.