Google Firestore Collection MCP Server for CursorGive Cursor instant access to 3 tools to Delete Document, Get Document, Set Document
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this MCP Server for Cursor
The Google Firestore Collection MCP Server for Cursor is a standout in the Industry Titans category — giving your AI agent 3 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
{
"mcpServers": {
"google-firestore-collection": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Google Firestore Collection and 4,000+ MCP Servers from a single visual interface.





* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Google Firestore Collection MCP Server
This server strips away dangerous global GCP permissions. It gives your AI agent one surgical superpower: the ability to query, insert, and update documents inside one specific Firestore Collection.
Cursor's Agent mode turns Google Firestore Collection into an in-editor superpower. Ask Cursor to generate code using live data from Google Firestore Collection and it fetches, processes, and writes. all in a single agentic loop. 3 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
By strictly scoping access, your AI can safely manage structured data, store chat histories, and process complex NoSQL queries without ever touching your critical cloud databases.
The Superpowers
- Absolute Containment: The agent is locked to a single collection. It cannot query other collections or drop your production data.
- Native Firestore Integration: Direct interactions with Firestore, supporting rich document structures and filters.
- Plug & Play Database: Instantly gives your agent a scalable NoSQL database to store structured memories and application state.
The Google Firestore Collection MCP Server exposes 3 tools through the Vinkius. Connect it to Cursor in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 3 Google Firestore Collection tools available for Cursor
When Cursor connects to Google Firestore Collection through Vinkius, your AI agent gets direct access to every tool listed below — spanning nosql, document-database, data-persistence, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.
Delete document on Google Firestore Collection
Delete a document from the Google Firestore collection
Get document on Google Firestore Collection
Read a document from the configured Google Firestore collection
Set document on Google Firestore Collection
If the document exists, fields are updated. Create or update a document in the Google Firestore collection
Connect Google Firestore Collection to Cursor via MCP
Follow these steps to wire Google Firestore Collection into Cursor. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Google Firestore Collection
Why Use Cursor with the Google Firestore Collection MCP Server
Cursor AI Code Editor provides unique advantages when paired with Google Firestore Collection through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Google Firestore Collection + Cursor Use Cases
Practical scenarios where Cursor combined with the Google Firestore Collection MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Google Firestore Collection in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Google Firestore Collection immediately.
"Get the document with ID 'task-99'."
"Save this workflow result to a new document 'result-123': {"status": "done", "score": 95}."
"Delete the temporary 'draft-01' document."
Troubleshooting Google Firestore Collection MCP Server with Cursor
Common issues when connecting Google Firestore Collection to Cursor through Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Google Firestore Collection + Cursor FAQ
Common questions about integrating Google Firestore Collection MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.Can Cursor use MCP tools in inline edits?
How do I verify MCP tools are loaded?
Explore More MCP Servers
View all →
Follow Up Boss
12 toolsManage real estate leads, track deals, and oversee follow-up tasks via AI agents with Follow Up Boss.

AT&T IoT
10 toolsIoT Control Center -- Manage SIM devices, activation, data pools, shared plans, and connectivity diagnostics via AT&T IoT API.

Qichacha / 企查查
10 toolsLeading enterprise data platform in China — search companies, check industrial info, and monitor risks via AI.
Honeybadger (Error Tracking)
10 toolsMonitor app exceptions and uptime via Honeybadger — list projects, resolve faults, and track deployments.
