How to Use the IPGeolocation (IP Intelligence & Time) MCP in LlamaIndex

Q: Can LlamaIndex filter tools from the IPGeolocation (IP Intelligence & Time) server?

Yes, you can use the allowedtools filter when initializing your tool spec. This lets you restrict your agent to just the timezone tool if you do not need coordinate lookups.

Index real-world IP, timezone, and astronomy data directly into your LlamaIndex vector store for contextual RAG queries.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect IPGeolocation (IP Intelligence & Time) MCP to LlamaIndex

Create your Vinkius account to connect IPGeolocation (IP Intelligence & Time) 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 IPGeolocation (IP Intelligence & Time) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build a searchable location history

`get_location` extracts geographical coordinates and ISP data from incoming IP addresses to build a localized knowledge base. LlamaIndex indexes these results directly into your vector store so your agent can query past user locations semantically. This setup turns transient network data into a queryable resource. You avoid redundant API calls by searching your indexed database for previously resolved IP blocks first.

Ground agent responses in local time

`get_timezone` resolves the current local time and offset for any IP, feeding this temporal context directly into your index. Your LlamaIndex RAG application uses this data to ground its answers, preventing the agent from hallucinating outdated schedules. The tool integrates with the MCP tool spec to expose timezone lookups during retrieval steps. This keeps your agent synchronized with the user's actual wall-clock time during complex QA sessions.

Query local astronomical events

`get_astronomy` fetches sunrise and sunset times based on resolved IP coordinates to add environmental context to your index. LlamaIndex treats this astronomical data as metadata for document filtering or direct agent queries. Your agent accesses these solar schedules using the standard tool-calling interface. By combining this MCP server with your existing vector store, you build applications that understand both digital files and physical cycles.

Setup guide

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

Use the llama-index-tools-mcp package to wrap this MCP Server as a tool spec. The tool outputs are then converted into document nodes that can be indexed directly into your vector store.

Yes, you can use the allowed_tools filter when initializing your tool spec. This lets you restrict your agent to just the timezone tool if you do not need coordinate lookups.

It provides hard, verifiable network and time data instead of relying on the LLM's internal weights. The agent queries the server directly, ensuring the timezone and location details are accurate to the second.

Yes, LlamaIndex supports async tool calling for this server. You can call the async tool list method to run multiple IP lookups in parallel without blocking your main application loop.

All IP addresses sent to this MCP Server are processed within an ephemeral, zero-trust sandbox. No lookup history or network identifiers are written to disk, ensuring complete data isolation for your users.

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