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 LlamaIndex 8 tools — connect in under 2 minutes

Name: OnPay
Availability: InStock
Author: Vinkius

docs.llamaindex.ai/en/stable/module_guides/tools/mcp

Built by Vinkius GDPR 8 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add OnPay as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

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

import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to OnPay. "
            "You have 8 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in OnPay?"
    )
    print(response)

asyncio.run(main())

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.

LlamaIndex agents combine OnPay tool responses with indexed documents for comprehensive, grounded answers. Connect 8 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

Follow these steps to integrate the OnPay MCP Server with LlamaIndex.

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.py and run: python agent.py

Explore tools

The agent discovers 8 tools from OnPay

Why Use LlamaIndex with the OnPay MCP Server

LlamaIndex provides unique advantages when paired with OnPay through the Model Context Protocol.

Data-first architecture: LlamaIndex agents combine OnPay tool responses with indexed documents for comprehensive, grounded answers

Query pipeline framework lets you chain OnPay tool calls with transformations, filters, and re-rankers in a typed pipeline

Multi-source reasoning: agents can query OnPay, a vector store, and a SQL database in a single turn and synthesize results

Observability integrations show exactly what OnPay tools were called, what data was returned, and how it influenced the final answer

OnPay + LlamaIndex Use Cases

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

Hybrid search: combine OnPay real-time data with embedded document indexes for answers that are both current and comprehensive

Data enrichment: query OnPay to augment indexed data with live information before generating user-facing responses

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying OnPay for fresh data

Analytical workflows: chain OnPay queries with LlamaIndex's data connectors to build multi-source analytical reports

OnPay MCP Tools for LlamaIndex (8)

These 8 tools become available when you connect OnPay to LlamaIndex 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 LlamaIndex

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

"List all active employees."

Troubleshooting OnPay MCP Server with LlamaIndex

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

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

OnPay + LlamaIndex FAQ

Common questions about integrating OnPay MCP Server with LlamaIndex.

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.