How to Use the Culinary Unit Converter MCP in LlamaIndex

Q: How can I use the Culinary Unit Converter to create a RAG application in LlamaIndex?

Instantiate the McpToolSpec with your client details, then call totoollistasync() to get the tools. Pass these tools to your FunctionAgent to use them in a knowledge-augmented generation pipeline.

Q: Can I filter which tools from this MCP are available to my LlamaIndex agent?

Yes, the McpToolSpec supports an allowedtools filter. You can give your agent access to only convertvolume, for instance, if you don't want it performing mass estimations.

Index your recipe conversions with LlamaIndex and build a searchable culinary knowledge base.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Culinary Unit Converter MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Turn Conversions into Knowledge

Don't just run a one-off conversion. Use LlamaIndex to call tools from this MCP and automatically index the results. Convert from ounces to tablespoons with `convert_volume`, and that data point becomes part of a queryable knowledge graph. Next time you ask a similar question, your agent pulls the answer from its indexed memory. It's faster and grounded in real data from past tool calls, not a fresh, potentially wrong calculation.

Query Your Kitchen's History with LlamaIndex

Build a RAG pipeline that combines your personal recipe notes with live tool outputs. Your agent can use `estimate_mass` to figure out the approximate weight of '2 cups of packed brown sugar'. That result is indexed. Later, you can ask, 'What was the estimated weight for brown sugar in my cookie recipe?' Your LlamaIndex agent finds the exact answer from its knowledge base. It's like having a perfect memory for your kitchen experiments.

Build an Ingredient Encyclopedia

Sometimes the unit itself is the confusing part. Your agent can use `get_unit_details` to fetch context on obscure measurements, like a 'jigger' or a 'dash,' and add that information to its index. This process builds a rich, internal encyclopedia for your agent. It's not just converting numbers; the agent is learning the language of the kitchen. This MCP Server provides the raw data for that knowledge base.

Setup guide

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

Instantiate the `McpToolSpec` with your client details, then call `to_tool_list_async()` to get the tools. Pass these tools to your `FunctionAgent` to use them in a knowledge-augmented generation pipeline.

The MCP itself is stateless, but LlamaIndex is designed to remember. By indexing the tool outputs, you create a knowledge base of every conversion your agent performs, which it can then query for future tasks.

It indexes the inputs and outputs of the tool calls. For example, if you convert '2 cups' to '1 pint', LlamaIndex can store that relationship. This makes your agent's knowledge base specific to your actual usage.

Yes, the `McpToolSpec` supports an `allowed_tools` filter. You can give your agent access to only `convert_volume`, for instance, if you don't want it performing mass estimations.

Your conversion queries, which include ingredient names and quantities, are sent to the MCP for processing. Vinkius doesn't log or retain this data beyond the immediate transaction. Your LlamaIndex application is what stores the results in your own vector database.

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