Server facts
pocketbase-mcp
Project
- Author
- tokenscompany
- Repository
- github.com/tokenscompany/pocketbase-mcp
- License
- Not specified
- Category
- Databases
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 4
- Last commit
- Data as of
Overview
PocketBase collection and record workflows sit at the center of pocketbase-mcp. Its tools let MCP clients inspect collection definitions, including fields, rules, and indexes, before creating collections or changing their schemas and rules. Bulk schema imports support migration work, while record operations cover searching, retrieving individual entries by ID, creating entries, updating them, and deleting them. A separate MCP resource exposes collection schemas in JSON form, giving clients another way to access the database structure.
Operational tools extend beyond data editing: users can check PocketBase health, list or create backups, remove backups by key, obtain download URLs for file fields, inspect or modify application settings, and query request logs. Deployment options include a hosted endpoint and self-hosting with Bun or Docker. Requests supply the target PocketBase URL alongside either superuser email and password credentials or a superuser token; a supplied token takes precedence. Setup examples cover Claude Code, Cursor, and OpenCode.
pocketbase-mcp setup notes
- pocketbase-mcp records stdio only; confirm a network transport upstream before planning remote access.
- pocketbase-mcp has no recorded license; confirm reuse terms in its repository.