How to Use the Make (Workflow Automation) MCP in LlamaIndex

Q: How do I index my Make (Workflow Automation) scenarios into LlamaIndex?

Use llama-index-tools-mcp to connect to the MCP Server, then load the output of listscenarios into your document store.

Q: Can LlamaIndex search through Make (Workflow Automation) execution logs?

Yes. The agent calls listscenariologs to retrieve recent events, indexes them as text nodes, and runs semantic search over them.

Q: How do I fetch scenario details using this integration?

The agent invokes getscenario with the target scenario ID, formatting the response as a clean text node for your index.

Q: Where does my Make scenario configuration data go during MCP indexing?

All configuration data pulled via getscenario is processed in memory inside our secure, zero-trust sandbox. It is never stored on Vinkius infrastructure, passing directly to your local LlamaIndex vector store.

Index your Make scenarios and execution logs into LlamaIndex vector stores for instant semantic search.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Make (Workflow Automation) MCP to LlamaIndex

Create your Vinkius account to connect Make (Workflow Automation) 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 Make (Workflow Automation) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build a searchable index of your MCP Server metadata

This MCP Server allows LlamaIndex to take raw outputs from `list_scenarios` and `list_data_stores` and converts them into searchable document nodes. Your agent queries this vector index to find which scenarios interact with specific databases without reading JSON files. Because the tool output is indexed, you avoid hallucinated configurations. Your queries about active data pipelines are grounded in live schema data retrieved directly from your active integrations.

Ground LlamaIndex queries in live execution logs

By indexing the output of `list_scenario_logs`, your LlamaIndex RAG application can answer complex troubleshooting questions. The agent searches past execution errors to find patterns in why specific automated tasks are failing. This turns raw, messy log files into structured knowledge. Instead of manually parsing stack traces, you ask the agent why a workflow failed, and it pulls the exact log context.

Map organizations and teams semantically

Your agent uses this MCP Server to query `list_organizations` and `list_teams` to understand how your workspace is structured. LlamaIndex stores this hierarchy as a semantic map, making it easy to check who owns which automated pipeline. When you ask which team manages a specific integration, the agent searches the indexed team structures. It verifies ownership by cross-referencing team lists with `get_scenario` outputs.

Setup guide

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

Use `llama-index-tools-mcp` to connect to the MCP Server, then load the output of `list_scenarios` into your document store.

Yes. The agent calls `list_scenario_logs` to retrieve recent events, indexes them as text nodes, and runs semantic search over them.

You can filter your vector index by metadata extracted from `list_data_stores` to target specific storage configurations.

The agent invokes `get_scenario` with the target scenario ID, formatting the response as a clean text node for your index.

All configuration data pulled via `get_scenario` is processed in memory inside our secure, zero-trust sandbox. It is never stored on Vinkius infrastructure, passing directly to your local LlamaIndex 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