How to Use the Alpic MCP in LlamaIndex

Q: How do I register Alpic tools in LlamaIndex?

Install llama-index-tools-mcp and initialize the BasicMCPClient. Wrap it in McpToolSpec and convert it to a tool list to pass to your agent.

Q: Can LlamaIndex query my Alpic project analytics?

Yes. The agent calls getprojectanalytics to fetch raw usage metrics, then indexes this data to generate performance reports or alert you to traffic spikes.

Q: What is the purpose of the tunnel ticket tool?

Calling gettunnelticket creates a secure local tunnel. This lets you debug your server locally while still allowing your cloud-hosted LlamaIndex agent to interact with it.

Index your Alpic MCP server configurations and deployment logs directly into your LlamaIndex vector store.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Alpic MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Semantic search over server configurations

`list_projects` retrieves your entire infrastructure setup so LlamaIndex can index your project metadata. The agent parses this data to answer questions about active deployments and team structures. By feeding this output into a vector store, your agent avoids making repetitive API calls. It queries the local index first to find the right project ID for subsequent tasks.

Index Alpic deployment logs in LlamaIndex

`get_deployment_logs` pulls build and runtime outputs directly into your RAG pipeline. If a deployment fails, LlamaIndex indexes these logs to let your agent search for recurring error patterns. This turns raw text files into searchable nodes. Your agent quickly matches new build failures against historical logs to find the exact root cause.

Audit variables and project states

`list_variables` exposes active configuration keys without revealing the actual masked values. Your agent indexes these keys to verify which environments have the correct setup. When configuration gaps are found, the agent uses `add_variable` to patch the missing keys. This ensures your staging and production environments stay perfectly aligned.

Setup guide

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

Install `llama-index-tools-mcp` and initialize the `BasicMCPClient`. Wrap it in `McpToolSpec` and convert it to a tool list to pass to your agent.

Yes. The agent calls `get_project_analytics` to fetch raw usage metrics, then indexes this data to generate performance reports or alert you to traffic spikes.

The agent uses semantic search to match user queries to the correct tool, like `list_environments`. It only invokes the tool when it needs fresh, real-time configuration data.

Calling `get_tunnel_ticket` creates a secure local tunnel. This lets you debug your server locally while still allowing your cloud-hosted LlamaIndex agent to interact with it.

We store your project settings, environment details, and team configurations in isolated, zero-trust databases. Only authorized agent tokens can query this metadata, and values are never shared or used for model training.

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