How to Use the ProcessOn MCP in LlamaIndex

Q: How do I load ProcessOn tools into LlamaIndex?

Install llama-index-tools-mcp. Set up a BasicMCPClient, wrap it in McpToolSpec, and pass the async tool list to your FunctionAgent.

Q: Can LlamaIndex search the text inside my ProcessOn flowcharts?

Not directly. The tools handle metadata like getfile and listfiles. You index the file details, not the visual canvas content.

Q: How do I export ProcessOn diagrams through the MCP Server in LlamaIndex?

The agent can trigger exportfile when a user requests a hard copy. You get a downloadable link right in the chat response.

Q: Can I filter which ProcessOn tools LlamaIndex sees?

Yes. Use the allowedtools parameter to restrict the agent. You might only want it using getrecentfiles and block destructive actions entirely.

Index your ProcessOn diagrams and collaborator lists into searchable vector stores using LlamaIndex.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect ProcessOn MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Index ProcessOn data

LlamaIndex turns your flowchart metadata into queryable knowledge. You run `list_files` to grab your entire ProcessOn inventory. The framework embeds those titles and descriptions into your vector store. Now your RAG pipeline knows exactly which diagrams exist without needing to hit the API a second time.

Query your workspace with the MCP Server

Finding the right mind map usually means clicking through endless folders. Instead, use `get_folder_content` to pull the raw directory data. LlamaIndex indexes that structure. When a user asks where the Q3 architecture diagram lives, the agent queries the index and returns the exact path using the cached `get_file` output.

Map your collaborators

You need to know who owns which flowchart. By combining `get_org_info` and `list_collaborators`, you extract the permission matrix. Feed that matrix into a LlamaIndex document. Your application can now answer semantic queries about team structure and diagram ownership instantly.

Setup guide

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

Install `llama-index-tools-mcp`. Set up a `BasicMCPClient`, wrap it in `McpToolSpec`, and pass the async tool list to your `FunctionAgent`.

Not directly. The tools handle metadata like `get_file` and `list_files`. You index the file details, not the visual canvas content.

The agent can trigger `export_file` when a user requests a hard copy. You get a downloadable link right in the chat response.

Yes. Use the `allowed_tools` parameter to restrict the agent. You might only want it using `get_recent_files` and block destructive actions entirely.

The MCP Server handles your organization IDs and folder structures. Vinkius runs this connection in an ephemeral, zero-trust environment, meaning no diagram metadata persists after the query finishes.

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