PocketBase MCP Server
Related Servers
Alternatives to PocketBase MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseDqualityNot gradedmaintenanceA comprehensive MCP server that provides sophisticated tools for interacting with PocketBase databases. This server enables advanced database operations, schema management, and data manipulation through the Model Context Protocol (MCP).14822 npm70MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for managing PocketBase database schemas and migrations via REST API. It enables users to generate and execute migrations for creating, modifying, and deleting collections and fields directly through MCP-compatible clients.37 npmMIT
- AlicenseAqualityCmaintenanceA complete MCP server for PocketBase, exposing 55 tools to manage collections, records, authentication, files, logs, settings, backups, and crons.5518 npm3MIT
- FlicenseNot gradedqualityDmaintenanceMCP server integrating with PocketBase to manage tasks and projects. Enables AI models to create tasks, list tasks with status filters, and browse projects.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to manage PocketBase databases by creating collections, performing record CRUD with pagination and relation expansion, handling user authentication, and backing up data.37 npmISC
- AlicenseNot gradedqualityAmaintenanceThe PocketBase MCP Server provides sophisticated tools for interacting with PocketBase databases, enabling advanced database operations, schema management, and data manipulation through the Model Context Protocol (MCP).37 npmISC
TDQS
Scored across 22 tools
Each tool targets a distinct operation on a specific resource (collections, records, migrations, logs, cron, files). No two tools have overlapping purposes; descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_record, list_collections, apply_migration). No mixing of conventions or vague verbs.
22 tools is appropriate for a PocketBase server, covering collections, records, migrations, logs, cron, and file handling. Each tool serves a clear purpose without redundancy.
Significant gaps: no tool to delete a record or collection, and no direct create/update/delete for collections (only migration-based). This will likely cause agent failures when cleanup is needed.