How to Use the KeyPay MCP in LlamaIndex

Q: How does LlamaIndex handle live updates from KeyPay?

Look, the agent uses getpayrundetails on a schedule to fetch the latest finalized runs. It updates the vector index incrementally, keeping your search results fresh without re-indexing the entire history.

Q: Does this support filtering tools before indexing?

Yes, you can pass an allowedtools filter to the MCP client. This prevents your agent from accessing sensitive endpoints like listpayslips while indexing public business metadata.

Index payroll runs and employee records directly into LlamaIndex using this KeyPay MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect KeyPay MCP to LlamaIndex

Create your Vinkius account to connect KeyPay to LlamaIndex 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 KeyPay with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Semantic search over historical pay runs

Your RAG pipeline indexes outputs from `list_pay_runs` and `list_pay_run_earnings` to allow natural language queries over past payroll cycles. The agent fetches the raw run details, structures the text, and feeds it to your index. LlamaIndex converts these payroll records into searchable vector embeddings. Instead of writing SQL queries, you ask your agent about specific historical compensation trends and get answers backed by raw payroll data.

Context-aware employee record indexing

Building a searchable workforce directory starts with fetching records via `list_employees` and `get_employee_details`. The agent pulls the complete workforce roster and indexes each profile's metadata. This setup uses the MCP tool specification to load live employee profiles directly into your query engine. Your agent retrieves the exact profile details during customer support sessions, resolving internal queries without manual database searches.

Semantic analysis of MCP Server leave balances

Analyzing time-off trends requires pulling data from `list_leave_requests` and `list_pay_slips` across multiple periods. The agent extracts the leave status and maps it to historical pay records. By indexing these outputs into a LlamaIndex document store, you build a queryable interface for HR policy audits. Your agent scans the indexed leave records to identify patterns, ensuring compliance with local labor rules.

Setup guide

Set up KeyPay MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all KeyPay MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

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

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to KeyPay tools.",
)
response = await agent.run("List recent KeyPay data")

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 KeyPay. 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 KeyPay 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 KeyPay MCP in LlamaIndex

You use the llama-index-tools-mcp package to load the tools into an McpToolSpec. From there, your agent calls list_pay_runs and indexes the returned JSON documents into a vector store.

Yes, you can query your vector index to find specific workers after loading their details via list_employees. LlamaIndex retrieves the relevant profile context to ground the agent's response.

Look, the agent uses get_pay_run_details on a schedule to fetch the latest finalized runs. It updates the vector index incrementally, keeping your search results fresh without re-indexing the entire history.

Yes, you can pass an allowed_tools filter to the MCP client. This prevents your agent from accessing sensitive endpoints like list_pay_slips while indexing public business metadata.

All payroll earnings, deductions, and tax files are processed in-memory within an isolated, stateless environment. Vinkius handles the API handshake securely, ensuring your credentials never leak into the LLM context or vector store.

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