How to Use the PDFMonkey MCP in LlamaIndex

Q: How do I index PDFMonkey document metadata into a LlamaIndex vector store?

Use listgenerateddocuments to fetch the recent document list. Your pipeline then converts these JSON payloads into Document objects and indexes them.

Q: Can LlamaIndex search through my PDFMonkey templates?

Yes, it can. The agent calls listtemplates to get the list, then uses semantic retrieval to find the template that matches the user's intent.

Q: How does this MCP setup prevent LlamaIndex from hallucinating about my PDFMonkey files?

The agent queries live data using getpdfdetails before answering. This grounds every response in real document metadata rather than relying on LLM memory.

Q: Can I delete old documents directly through the query interface?

Yes, if you allow it. The agent can invoke deletegeneratedpdf when a user requests document removal during a chat session.

Index your PDFMonkey document metadata into LlamaIndex vector stores to search and query your generated files with live context.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect PDFMonkey MCP to LlamaIndex

Create your Vinkius account to connect PDFMonkey to LlamaIndex — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup PDFMonkey with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Indexing Generated Document Metadata

Your RAG pipeline can ingest live document lists by calling `list_generated_documents` and indexing the metadata into a vector store. This allows you to query your generated documents semantically instead of searching by strict database IDs. If you need to verify specific details, the LlamaIndex agent calls `get_pdf_details` to pull down the exact layout properties. The resulting text is then embedded, making your document generation history completely searchable.

Semantic Template Discovery via LlamaIndex MCP Server

Instead of hardcoding template IDs, let your LlamaIndex agent scan your template library using `list_templates` to retrieve all available layouts. The agent matches them against user queries using semantic search. Once the correct template is found, the agent uses `get_template` to verify the required JSON structure. This ensures your LlamaIndex application always selects the correct invoice or receipt layout based on the user's conversation.

Workspace Context Retrieval for RAG

Keep your vector index updated by querying workspace configurations dynamically with `list_workspaces` to gather active environments. The MCP server lets your agent feed this structural data directly into your query engine. When a user asks about document distribution across departments, LlamaIndex uses `get_workspace` to map documents to their respective business units. You get grounded answers based on actual workspace structures, not guesswork.

Setup guide

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

Use `list_generated_documents` to fetch the recent document list. Your pipeline then converts these JSON payloads into Document objects and indexes them.

Yes, it can. The agent calls `list_templates` to get the list, then uses semantic retrieval to find the template that matches the user's intent.

The agent queries live data using `get_pdf_details` before answering. This grounds every response in real document metadata rather than relying on LLM memory.

Yes, if you allow it. The agent can invoke `delete_generated_pdf` when a user requests document removal during a chat session.

Your workspace IDs and download URLs are processed in memory and never stored on external servers. The MCP integration ensures that sensitive document links are only handled during active query execution.

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