docs/dev-guides/agent-context/google-vertex-ai.md
📚 Navigation: ← Back to Agent Context Kit | Google ADK Integration →
Google Vertex AI Agent Builder provides a visual, low-code environment for building AI agents — but agents often struggle with data questions because they:
The Vertex AI integration lets you connect the DataHub MCP server to your Vertex AI agent visually, enabling your agents to answer data questions accurately using real metadata from your organization.
Agent Designer is a low-code visual designer built into the Google Cloud Console as part of Vertex AI Agent Builder. It lets you design and test agents in the browser, then export the generated code for further development.
Note: Agent Designer is currently a preview feature.
https://<tenant>.acryl.io/integrations/ai/mcp)DataHub) and your DataHub MCP endpoint URL.Important: The Agent Designer UI only supports MCP servers that do not require authentication. If your DataHub MCP server requires a bearer token (as DataHub Cloud does), the UI cannot pass authentication headers.
To work around this, use the "Get code" button in Agent Designer to export the generated agent code, then add the Authorization header manually:
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
MCP_URL = "https://<tenant>.acryl.io/integrations/ai/mcp"
YOUR_TOKEN = "<your-datahub-token>"
toolset = McpToolset(
connection_params=StreamableHTTPConnectionParams(url=MCP_URL),
# Add the Authorization header here — the UI cannot do this for you
headers={"Authorization": f"Bearer {YOUR_TOKEN}"},
)
See the Google ADK Integration page for a complete working example with authentication.
Once you're happy with your agent design, click "Get code" to view the full source code representation of your agent. You can copy this code into your editor and continue development using:
This allows you to start with the visual designer for rapid prototyping and then transition to code for production-grade agents that require authentication, custom logic, or CI/CD deployment.