How to integrate Short io MCP with LlamaIndex

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Short io logo
LlamaIndex logo
divider

Introduction

This guide walks you through connecting Short io to LlamaIndex using the Composio tool router. By the end, you'll have a working Short io agent that can show click stats for your latest short links, list most popular short urls this month, get opengraph settings for a specific link through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Short io account through Composio's Short io MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Short io with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Short io
  • Connect LlamaIndex to the Short io MCP server
  • Build a Short io-powered agent using LlamaIndex
  • Interact with Short io through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

What is the Short io MCP server, and what's possible with it?

The Short io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Short io account. It provides structured and secure access to your branded short links, so your agent can create and manage links, retrieve analytics, organize domains, and optimize your link campaigns automatically.

  • Automated branded link creation and management: Instantly generate new short links, fetch details, update metadata, and organize your links by domain—all on demand.
  • Comprehensive click analytics and statistics: Retrieve detailed click metrics for individual links or aggregated data by domain to track performance and measure engagement.
  • Popular path and traffic insights: Analyze the most visited short link paths in your domains over time to understand which content resonates with your audience.
  • Granular permissions and access control: Check and manage user permissions on links within your domains, ensuring secure collaboration and streamlined workflows.
  • Open Graph and targeting customization: Review and adjust Open Graph properties for better link previews and set up advanced targeting rules by region or country to maximize reach.

Supported Tools & Triggers

Tools
Add Tag to Links in BulkTool to append a single tag to multiple short links in one call.
Archive LinkArchive a short link, hiding it from the dashboard while keeping it accessible.
Create FolderTool to create a new folder for organizing links within a domain.
Create Short LinkTool to create a new short link from a long URL on your branded domain.
Delete LinkTool to permanently delete a short link by its unique ID.
Delete Link PermissionRevokes a specific user's access permission for a short link.
Delete Links in BulkDelete multiple short links in a single API call (up to 150 links).
Duplicate LinkTool to duplicate an existing short link by its ID.
Generate QR Code for LinkTool to generate a QR code for a short link.
Get Bundle TemplatesTool to retrieve all available bundle templates.
Get Domain Details by IDTool to retrieve detailed information for a specific domain by its ID.
Get Domain Link ClicksTool to get click statistics for specific links in a domain.
Get Domain PathsTool to list the most popular paths in a domain over time.
Get Domain StatisticsTool to get comprehensive statistics for a domain over a specified period.
Get FolderTool to retrieve folder details by ID.
Get Link by Original URLTool to get link info by original URL.
Get Link CountriesTool to get country targeting rules for a short link.
Get Link Info by Link IDRetrieves comprehensive metadata for a short link using its unique ID.
Get Link Info by PathTool to get link info by its path and domain.
Get Link OpenGraph PropertiesTool to retrieve OpenGraph settings for a link.
Get Link PermissionsRetrieves all user access permissions for a specific short link within a domain.
Get Link Regions by CountryTool to list all regions available for a country.
Get Link RegionsRetrieves all region-based targeting rules configured for a specific short link.
Get Links by Original URLTool to get multiple links info by original URL.
Get Links ListTool to list short links on a domain with optional filters.
Get Link StatisticsTool to get click statistics for a specific link.
Get Link (Tweetbot)Create a short link using the simplified Tweetbot GET endpoint.
List DomainsTool to retrieve all domains associated with the Short.
List FoldersTool to list all folders for a specific domain.
Post Domain Link ClicksTool to get click statistics for specific links in a domain using POST method.
Get Domain Statistics by IntervalTool to retrieve domain statistics over a custom interval.
Post Domains Last ClicksTool to retrieve the latest raw click events for a domain.
Get Domain StatisticsTool to get detailed statistics for a domain over a specified period.
Get Domain Top ValuesRetrieves top values for a specified analytics column ranked by click count for a domain.
Archive Links in BulkArchive multiple short links in a single API call (up to 150 links).
Create Links in BulkTool to create up to 1000 short links in one call.
Generate QR Codes in BulkTool to generate QR codes for multiple links in bulk.
Unarchive Links in BulkUnarchive multiple short links in bulk (up to 150 links per request).
Unarchive LinkUnarchive a previously archived short link to restore it to active status.
Update Domain SettingsTool to update domain settings for a Short.
Update LinkTool to update an existing short link by its ID.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Short io account and project
  • Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Short io

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

  • composio-llamaindex: Composio's LlamaIndex integration
  • llama-index: Core LlamaIndex framework
  • llama-index-llms-openai: OpenAI LLM integration
  • llama-index-tools-mcp: MCP client for LlamaIndex
  • python-dotenv: Environment variable management

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Short io access

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

Create a new file called short io_llamaindex_agent.py and import the required modules:

Key imports:

  • asyncio: For async/await support
  • Composio: Main client for Composio services
  • LlamaIndexProvider: Adapts Composio tools for LlamaIndex
  • ReActAgent: LlamaIndex's reasoning and action agent
  • BasicMCPClient: Connects to MCP endpoints
  • McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set in the environment")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment")

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["short_io"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Short io actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Short io actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, short io)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Short io tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

  • We're creating a direct terminal interface to chat with your Short io database
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Short io

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Short io, then start asking questions.

Complete Code

Here's the complete code to get you started with Short io and LlamaIndex:

import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["short_io"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Short io actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Short io actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

Conclusion

You've successfully connected Short io to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Short io tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

How to build Short io MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Short io MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Short io MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Short io MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Short io MCP with Claude Cowork

Codex logo

Codex

Use Short io MCP with Codex

OpenClaw logo

OpenClaw

Use Short io MCP with OpenClaw

Hermes logo

Hermes

Use Short io MCP with Hermes

CLI logo

CLI

Use Short io MCP with CLI

Google ADK logo

Google ADK

Use Short io MCP with Google ADK

LangChain logo

LangChain

Use Short io MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Short io MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Short io MCP with Mastra AI

CrewAI logo

CrewAI

Use Short io MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Short io MCP?

With a standalone Short io MCP server, the agents and LLMs can only access a fixed set of Short io tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Short io and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with LlamaIndex?

Yes, you can. LlamaIndex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Short io tools.

Can I manage the permissions and scopes for Short io while using Tool Router?

Yes, absolutely. You can configure which Short io scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Short io data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗