How to Use the Google Firestore Collection MCP in LlamaIndex

Q: How do I register the Google Firestore Collection MCP Server in LlamaIndex?

Install llama-index-tools-mcp and initialize the BasicMCPClient with your Vinkius server URL. Wrap the client in McpToolSpec and call totoollistasync to pass the tools to your agent.

Q: What happens if a document is missing when LlamaIndex requests it from Google Firestore Collection?

The getdocument tool returns an empty result or error state. Your LlamaIndex agent reads this response and can choose to create the record using the setdocument tool instead.

Index and retrieve Google Firestore Collection documents directly within LlamaIndex RAG pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Google Firestore Collection MCP to LlamaIndex

Create your Vinkius account to connect Google Firestore Collection to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Google Firestore Collection with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Ground LlamaIndex queries in live Firestore data

The `get_document` tool pulls raw records from your Google Firestore Collection directly into your query engine. Your LlamaIndex agent reads the document payload and uses it to construct answers based on real database records rather than static files. This MCP Server integration allows you to build RAG systems that query live transactional data. The agent fetches the document, parses the fields, and feeds the content straight into the local index.

Update index metadata using LlamaIndex agents

The `set_document` tool writes structured data back to your collection during index processing. When your LlamaIndex agent extracts new entities or updates metadata, it saves those changes directly to the database. You avoid writing custom pipeline connectors to synchronize your vector store with your primary database. The agent updates the Firestore document in real-time as it parses and processes your documents.

Purge stale knowledge from your database

The `delete_document` tool removes obsolete records from your Firestore collection. When a LlamaIndex agent identifies outdated user profiles or expired sessions during a task, it deletes the record immediately. This direct write-back keeps your storage footprint minimal. Your agent maintains database hygiene without requiring separate cron jobs or manual database administration.

Setup guide

Set up Google Firestore Collection MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Google Firestore Collection MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Google Firestore Collection tools.",
)
response = await agent.run("List recent Google Firestore Collection data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Google Firestore Collection. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Google Firestore Collection now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Google Firestore Collection MCP in LlamaIndex

Install `llama-index-tools-mcp` and initialize the `BasicMCPClient` with your Vinkius server URL. Wrap the client in `McpToolSpec` and call `to_tool_list_async` to pass the tools to your agent.

No. The server does not support collection-wide semantic queries. Your LlamaIndex agent uses `get_document` to fetch specific records by ID, then indexes that retrieved text for local semantic search.

The `get_document` tool returns an empty result or error state. Your LlamaIndex agent reads this response and can choose to create the record using the `set_document` tool instead.

Yes. You can filter the tools passed to your agent. If you only want your pipeline to read data, pass only `get_document` and omit `set_document` and `delete_document`.

Vinkius handles the database authentication safely inside an ephemeral sandbox. Your Firestore credentials are never exposed to LlamaIndex or the LLM, keeping your NoSQL records completely isolated.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript