How to integrate JoggAI MCP with LlamaIndex

This guide walks you through connecting JoggAI to LlamaIndex using the Composio tool router. By the end, you'll have a working JoggAI agent that can generate your scripts, animate avatars, create product videos, sync lips to audio, and manage webhooks through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a JoggAI account through Composio's JoggAI MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

JoggAI logoJoggAI
Api Key

JoggAI is an AI video creation platform for avatar, product, lip-sync, template, and translated videos. It helps teams turn scripts, products, and media assets into polished videos through APIs.

36 Tools

Introduction

This guide walks you through connecting JoggAI to LlamaIndex using the Composio tool router. By the end, you'll have a working JoggAI agent that can generate your scripts, animate avatars, create product videos, sync lips to audio, and manage webhooks through natural language commands.

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

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

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

The JoggAI MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your JoggAI account. It provides structured and secure access to your avatars, products, videos, templates, scripts, and supporting media assets, so your agent can create videos, generate avatars, translate content, track production tasks, and manage webhooks on your behalf.

  • Avatar and lip-sync video creation: Have your agent create talking-avatar and lip-sync videos, generate photo or product avatars, and animate selected avatar images with speech and motion.
  • Product video production: Let the agent create or update product details, generate scripts and visual previews, then render selected concepts into finished product videos.
  • Template-based video rendering: Direct your agent to produce videos from JoggAI templates using text, scripts, images, videos, avatars, voices, captions, and music.
  • Video translation and dubbing: Instruct your agent to find supported languages and translate videos with options for dubbing, lip sync, subtitles, audio-only output, and adjusted duration.
  • Media tracking and notifications: Have your agent check video and avatar generation progress, browse available voices, music, templates, and visual styles, review account credits, and manage webhook notifications.

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

Getting API Keys for OpenAI, Composio, and JoggAI

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 JoggAI 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 joggai_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: ["jogg_ai"],
    },
  );

  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 JoggAI 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, joggai)
  • 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 JoggAI 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 JoggAI
  • 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 JoggAI 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 JoggAI
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with JoggAI 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: ["jogg_ai"],
    },
  );

  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 JoggAI 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 JoggAI to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes JoggAI 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 JoggAI action and event your agent gets out of the box.

Animate Photo Avatar

Create a reusable animated avatar from a photo-avatar image.

Animate Product Avatar

Add motion and a voice to a selected JoggAI product-avatar image generation.

Create Asset Upload URL

Create a signed URL for uploading an asset to JoggAI.

Create Lip Sync Video

Start an asynchronous lip-sync video from publicly reachable video and audio URLs.

Create Product

Create product information from exactly one source: a product page URL, or manually supplied product details.

Create Product Video

Start a product video using a saved product and nested video, avatar, voice, audio, and script settings.

Create Product Video Previews

Generate product-video previews for one or more visual styles.

Create Talking Avatar Video

Start a talking-avatar video using an avatar and either a text script or hosted audio.

Create Template Video

Start rendering a JoggAI v2 template with typed text, script, image, or video variables and optional avatar, voice, captions, and music settings.

Create Webhook

Create a JoggAI webhook endpoint with a callback URL, delivery status, and event subscriptions.

Delete Webhook

Permanently delete one JoggAI webhook endpoint.

Generate AI Scripts

Start asynchronous AI script generation from a saved product or inline product details.

Generate Photo Avatar Image

Start AI photo-avatar image generation using JoggAI's exact demographic, style, model, and aspect-ratio modes.

Generate Product Avatar Images

Start asynchronous generation of one to four product-avatar images from a public product image and an existing avatar, reference image, or description.

Get Account and Credit Balance

Return the connected JoggAI user and remaining credit balance.

Get AI Script Task

Check an AI script generation task and return generated scripts when completed.

Get Lip Sync Video

Check a lip-sync task and return its output URLs and duration when successful.

Get Photo Avatar

Check photo-avatar motion generation and return the reusable avatar details when complete.

Get Photo Avatar Image

Check photo-avatar image generation and return the generated image URLs and keys when ready.

Get Product Avatar

Check product-avatar motion generation and return the reusable avatar when complete.

Get Product Avatar Image Task

Check a product-avatar image generation batch and return its status summary and generated image candidates.

Get Product Video

Check one product video and return its generated media when available.

Get Talking Avatar Video

Check a talking-avatar video and return its media URLs when completed.

Get Template Video

Check a template-rendered video and return its output details when complete.

Get Video Translation

Check a video translation and return translated media when complete.

List Avatars

List public, instant, photo, or product avatars available for JoggAI video generation.

List Creation Assets

Browse one music, template, visual-style, or voice catalog used to create JoggAI media.

List Product Previews

List generated JoggAI product-video previews and their statuses one page at a time.

List Product Videos

List product videos with status and sort filters, one bounded page at a time.

List Translation Languages

Return currently supported lowercase target-language identifiers for JoggAI video translation.

List Webhook Events

Return event identifiers that can be subscribed to by a JoggAI webhook.

List Webhooks

List webhook endpoints registered on the connected JoggAI account.

Render Product Video Preview

Render one selected product preview into a final video.

Translate Video

Start asynchronous video translation with optional audio-only translation, dubbing, lip sync, subtitles, and dynamic duration.

Update Product

Update an existing JoggAI product's descriptive fields.

Update Webhook

Fully replace an existing JoggAI webhook's callback URL, delivery status, and event subscriptions.

FAQ

Frequently asked questions

With a standalone JoggAI MCP server, the agents and LLMs can only access a fixed set of JoggAI tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from JoggAI 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 JoggAI tools.

Yes, absolutely. You can configure which JoggAI 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 JoggAI data and credentials are handled as safely as possible.

Start with JoggAI.It takes 30 seconds.

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

Start building