How do I get an OnPay API Token?

Log in to your OnPay management panel, and navigate to Settings > API to generate a static API token.

OnPay MCP Server for Google ADK 8 tools — connect in under 2 minutes

Name: OnPay
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 8 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add OnPay as an MCP tool provider through 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="onpay_agent",
    instruction=(
        "You help users interact with OnPay "
        "using 8 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 OnPay MCP Server

Connect your OnPay account to empower your AI agents with payroll and HR capabilities. This server provides programmatic access to the OnPay API, allowing for seamless management of employee profiles, payment transactions, and recurring pay schedules.

Google ADK natively supports OnPay as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 8 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

Employee Directory — List and inspect complete employee profiles and records
Transaction Monitoring — Access historical payment transactions and statuses in real-time
Payroll Orchestration — Monitor upcoming pay schedules and cycles for your company
Subscription Tracking — View active and past subscriptions managed through the platform
Accounting Integration — Retrieve item codes and company settings for financial reconciliation

The OnPay MCP Server exposes 8 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 OnPay to Google ADK via MCP

Follow these steps to integrate the OnPay 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 8 tools from OnPay via MCP

Why Use Google ADK with the OnPay MCP Server

Google ADK provides unique advantages when paired with OnPay 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 OnPay

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 OnPay tools with BigQuery, Vertex AI, and Cloud Functions

OnPay + Google ADK Use Cases

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

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

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

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

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

OnPay MCP Tools for Google ADK (8)

These 8 tools become available when you connect OnPay to Google ADK via MCP:

get_company_info

Get general company information

get_employee

Get employee details

get_transaction

Get transaction details

list_employees

List all employees

list_item_codes

List accounting item codes

list_pay_schedules

List payroll schedules

list_subscriptions

List subscriptions

list_transactions

List payment transactions

Example Prompts for OnPay in Google ADK

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

"List all active employees."

Troubleshooting OnPay MCP Server with Google ADK

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

McpToolset not found

Update: pip install --upgrade google-adk

OnPay + Google ADK FAQ

Common questions about integrating OnPay 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.