How to Use the CallPage MCP in Google ADK

Q: How do I configure the CallPage MCP Server for Google ADK?

Install the google-adk package and create an McpToolset using your Vinkius URL. Pass that toolset to your LlmAgent initialization. You can use the toolnames filter if you only want to expose specific endpoints.

Q: Can Google ADK merge CallPage leads with BigQuery?

Yes, your agent can run listleads to pull recent callbacks. It then writes that data into BigQuery tables using native ADK integrations. Gemini handles the schema mapping automatically.

Give your Google ADK agents access to CallPage to analyze callback data alongside BigQuery using Gemini's massive context window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CallPage MCP to Google ADK

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Analyze thousands of leads with Google ADK

The `list_leads` tool feeds raw prospect data directly into your Gemini context window. Because Google's models handle millions of tokens, you can dump months of lead history into a single prompt. The agent reads the captured contact details without choking on context limits. Individual prospect histories require `get_lead_details`. You can cross-reference this CallPage data with existing customer records stored in BigQuery. The ADK handles the transport layer while Gemini does the heavy lifting.

Process call recordings and metadata

Fetching your callback history happens through the `list_calls` tool. It returns timestamps, durations, and URLs for the actual voice recordings. You can pipe these recording links straight into Vertex AI for transcription and sentiment analysis. Specific conversation metrics come from `get_call_details`. This MCP Server lets your Google Cloud agents verify exactly when a sales rep connected with a prospect. Everything runs over a standard HTTP transport setup.

Map sales departments and widgets

Your agent pulls your organizational structure using `list_departments` and `list_managers`. This data helps the model understand who owns which territory. You just pass the Vinkius URL into `McpToolset` and the agent maps the tools automatically. Extracting form configurations requires `get_widget_settings` and `list_widgets`. If a specific callback widget stops converting, Gemini can read the settings and suggest optimizations. The `list_sms_templates` tool also shows what automated text messages are firing.

Setup guide

Set up CallPage 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 CallPage 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="CallPage_agent",
    model="gemini-2.0-flash",
    instruction="You have access to CallPage 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 CallPage. 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 CallPage 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 CallPage MCP in Google ADK

Install the `google-adk` package and create an `McpToolset` using your Vinkius URL. Pass that toolset to your `LlmAgent` initialization. You can use the `tool_names` filter if you only want to expose specific endpoints.

Yes, your agent can run `list_leads` to pull recent callbacks. It then writes that data into BigQuery tables using native ADK integrations. Gemini handles the schema mapping automatically.

The massive context window is perfect for this. You can pull the entire output of `list_calls` and `list_sms_templates` into one prompt. The agent reads the whole dataset to find patterns in your callback strategy.

The ADK allows you to restrict tool access. If you only want the agent reading metrics, expose `get_call_details` and hide the rest. This keeps the model focused on specific tasks.

We route all traffic through a zero-trust architecture. When your agent fetches audio recording URLs or caller phone numbers, the execution happens in a temporary sandbox. The credentials exist only for the duration of that specific API call.

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