How to Use the Builder.io MCP in Google ADK

Q: Can I filter which Builder.io tools my Google ADK agent sees?

Yes. The framework allows you to define a toolnames filter. This restricts the agent to only the specific CMS operations you want to permit.

Connect your Google ADK agents to Builder.io for direct CMS management.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Builder.io MCP to Google ADK

Create your Vinkius account to connect Builder.io to Google ADK 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 Builder.io with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Builder.io integration for Google ADK

The `get_space` and `get_model` tools give your agent a map of your entire CMS infrastructure. It reads the model definitions so it can structure new content entries correctly. This integration allows your agent to work with your BigQuery data and CMS content simultaneously. It bridges the gap between your cloud analytics and your frontend assets.

Search content entries via Google ADK tools

You can use `list_content` to find specific entries matching your criteria. The agent filters through your CMS records to find the right data to update or reference. This works well with the long-context capabilities of Gemini models. Your agent keeps track of large content sets without losing the thread.

Manage CMS symbols through the Google ADK

The `list_symbols` tool exposes your reusable components to the agent. It can now identify which parts of your site are modular and ready for updates. By feeding these symbols into the agent, you ensure it only modifies defined components. This avoids breaking your site's visual consistency.

Setup guide

Set up Builder.io MCP in Google ADK

Prerequisites

Python 3.10+ installed
google-adk package (pip install google-adk)
Active Vinkius subscription with a valid endpoint token

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with Builder.io tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="Builder.io_agent",
    model="gemini-2.0-flash",
    instruction="You have access to Builder.io tools via MCP.",
    tools=mcp_tools,
)

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 Builder.io. 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 Builder.io 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 Builder.io MCP in Google ADK

Yes. You pass the server parameters to the McpToolset and add it to your LlmAgent configuration. It supports both Stdio and HTTP transports.

Yes. The framework allows you to define a tool_names filter. This restricts the agent to only the specific CMS operations you want to permit.

Your agent uses the server to fetch content schemas and entries that fill its context window. It then uses that data to reason through complex content updates.

No. Once you set the server URL in your StreamableHttpServerParameters, the ADK handles the handshake and tool registration automatically.

We use scoped tokens to authenticate every request. Your content entries are retrieved via secure channels and the server logs only the metadata required for system health.

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