How to Use the Dryfta MCP in LlamaIndex

Q: How do I index Dryfta event schedules using LlamaIndex?

You run listeventsessions to pull down the active Dryfta program, then pass those documents to your LlamaIndex vector index. This makes your Dryfta schedule searchable via natural LlamaIndex queries.

Q: Can LlamaIndex search Dryfta attendee records semantically?

Yes, by combining listeventattendees with a LlamaIndex indexer, you can search Dryfta participant profiles by concept. The LlamaIndex agent retrieves the matching vector node and displays the Dryfta details.

Q: How do I filter Dryfta abstracts before indexing them in LlamaIndex?

You can use the listsubmittedabstracts tool within your LlamaIndex pipeline to filter Dryfta submissions by status before indexing. This ensures only approved Dryfta papers enter your LlamaIndex vector store.

Index Dryfta event schedules and attendee profiles directly into LlamaIndex vector stores for RAG.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Dryfta MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Ground your LlamaIndex queries in Dryfta session data

The `list_event_sessions` tool pulls your active Dryfta schedule directly into your LlamaIndex RAG pipeline. LlamaIndex indexes these Dryfta workshops and speakers into vector nodes for semantic search. When users query your LlamaIndex agent about the event, it retrieves the exact Dryfta session details. This grounding prevents LlamaIndex from hallucinating Dryfta speaker times or workshop locations.

Build Dryfta attendee indexes via MCP Server tools

Your LlamaIndex pipeline uses `list_event_attendees` to build a searchable knowledge base of Dryfta registrants. LlamaIndex embeds these Dryfta profiles, allowing you to run semantic searches over Dryfta participant titles and companies. For deeper lookups, LlamaIndex calls `get_attendee_details` to verify a specific Dryfta user's registration status. This combines live Dryfta API lookups with your LlamaIndex vector database for real-time accuracy.

Index Dryfta abstracts for semantic LlamaIndex matching

The `list_submitted_abstracts` tool imports your Dryfta paper submissions directly into LlamaIndex. LlamaIndex indexes these Dryfta abstracts so Dryfta organizers can query for similar research topics using natural language. Using this MCP setup, your LlamaIndex agent can then compare incoming Dryfta abstracts against existing Dryfta sessions to find the best fit. This eliminates manual sorting by letting LlamaIndex match Dryfta submissions to scheduled Dryfta tracks automatically.

Setup guide

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

You run `list_event_sessions` to pull down the active Dryfta program, then pass those documents to your LlamaIndex vector index. This makes your Dryfta schedule searchable via natural LlamaIndex queries.

Yes, by combining `list_event_attendees` with a LlamaIndex indexer, you can search Dryfta participant profiles by concept. The LlamaIndex agent retrieves the matching vector node and displays the Dryfta details.

You can use the `list_submitted_abstracts` tool within your LlamaIndex pipeline to filter Dryfta submissions by status before indexing. This ensures only approved Dryfta papers enter your LlamaIndex vector store.

Yes, the MCP Server allows LlamaIndex to fetch batches of Dryfta registrants and feed them into your index. This lets you build a local LlamaIndex knowledge graph of your Dryfta event.

Your Dryfta abstract text and author details are processed by this MCP Server through an ephemeral sandbox that destroys the LlamaIndex runtime context immediately after execution. Your Dryfta papers and submission drafts are never cached.

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