How to Use the Geocode.xyz MCP in LlamaIndex

Q: Can I filter which Geocode.xyz tools LlamaIndex sees?

Yes. Use the allowedtools filter when defining your tool list. This limits the agent to only the specific location functions you need.

Q: Does LlamaIndex support async calls to the Geocode.xyz MCP server?

It does. You use totoollistasync to fetch your tools, ensuring your indexing process doesn't block the event loop.

Index location data from Geocode.xyz directly into your LlamaIndex knowledge base.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Geocode.xyz MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Ground LlamaIndex queries in real-world locations

Run `reverse_geocode` to turn coordinates into human-readable addresses. LlamaIndex then stores these results as searchable nodes in your vector store. This lets you query your historical location data later. You get answers based on actual API results instead of LLM guesses.

Automate address parsing with LlamaIndex

The `geoparse` tool acts as a pre-processor for your documents. You push unstructured text through the tool, then index the output to ensure your data is clean. Your RAG pipeline stays consistent. It's the best way to keep location-heavy data searchable.

Index IP metadata for LlamaIndex agents

Use `ip_geolocation` to tag incoming documents with regional metadata. LlamaIndex stores these tags to improve the relevance of your semantic searches. Your agent retrieves context that matches the user's physical location. It’s a clean way to ground your retrieval process.

Setup guide

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

The McpToolSpec converts API outputs into a format your indexer understands. You simply pass the tool list to your agent and define the ingestion pipeline.

Yes. Use the allowed_tools filter when defining your tool list. This limits the agent to only the specific location functions you need.

Once you index the tool output into your vector store, it remains available for future queries. You aren't just getting a one-time answer.

It does. You use `to_tool_list_async` to fetch your tools, ensuring your indexing process doesn't block the event loop.

The server transmits your coordinates over an encrypted channel. Your indexer only stores the final result, keeping your raw API request logs separate.

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