Advanced PocketBase MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Advanced PocketBase MCP Server?

The Advanced PocketBase MCP Server is a comprehensive server designed for sophisticated interactions with PocketBase databases, enabling advanced database operations, schema management, and data manipulation through the Model Context Protocol (MCP).

How to use Advanced PocketBase MCP Server?

To use the server, set up your PocketBase instance, configure the required environment variables, and utilize the provided tools for collection management, record operations, user management, and database operations.

Key features of Advanced PocketBase MCP Server?

  • Collection management with custom schemas and migration support.
  • CRUD operations for records with advanced querying capabilities.
  • User authentication and role-based access control.
  • Database backup, restore, and data migration tools.
  • Comprehensive TypeScript type definitions for development.

Use cases of Advanced PocketBase MCP Server?

  1. Managing complex database schemas and collections.
  2. Performing batch operations for data import/export.
  3. Implementing user authentication and session management.
  4. Backing up and restoring database states.

FAQ from Advanced PocketBase MCP Server?

  • Is the server compatible with all versions of PocketBase?

Yes, it is designed to work with the latest versions of PocketBase.

  • How do I install the server?

You can install it via Smithery or by cloning the repository and following the setup instructions.

  • What programming languages are supported?

The server is primarily built with JavaScript and includes TypeScript definitions for type safety.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
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