How to Use the Lit Protocol (Decentralized Access Control) MCP in LlamaIndex

Q: Can I use natural language to query my Lit Protocol (Decentralized Access Control) groups in LlamaIndex?

Yes, once the agent indexes the output of listgroups and listapikeys, you can query the system in plain English. The LlamaIndex agent searches the vector database to identify which PKPs belong to which security boundaries.

Q: How do I restrict which MCP tools the LlamaIndex agent can access?

You pass an allowedtools list to your McpToolSpec instance to restrict the agent's capabilities. This prevents the agent from running destructive tools like removegroup while still allowing it to query active cryptographic configurations.

Q: What happens when my LlamaIndex agent executes a Lit Action?

The agent calls executelitaction with either an IPFS ID or raw JS code to perform secure calculations. The enclave executes the code, and the verified result is returned to LlamaIndex to update your active index.

Q: How is my billing data and API key configuration secured?

All billing details retrieved via getbillingbalance and API permissions managed by updateusageapikey are processed within Vinkius's secure sandbox, meaning the MCP Server never exposes raw configuration parameters to the LlamaIndex client.

Index decentralized access policies and query PKP metadata directly within your LlamaIndex RAG pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Lit Protocol (Decentralized Access Control) MCP to LlamaIndex

Create your Vinkius account to connect Lit Protocol (Decentralized Access Control) 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 Lit Protocol (Decentralized Access Control) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Semantic Indexing of Decentralized Wallets

`list_wallets` pulls all Programmable Key Pairs (PKPs) associated with your account so LlamaIndex can index their metadata into a searchable vector store. This tool exposes cryptographic identity lists that your agent can query semantically. Instead of hardcoding wallet addresses, your agent searches the indexed vector database to find the correct PKP for a specific transaction. This grounds your agentic workflows in real-time blockchain identity data rather than static, outdated files.

Queryable Access Control Groups via MCP Server

`list_groups` retrieves the active decentralized access control configurations to feed them directly into your LlamaIndex knowledge base. This MCP Server tool allows your agent to perform semantic searches over active security structures. The agent uses `list_actions` to match IPFS-hosted code with corresponding security groups dynamically. This setup lets your RAG pipeline answer complex natural language questions about who has access to what, using live cryptographic data.

Immutable TEE Execution Grounding

`execute_lit_action` runs secure, decentralized logic and returns verified outputs that LlamaIndex instantly parses and indexes. This tool guarantees that the data entering your knowledge base has been processed inside a secure enclave. Your agent uses these verified outputs to ground its responses, preventing hallucinated data from corrupting your RAG applications. This ensures every piece of synthesized information traces back to a cryptographically proven computation.

Setup guide

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

You initialize the BasicMCPClient and wrap it using McpToolSpec to extract the tool list. Your LlamaIndex agent calls list_groups and list_wallets, then indexes the returned JSON objects directly into your vector store.

Yes, once the agent indexes the output of list_groups and list_api_keys, you can query the system in plain English. The LlamaIndex agent searches the vector database to identify which PKPs belong to which security boundaries.

You pass an allowed_tools list to your McpToolSpec instance to restrict the agent's capabilities. This prevents the agent from running destructive tools like remove_group while still allowing it to query active cryptographic configurations.

The agent calls execute_lit_action with either an IPFS ID or raw JS code to perform secure calculations. The enclave executes the code, and the verified result is returned to LlamaIndex to update your active index.

All billing details retrieved via get_billing_balance and API permissions managed by update_usage_api_key are processed within Vinkius's secure sandbox, meaning the MCP Server never exposes raw configuration parameters to the LlamaIndex client.

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