2,500+ MCP servers ready to use
Vinkius

AfterShip MCP Server for LlamaIndex 9 tools — connect in under 2 minutes

Built by Vinkius GDPR 9 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add AfterShip as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to AfterShip. "
            "You have 9 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in AfterShip?"
    )
    print(response)

asyncio.run(main())
AfterShip
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About AfterShip MCP Server

Connect AfterShip tracking platform to any AI agent and track packages from 1,000+ couriers worldwide, auto-detect shipping companies, and manage all your shipments through natural language.

LlamaIndex agents combine AfterShip tool responses with indexed documents for comprehensive, grounded answers. Connect 9 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

What you can do

  • Package Tracking — Create and monitor shipments from FedEx, UPS, DHL, USPS, and 1,000+ other couriers
  • Auto-Detect Courier — Automatically identify the shipping company from just a tracking number
  • Tracking History — View complete delivery history with checkpoint timestamps and locations
  • Delivery Management — Mark trackings as completed, retrack expired ones, or delete old entries
  • Customer Notifications — Set up email and SMS notifications for delivery updates
  • Courier Directory — Browse all supported courier companies with their contact info and requirements

The AfterShip MCP Server exposes 9 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect AfterShip to LlamaIndex via MCP

Follow these steps to integrate the AfterShip MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 9 tools from AfterShip

Why Use LlamaIndex with the AfterShip MCP Server

LlamaIndex provides unique advantages when paired with AfterShip through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine AfterShip tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain AfterShip tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query AfterShip, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what AfterShip tools were called, what data was returned, and how it influenced the final answer

AfterShip + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the AfterShip MCP Server delivers measurable value.

01

Hybrid search: combine AfterShip real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query AfterShip to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying AfterShip for fresh data

04

Analytical workflows: chain AfterShip queries with LlamaIndex's data connectors to build multi-source analytical reports

AfterShip MCP Tools for LlamaIndex (9)

These 9 tools become available when you connect AfterShip to LlamaIndex via MCP:

01

create_tracking

Requires at least the tracking number. Optionally specify the courier slug, title, customer emails, SMS phone numbers, order ID, and custom fields. Create a new package tracking

02

delete_tracking

This action cannot be undone. Delete a tracking entry

03

detect_courier

Useful when the user provides a tracking number but doesn't know which courier it belongs to. Returns a ranked list of likely couriers. Auto-detect courier from tracking number

04

get_tracking

Get details of a specific tracking

05

list_couriers

) that can be used for tracking packages. List all supported courier companies

06

list_trackings

Supports extensive filtering by courier (slug), tag, keyword, origin, destination, date ranges, and delivery status. List all package trackings

07

mark_tracking_completed

Useful when the package has been delivered but the courier hasn't updated the final status. Mark a tracking as completed

08

retrack_tracking

This restarts monitoring and will fetch new checkpoint updates. Retrack an expired tracking

09

update_tracking

Does not affect the tracking number or courier. Update an existing tracking

Example Prompts for AfterShip in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with AfterShip immediately.

01

"Track my package with tracking number 1Z999AA10123456784."

02

"What courier handles tracking number 9400111899223344556677?"

03

"Show me all my active trackings."

Troubleshooting AfterShip MCP Server with LlamaIndex

Common issues when connecting AfterShip to LlamaIndex through the Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

AfterShip + LlamaIndex FAQ

Common questions about integrating AfterShip MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query AfterShip tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect AfterShip to LlamaIndex

Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.