How to integrate Imgix MCP with LlamaIndex

This guide walks you through connecting Imgix to LlamaIndex using the Composio tool router. By the end, you'll have a working Imgix agent that can auto-optimize all images in this folder, overlay company logo on product photos, extract main color palette from image through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Imgix account through Composio's Imgix MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Imgix logoImgix
Api Key

Imgix is a real-time image processing and delivery service for developers. It helps you optimize, transform, and deliver images efficiently at any scale.

53 Tools

Introduction

This guide walks you through connecting Imgix to LlamaIndex using the Composio tool router. By the end, you'll have a working Imgix agent that can auto-optimize all images in this folder, overlay company logo on product photos, extract main color palette from image through natural language commands.

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

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

Also integrate Imgix 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 Imgix
  • Connect LlamaIndex to the Imgix MCP server
  • Build a Imgix-powered agent using LlamaIndex
  • Interact with Imgix 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 Imgix MCP server, and what's possible with it?

The Imgix MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Imgix account. It provides structured and secure access to your image library, so your agent can perform actions like optimizing images, applying overlays, adjusting visual properties, and extracting color palettes on your behalf.

  • Real-time image optimization: Ask your agent to automatically compress, enhance, or format images for faster delivery and better quality using Imgix's auto optimization tools.
  • Dynamic overlays and blending: Direct the agent to blend images, text, or solid colors over your base images—perfect for watermarks, banners, or creative composites.
  • Precision image adjustments: Have your agent modify image brightness, contrast, and border settings to meet your design and branding needs instantly.
  • Extract and analyze color palettes: Let your agent pull color palettes from any image, making it easy to generate theme colors or analyze brand consistency.
  • Fine-tune overlay positioning: Control exactly where overlays appear on your images by specifying alignment and pixel-level positioning through your agent.

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

Step by step10 STEPS
1

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 Imgix account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Imgix

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
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

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 Imgix access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called imgix_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

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

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["imgix"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Imgix actions." ,
    llm,
    tools,
  });

  return agent;
}

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, imgix)
  • 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 Imgix tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Imgix
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Imgix tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

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 Imgix
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["imgix"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Imgix actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Imgix to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Imgix 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.
TOOLS

Supported Tools

Every Imgix action and event your agent gets out of the box.

IMGIX_ADD_ASSET_FROM_ORIGIN

Tool to queue a path from your origin to be added to the Asset Manager.

Imgix Auto Optimization

Apply automatic image optimizations using imgix's auto parameter.

Blend Overlay

Tool to overlay an image, text, or color onto a base image using imgix blending parameters.

Imgix Blend Align

Tool to align the overlay relative to the base image when blending.

Blend Color Over Image

Tool to blend a solid color over an image using CSS keyword or hex.

Imgix Blend X Position

Position an overlay image horizontally on a base image using imgix's blend-x parameter.

Draw Image Border

Tool to draw a border around an image.

Adjust Image Brightness

Tool to adjust image brightness.

IMGIX_CANCEL_UPLOAD_SESSION

Tool to cancel an Imgix Asset Manager upload session.

IMGIX_CH

Tool to opt in to Client Hints.

IMGIX_CLOSE_UPLOAD_SESSION

Tool to close an Imgix Asset Manager upload session after the client uploads to the presigned URL.

Adjust Image Contrast

Tool to adjust image contrast.

IMGIX_CREATE_IMGIX_SOURCE

Tool to create and deploy a new imgix Source.

IMGIX_CREATE_UPLOAD_SESSION

Tool to create an Imgix Asset Manager upload session and return a presigned URL for client-side upload.

IMGIX_CS

Tool to set or strip output color space/profile on an Imgix image.

IMGIX_DL

Download an asset from an Imgix source with optional custom filename.

Adjust Image DPI

Tool to embed DPI (dots-per-inch) metadata for print output on an Imgix-rendered image.

Set Device Pixel Ratio

Tool to set device pixel ratio for an Imgix image.

Imgix URL Expiration

Tool to append an expiration parameter to an Imgix URL so it returns 404 after a given time.

IMGIX_FIT

Tool to control how an image fits target dimensions after resizing.

IMGIX_FM

Tool to choose output file format for the rendered asset.

Force Aspect Ratio

Tool to force a target aspect ratio on an Imgix image.

IMGIX_GET_SOURCE

Tool to retrieve details for a single imgix Source by its ID.

IMGIX_GET_UPLOAD_SESSION_STATUS

Tool to retrieve the status of an Imgix Asset Manager upload session.

IMGIX_H

Tool to set output image height in pixels or as a ratio of the source height.

Adjust Image Highlights

Tool to adjust highlight tonal mapping (−100 to 0).

IMGIX_LIST_ASSETS

Tool to retrieve a paginated list of assets in an imgix Source.

IMGIX_LIST_REPORTS

Tool to retrieve a list of all available reports for your imgix account.

IMGIX_LIST_SOURCES

Tool to list all Sources for an account.

Set Watermark Base URL

Tool to set the base URL prepended to the watermark image path.

Watermark Fit Mode

Tool to set how a watermark fits its target dimensions.

Imgix Mark Height

Tool to set watermark height on an Imgix URL in pixels or as a ratio of the watermark source.

IMGIX_MARK_PAD

Tool to set pixel padding between a watermark and the image edge or between tiled watermarks.

Watermark Width

Tool to set watermark width.

IMGIX_MASK

Tool to apply a mask to an image.

IMGIX_MAX_H

Constrain the maximum height of an imgix image.

IMGIX_MAX_W

Tool to set the maximum output width on an Imgix URL.

IMGIX_PALETTE

Tool to extract a color palette from an image in CSS or JSON form.

Set CSS Palette Prefix

Tool to set class-name prefix for CSS palette output.

IMGIX_PURGE_ASSET

Tool to purge an asset from the imgix cache.

Set Output Quality

Tool to set output quality for lossy formats.

IMGIX_RECT

Tool to select a source-image rectangle region in Imgix before other resizing.

Imgix Rotate

Tool to rotate an image on Imgix.

IMGIX_ROT_TYPE

Tool to control rotation behavior when `rot` is applied.

Text Overlay

Tool to render a single-line UTF-8 text overlay on an image.

IMGIX_TXT_ALIGN

Tool to align a text overlay on an Imgix image.

Set Text Color

Tool to set text overlay color on an Imgix image.

Set Text Font

Tool to choose font family/style for overlay text.

Set Text Outline Width

Tool to set outline width around overlay text.

Text Outline Color

Apply an outline color to text overlays on Imgix images.

IMGIX_TXT_SHAD

Set text shadow strength for imgix text overlays.

IMGIX_TXT_SIZE

Tool to set text font size in pixels.

IMGIX_UPDATE_SOURCE

Tool to update an existing imgix Source.

FAQ

Frequently asked questions

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

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 Imgix tools.

Yes, absolutely. You can configure which Imgix 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.

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 Imgix data and credentials are handled as safely as possible.

Start with Imgix.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Imgix tool your agent needs.Free to start.

Start building