Firestore, verified
MCP server by Google Cloud · Verified
Read and write Firestore documents and manage databases, indexes, backups and backup schedules in Google Cloud.
Connect to Firestore
Firestore needs sign-in. Connect with its own URL:
Your client opens Google Cloud’s sign-in the first time you use it. The token stays between your client and Google Cloud.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/firestoreAbout
Connects an assistant to Google Cloud Firestore. It can get, create, update, delete and list documents, list the collections under a document, and manage databases, composite indexes, backups and backup schedules.
Runs as a hosted streamable HTTP endpoint at https://firestore.googleapis.com/mcp. Access uses Google OAuth 2.0 and is governed by IAM permissions on your Google Cloud project. Several tools are destructive (deleting documents, databases, indexes, backups), so grant roles carefully.
What you can do
- Get, add, update, delete and list Firestore documents
- List collection IDs under a document
- Create, update, get, list and delete databases
- Create, get, list and delete composite indexes
- Get, list and delete backups
- Create, update, get, list and delete backup schedules
Tools 23
get_documentRead-onlyGet a document from a Firestore database.
add_documentWritesCreate a document in a collection.
update_documentWritesUpdate an existing document.
delete_documentCan deleteDelete a document (destructive).
list_documentsRead-onlyList documents in a collection.
list_collectionsRead-onlyList collection IDs underneath a document.
create_databaseWritesCreate a Firestore database.
get_databaseRead-onlyGet details of a Firestore database.
list_databasesRead-onlyList Firestore databases in a project.
update_databaseWritesUpdate a Firestore database.
delete_databaseCan deleteDelete a Firestore database (destructive).
create_indexWritesCreate a composite index.
Show 11 more tools
get_indexRead-onlyGet a Firestore index.
list_indexesRead-onlyList Firestore indexes.
delete_indexCan deleteDelete a Firestore index (destructive).
get_backupRead-onlyGet a Firestore backup.
list_backupsRead-onlyList Firestore backups.
delete_backupCan deleteDelete a Firestore backup (destructive).
create_backup_scheduleWritesCreate a Firestore backup schedule.
get_backup_scheduleRead-onlyGet a Firestore backup schedule.
list_backup_schedulesRead-onlyList backup schedules for a database.
update_backup_scheduleWritesUpdate a Firestore backup schedule.
delete_backup_scheduleCan deleteDelete a Firestore backup schedule (destructive).
Read from the live server on 3 Oct 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
List the collections under the users document in my Firestore database.
Add a document to the orders collection with status pending.
Show all composite indexes in my project's default database.
Create a daily backup schedule for my Firestore database.
Set up
Every client connects to firestore.googleapis.com, and Google Cloud asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http firestore https://firestore.googleapis.com/mcp- Start Claude Code, type
/mcp, pick firestore and choose Authenticate. A browser window opens for the Google Cloud sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it Firestore and paste this URL:
https://firestore.googleapis.com/mcp- Click Add, then Connect, and sign in when Google Cloud asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://firestore.googleapis.com/mcpand click Add. - Click Connect and sign in when Google Cloud asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://firestore.googleapis.com/mcpas the server URL and choose OAuth. ChatGPT sends you to Google Cloud to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"firestore": {
"url": "https://firestore.googleapis.com/mcp"
}
}
}Cursor shows Needs login next to the server. Click it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"firestore","type":"http","url":"https://firestore.googleapis.com/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"firestore": {
"type": "http",
"url": "https://firestore.googleapis.com/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"firestore": {
"serverUrl": "https://firestore.googleapis.com/mcp"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add firestore --url https://firestore.googleapis.com/mcp
codex mcp login firestoreOr edit ~/.codex/config.toml directly:
[mcp_servers.firestore]
url = "https://firestore.googleapis.com/mcp"Gemini CLI
gemini mcp add --transport http firestore https://firestore.googleapis.com/mcpThen, inside Gemini CLI, run /mcp auth firestore to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"firestore": {
"type": "http",
"url": "https://firestore.googleapis.com/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://firestore.googleapis.com/mcp.
FAQ
Can I paste mcp.tc/i/firestore into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://firestore.googleapis.com/mcp, so your client talks to Firestore directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Firestore need an API key or a sign-in?
Yes, you need a Google Cloud account. The first time your client connects, it opens Google Cloud’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is Firestore a remote or a local server?
Remote. Google Cloud hosts it at https://firestore.googleapis.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Firestore do?
It has 23 tools, including get_document, add_document and update_document. You can get, add, update, delete and list Firestore documents, list collection IDs under a document and create, update, get, list and delete databases.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc’s robot read Firestore’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Embed
Show Firestore in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
README badge
[](https://mcp.tc/i/firestore)<a href="https://mcp.tc/i/firestore"><img src="https://mcp.tc/i/firestore/badge.svg" alt="Firestore on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/firestore.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/firestore" title="Firestore on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/firestore.jsonmcp.tc isn’t affiliated with Google Cloud. This page was built from Firestore’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.