{
"mcpServers": {
"pb-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 16 days ago. 57 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Pb_mcp_server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that provides comprehensive access to PocketBase functionality. This server enables AI assistants and other MCP clients to interact with PocketBase databases for authentication, data management, and administrative operations.
saveSession parameter# Clone the repository
git clone https://github.com/ssakone/pocketbase-mcp-server.git
cd pocketbase-mcp-server
# Install dependencies
npm install
# Build the project
npm run build
Create a .env file or set environment variables:
# PocketBase server URL (default: http://127.0.0.1:8090)
POCKETBASE_URL=http://127.0.0.1:8090
# Admin token for authenticated operations (optional - can be provided per-request)
POCKETBASE_ADMIN_TOKEN=your_admin_token_here
# Auto-authentication at startup (optional)
# If both are provided, the server will authenticate and obtain a token automatically
POCKETBASE_ADMIN_EMAIL=admin@example.com
POCKETBASE_ADMIN_PASSWORD=your_admin_password
# Output format: json (default) or toon
# TOON format reduces token usage by 30-60% when communicating with LLMs
MCP_OUTPUT_FORMAT=json
Alternatively, create a pocketbase.config.json:
{
"pocketbaseUrl": "http://127.0.0.1:8090",
"pocketbaseAdminToken": "your_admin_token_here"
}
npm start
# Default port 3001
npm run start:http
# Custom port
PORT=8080 npm run start:http
The HTTP server exposes an SSE endpoint at http://localhost:3001/sse.
Add to your MCP configuration:
{
"mcpServers": {
"pocketbase": {
"command": "npm",
"args": ["start"],
"cwd": "/path/to/pocketbase-mcp-server",
"env": {
"POCKETBASE_URL": "http://127.0.0.1:8090",
"POCKETBASE_ADMIN_EMAIL": "admin@example.com",
"POCKETBASE_ADMIN_PASSWORD": "your_password"
}
}
}
}
authenticate_adminAuthenticate as a PocketBase admin with full access to all operations.
{
"email": "admin@example.com",
"password": "adminpassword",
"baseUrl": "http://127.0.0.1:8090",
"saveSession": true
}
| Parameter | Type | Description |
|-----------|------|-------------|
| email | string | Admin email address |
| password | string | Admin password |
| baseUrl | string | PocketBase URL (optional) |
| saveSession | boolean | Save session for subsequent requests (default: true) |
authenticate_userAuthenticate as a regular user with permissions based on collection rules.
{
"email": "user@example.com",
"password": "userpassword",
"collection": "users",
"baseUrl": "h
... [View full README on GitHub](https://github.com/ssakone/pb_mcp_server#readme)