How to Use the Google Firestore Collection MCP in AutoGen

Q: How do I configure the Google Firestore Collection MCP Server in AutoGen?

Use mcpservertools with StreamableHttpServerParams pointing to your Vinkius endpoint. Pass the generated tools list directly to your AutoGen AssistantAgent constructor.

Enable multi-agent debate and consensus over your Google Firestore Collection documents in AutoGen.

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 AutoGen

Create your Vinkius account to connect Google Firestore Collection to AutoGen 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 AutoGen

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate multi-agent writes to your MCP Server

The `set_document` tool lets your AutoGen agents save structured decisions back to your Firestore collection. One agent can propose a document update, a critic agent can review it, and the execution agent writes the finalized data. This collaborative approach ensures that only verified data gets written to your NoSQL database. You eliminate single-agent errors by forcing consensus before modifying your live collection.

Share database context across AutoGen conversations

The `get_document` tool fetches shared state for your entire agent team. When a new agent joins the conversation, it reads the document to understand the current task state and user history. This setup removes the need to pass massive chat histories between agents. The Firestore document acts as a single source of truth that any agent can query at any point in the conversation loop.

Let agents delete temporary data after tasks

The `delete_document` tool allows your agents to clean up scratchpad documents once they reach a consensus. After the debate concludes and the final report is saved, the cleanup agent deletes the intermediate working files. This prevents clutter in your database. Your agents manage their own storage lifecycle, ensuring that temporary run data does not persist indefinitely.

Setup guide

Set up Google Firestore Collection MCP in AutoGen

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] package
Active Vinkius subscription with a valid endpoint token

1

Install AutoGen with MCP
Run pip install "autogen-ext[mcp]" autogen-agentchat. The MCP extension includes mcp_server_tools for stateless tool access.
2

Fetch tools from the MCP
Call mcp_server_tools(SseServerParams(url=...)) with your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Run your agent
Pass the tools to AssistantAgent and call agent.run(). The agent invokes Google Firestore Collection tools and returns structured results.

agent.py

from autogen_ext.tools.mcp import SseServerParams, mcp_server_tools
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

server_params = SseServerParams(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

tools = await mcp_server_tools(server_params)

agent = AssistantAgent(
    name="Google Firestore Collection_assistant",
    model_client=OpenAIChatCompletionClient(model="gpt-4o"),
    tools=tools,
)

result = await agent.run("List recent Google Firestore Collection data")
print(result.messages[-1].content)

Get your connection token →

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] + autogen-agentchat
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Same packages as above. McpWorkbench is ideal when your agent needs stateful sessions across multiple tool calls.
2

Use McpWorkbench as context manager
Wrap your agent in async with McpWorkbench(...) to maintain shared state and resources. The workbench manages the full MCP session lifecycle.
3

Run with workbench
Pass workbench=workbench to your agent. State is preserved across multiple tool calls within the same session.

agent.py

from autogen_ext.tools.mcp import McpWorkbench, SseServerParams
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

server_params = SseServerParams(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

async with McpWorkbench(server_params) as workbench:
    agent = AssistantAgent(
        name="Google Firestore Collection_assistant",
        model_client=OpenAIChatCompletionClient(model="gpt-4o"),
        workbench=workbench,
    )

    result = await agent.run("List recent Google Firestore Collection data")
    print(result.messages[-1].content)

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 AutoGen

Use `mcp_server_tools` with `StreamableHttpServerParams` pointing to your Vinkius endpoint. Pass the generated tools list directly to your AutoGen `AssistantAgent` constructor.

Your agents use their conversation logic to debate the write operation first. Once they agree on the payload, a single agent invokes `set_document` to update the database.

Yes. You can configure your agent definition to only receive the `get_document` tool from this MCP Server, preventing it from calling `set_document` or `delete_document` during the conversation.

The server supports both stdio and Streamable HTTP transports. AutoGen's MCP adapter handles the schema conversion automatically over your chosen connection.

Vinkius runs the server inside a zero-trust, ephemeral V8 isolate. Your raw Firestore documents are processed securely, ensuring no credentials or raw database payloads leak during agent execution.

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