Can I automatically refund payments without ever navigating to the Clip website?

Yes. The `refund_transaction` interface executes server-side cryptographic voiding. Pass the definitive transaction ID alongside an optional amount override, and the refund logic routes directly through Clip's banking partners unconditionally.

Are the payment links generated permanent or do they have expiration windows?

By default, Payment links created via this endpoint remain actively valid until either paid successfully or explicitly halted. You can seamlessly use the `cancel_payment_link` tool to kill rogue links manually blocking external vulnerability loopholes.

Can the agent check if physical POS terminals are active and connected to my account?

Yes. The `list_terminals` endpoint fetches the fleet array directly from Clip servers. It outputs device IDs mapped to your registry ensuring no unauthorized POS physical readers are leeching payments stealthily.

Clip API MCP Server for Google ADK 10 tools — connect in under 2 minutes

Name: Clip API
Availability: InStock
Author: Vinkius

google.github.io/adk-docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Clip API as an MCP tool provider through the Vinkius and your ADK agents can call every tool with full schema introspection.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token — get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="clip_api_agent",
    instruction=(
        "You help users interact with Clip API "
        "using 10 available tools."
    ),
    tools=[mcp_tools],
)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Clip API MCP Server

Directly empower your intelligent agents with the Clip API, the undisputed champion of point-of-sale and card payment gateways across Mexico. Bypass clunky merchant dashboards by commanding 10 specialized financial tools built to execute transactions, force refunds, and reconcile bulk backend settlements securely through plain text.

Google ADK natively supports Clip API as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

What you can do

Payment Link Generation — Programmatically spin up highly secure payment links instantly firing off collection demands mapped directly to specific user workflows without manual UI clicks.
Transaction Auditing — Track pending authorizations scanning exact balances sniffing out potential fraud drops analyzing transaction statuses aggressively.
Automated Reconciliations — Pull bulk settlement reports extracting clean matrices charting precisely when cash pipelines hit your registered banks.
Inventory & Subscription — Manage deep catalog arrays syncing SKUs and dictating heavy recurring billing cycles charging Mexican cards passively.

The Clip API MCP Server exposes 10 tools through the Vinkius. Connect it to Google ADK in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Clip API to Google ADK via MCP

Follow these steps to integrate the Clip API MCP Server with Google ADK.

Install Google ADK

Run pip install google-adk

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Create the agent

Save the code above and integrate into your ADK workflow

Explore tools

The agent will discover 10 tools from Clip API via MCP

Why Use Google ADK with the Clip API MCP Server

Google ADK provides unique advantages when paired with Clip API through the Model Context Protocol.

Google ADK natively supports MCP tool servers — declare a tool provider and the framework handles discovery, validation, and execution

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Clip API

Production-ready features like session management, evaluation, and deployment come built-in — not bolted on

Seamless integration with Google Cloud services means you can combine Clip API tools with BigQuery, Vertex AI, and Cloud Functions

Clip API + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Clip API MCP Server delivers measurable value.

Enterprise data agents: ADK agents query Clip API and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine Clip API tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query Clip API regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Clip API

Clip API MCP Tools for Google ADK (10)

These 10 tools become available when you connect Clip API to Google ADK via MCP:

add_product_to_catalog

Add a new item to the Clip Point of Sale catalog

cancel_payment_link

Void an active payment link

create_payment_link

Generate a Clip payment link to charge customers via card

create_subscription_plan

Build a recurring billing cycle charging clients periodically

get_balance_summary

Retrieve cash balance awaiting settlement

get_settlement_reports

Fetch detailed historical settlement reports

get_transaction_status

Retrieve the status of a payment transaction

list_products_catalog

Pull the complete inventory catalog registered in Clip

list_terminals

List all registered physical POS Clip terminals

refund_transaction

Omit amount for full refund. Execute a full or partial refund for a settled transaction

Example Prompts for Clip API in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Clip API immediately.

"Generate a new custom MXN payment link exactly for 450.50 referenced as invoice #X-99T."

"Refund the latest transaction specifically identified as Txn_88Z to its origin card fully."

"Calculate my comprehensive real cash balance available anticipating the incoming bulk settlements today blindly."

Troubleshooting Clip API MCP Server with Google ADK

Common issues when connecting Clip API to Google ADK through the Vinkius, and how to resolve them.

McpToolset not found

Update: pip install --upgrade google-adk

Clip API + Google ADK FAQ

Common questions about integrating Clip API MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.