Firestore MCP Server

Created By
gitskyfluxa year ago
MCP Server to interact with Google Cloud Firestore
Overview

What is Firestore MCP Server?

Firestore MCP Server is a Model Context Protocol server designed for seamless interaction with Google Cloud Firestore, allowing users to manage Firestore documents efficiently.

How to use Firestore MCP Server?

To use the Firestore MCP Server, install the necessary dependencies, build the project, and configure it within Claude Desktop by adding specific commands and environment variables in the configuration file.

Key features of Firestore MCP Server?

  • Create, read, update, and delete documents in Firestore collections.
  • Query documents with filtering, ordering, and limits.
  • List available collections for easy management.

Use cases of Firestore MCP Server?

  1. Managing user data in a web application.
  2. Storing and retrieving product information for an e-commerce platform.
  3. Handling dynamic content for mobile applications.

FAQ from Firestore MCP Server?

  • What is required to run Firestore MCP Server?

You need Node.js installed, along with the necessary Google Cloud credentials and permissions.

  • Can I use Firestore MCP Server for multiple projects?

Yes! You can configure multiple Google Cloud projects in the setup.

  • Is there a limit to the number of documents I can manage?

Firestore has its own limitations based on the plan you are using, but the server itself does not impose additional limits.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gitskyflux
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
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