How to Use the Factorial MCP in LlamaIndex

Q: How do I connect the Factorial MCP Server to a LlamaIndex agent?

Install llama-index-tools-mcp and initialize the BasicMCPClient with the Vinkius endpoint. Pass the client to McpToolSpec and convert it to tools for your FunctionAgent using the MCP standard.

Q: Does LlamaIndex support live tool calling for Factorial shift tracking?

Absolutely. The FunctionAgent calls the shift tools directly to pull real-time attendance data instead of relying on cached index data.

Q: How do I restrict which Factorial tools LlamaIndex can access?

Use the allowedtools filter when configuring your tool specification. This lets you block specific tools like contract listing while keeping directory lookups active.

Index Factorial employee details and documents directly into LlamaIndex to build search engines for your HR data.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Factorial MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build semantic search over Factorial documents

The `list_hr_documents` tool extracts metadata from your company documents so LlamaIndex can index them for semantic search. Instead of clicking through folders, your agent queries the vector store to find specific policy files based on meaning rather than exact keywords. LlamaIndex pairs this live metadata with your vector database to ground agent responses in actual company records. This eliminates hallucinations when staff ask questions about internal guidelines.

Query live employee profiles using LlamaIndex RAG

The `get_employee_details` tool retrieves specific profile information and roles to populate your local LlamaIndex knowledge base via MCP. The agent uses this data to answer complex organizational queries, combining live API responses with indexed historical files. You filter which tools are exposed using the `allowed_tools` setting in the client. This ensures your search pipelines only access the profile fields you want to index.

Expose document structures to your LlamaIndex MCP Server

The `list_document_folders` tool maps out your entire HR folder hierarchy directly into LlamaIndex query engines. Your agent navigates this structure to locate files, ensuring it searches the correct directories during retrieval steps. By enabling resource access, LlamaIndex reads the folder structure dynamically. This keeps your search index updated without requiring constant manual re-indexing of the directory tree.

Setup guide

Set up Factorial 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 Factorial 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 Factorial tools.",
)
response = await agent.run("List recent Factorial 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 Factorial. 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 Factorial 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 Factorial MCP in LlamaIndex

Install `llama-index-tools-mcp` and initialize the `BasicMCPClient` with the Vinkius endpoint. Pass the client to `McpToolSpec` and convert it to tools for your `FunctionAgent` using the MCP standard.

Yes, you can fetch employee records and load them into a LlamaIndex document index. This allows you to run semantic queries over your team structure and roles.

Absolutely. The `FunctionAgent` calls the shift tools directly to pull real-time attendance data instead of relying on cached index data.

Use the `allowed_tools` filter when configuring your tool specification. This lets you block specific tools like contract listing while keeping directory lookups active.

All employee profiles and shift records stay within your private infrastructure. Vinkius uses ephemeral, zero-trust sandboxes to execute tool calls, meaning your HR data is never stored or cached on our platform.

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