How to Use the Blink Payment MCP in Google ADK

Q: How do I limit which Blink Payment tools are exposed to Google ADK?

You can use the native toolnames parameter in the Google ADK McpToolset configuration. This lets you whitelist only safe tools like getpayment or listcustomers while blocking destructive actions like refundpayment.

Q: Can Gemini analyze massive Blink Payment transaction lists with Google ADK?

Absolutely. You can use listpayments to pull transaction logs and pass them directly into Gemini's long-context window via Google ADK to find specific billing patterns.

Connect Blink Payment to Gemini models using Google ADK to process transactions directly from your enterprise data pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Blink Payment MCP to Google ADK

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Analyze Blink Payment trends using Google ADK

The `list_payments` and `list_paylinks` tools allow your Gemini agents in Google ADK to fetch transaction records and match them against your company records. Because Google ADK integrates with Vertex AI and BigQuery, your agent can cross-reference live Blink Payment statuses with cold warehouse data. Feeding months of raw output from `get_payment` into a single Google ADK agent prompt is easy with Gemini's massive 1M+ token context window. Your agent can then spot billing anomalies or run complex Blink Payment refund audits without hitting context limits.

Direct checkout generation from cloud databases

The `create_paylink` and `create_payment_intent` tools enable your Google ADK enterprise agents to generate bills based on database triggers. If an SQL query in BigQuery flags an unpaid account, the Google ADK agent can automatically build a Blink Payment link. You can restrict the agent's capabilities by using the `tool_names` filter in your Google ADK setup. Hiding `create_paylink` from the MCP server while only exposing `get_payment` works perfectly if you only want your support agent to check statuses.

Automated enterprise customer sync

The `create_customer` tool lets your Google ADK agent sync new signups from your Google Cloud databases straight into your Blink Payment directory. When a new row hits your database, the Google ADK agent reads it and registers them using `get_customer` to verify. Running this on Vinkius means your Google Cloud Functions can interact with the MCP transport via simple HTTP. There is no need to manage complex SSH tunnels or store Blink Payment API keys inside your Google ADK code.

Setup guide

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

Yes, you pass the MCP toolset pointing to your Vinkius URL into the `LlmAgent` constructor. The Gemini model inside Google ADK will then be able to call `create_payment_intent` and other tools during its reasoning loop.

You can use the native `tool_names` parameter in the Google ADK `McpToolset` configuration. This lets you whitelist only safe tools like `get_payment` or `list_customers` while blocking destructive actions like `refund_payment`.

Yes, Google ADK supports both transports, but using the Vinkius hosted MCP endpoint is recommended for cloud deployments. It allows your serverless functions to access the tools without running persistent local processes.

Absolutely. You can use `list_payments` to pull transaction logs and pass them directly into Gemini's long-context window via Google ADK to find specific billing patterns.

Your API credentials are encrypted and stored inside the Vinkius zero-trust vault. Individual payment transaction payloads pass through ephemeral V8 isolates, meaning Google ADK never exposes raw API keys to the LLM provider.

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