PocketBase MCP Server

Created By
mabeldataa year ago
This is an MCP server that interacts with a PocketBase instance. It allows you to fetch, list, create, update, and manage records and files in your PocketBase collections.
Overview

What is PocketBase MCP Server?

PocketBase MCP Server is a backend server that interacts with a PocketBase instance, enabling users to manage records and files within their PocketBase collections.

How to use PocketBase MCP Server?

To use the PocketBase MCP Server, clone the repository, install the dependencies, and configure the necessary environment variables for your PocketBase instance. Then, you can run the server and utilize its tools for record and collection management.

Key features of PocketBase MCP Server?

  • Fetch, list, create, update, and manage records in PocketBase collections.
  • Comprehensive migration system for managing database schema changes.
  • Support for file uploads and downloads within collections.

Use cases of PocketBase MCP Server?

  1. Managing user data in a PocketBase application.
  2. Performing batch updates and migrations for database schema changes.
  3. Uploading and managing files associated with records in collections.

FAQ from PocketBase MCP Server?

  • Is PocketBase MCP Server free to use?

Yes! It is open-source and free to use.

  • What programming language is used?

The server is built using TypeScript.

  • How do I set up the server?

Follow the installation instructions in the repository to clone, install dependencies, and configure your environment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mabeldata
Star
8
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago