# How to integrate Templated MCP with LlamaIndex

```json
{
  "title": "How to integrate Templated MCP with LlamaIndex",
  "toolkit": "Templated",
  "toolkit_slug": "templated",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/templated/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/templated/framework/llama-index.md",
  "updated_at": "2026-05-12T10:28:08.798Z"
}
```

## Introduction

This guide walks you through connecting Templated to LlamaIndex using the Composio tool router. By the end, you'll have a working Templated agent that can generate invoice pdf from customer data, list all available image templates, clone existing certificate template for edits through natural language commands.
This guide will help you understand how to give your LlamaIndex agent real control over a Templated account through Composio's Templated MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Templated with

- [OpenAI Agents SDK](https://composio.dev/toolkits/templated/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/templated/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/templated/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/templated/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/templated/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/templated/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/templated/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/templated/framework/cli)
- [Google ADK](https://composio.dev/toolkits/templated/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/templated/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/templated/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/templated/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/templated/framework/crew-ai)

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

The Templated MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Templated account. It provides structured and secure access to your templates and renders, so your agent can generate dynamic documents, manage templates, clone or tag designs, and retrieve render results on your behalf.
- Automated document and image generation: Instantly have your agent render PDFs or images from any saved template, filling in dynamic variables to create invoices, certificates, or marketing materials.
- Template management and organization: Let your agent list, retrieve, clone, or delete templates, keeping your template library organized and up-to-date without manual effort.
- Dynamic tagging and categorization: Easily add or remove tags from templates, enabling smarter organization and fast searching for specific designs or document types.
- Render tracking and retrieval: Ask your agent to list all renders for a template or fetch detailed information about a specific document render, making it simple to track document creation and usage history.
- Account insights and validation: Have your agent retrieve account information to confirm API access, check account metadata, or audit usage details as needed.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `TEMPLATED_ADD_TAGS_TO_TEMPLATE` | Add Tags to Template | Tool to append new tags to an existing template without overwriting existing tags. Use when you already have the template ID and want to add additional tags. |
| `TEMPLATED_CLONE_TEMPLATE_ACTION` | Clone Template | Tool to clone an existing template. Use after you have a template ID and want to duplicate it with a new name. Example: "Clone template tpl_123 as 'Copy of Template'". |
| `TEMPLATED_COUNT_TEMPLATE_CLONES` | Count Template Clones | Tool to get the count of cloned templates for a specific source template. Use when you need to know how many clones exist for a particular template without retrieving the full list. |
| `TEMPLATED_CREATE_FOLDER` | Create Folder | Tool to create a new folder for organizing templates and renders. Use when you need to organize templates into logical groups. |
| `TEMPLATED_CREATE_RENDER` | Create Template Render | Create document renders from templates. Supports single/batch rendering with extensive customization. Returns a list of render objects (one per page for multi-page templates). |
| `TEMPLATED_CREATE_TEMPLATE` | Create Template | Tool to create a new template with specified dimensions and layers. Use when you need to programmatically define a template with background images, text overlays, or shapes. |
| `TEMPLATED_DELETE_FOLDER` | Delete Folder | Tool to delete a folder by its ID. The folder must be empty before deletion. Use when you have confirmed the folder ID and need to remove it permanently. |
| `TEMPLATED_DELETE_RENDER` | Delete Render | Tool to delete a specific render by its ID. Use when you need to permanently remove a render and its associated output files. |
| `TEMPLATED_DELETE_TEMPLATE` | Delete Template | Tool to delete a template by its unique ID. Use when you have confirmed the template ID and need to remove it permanently. |
| `TEMPLATED_DUPLICATE_RENDER` | Duplicate Template Render | Tool to duplicate an existing render with the same settings and template. Use when you need to create a copy of a render. The duplicated render will use the same template and payload as the original. |
| `TEMPLATED_GET_ACCOUNT_INFORMATION` | Get Account Information | Tool to retrieve account information, including email, name, team name, API usage statistics, and subscription plan. Use to check current API quota usage or verify API token validity. |
| `TEMPLATED_LIST_ALL_TEMPLATES` | List All Templates | Tool to list all templates of a user. Use when you need to retrieve available templates with optional pagination. |
| `TEMPLATED_LIST_FOLDER_RENDERS` | List Folder Renders | Tool to list all renders in a specific folder. Use when you need to retrieve all renders contained in a folder with optional pagination. |
| `TEMPLATED_LIST_FOLDERS` | List Folders | Tool to list all folders in the account. Use when you need to retrieve available folders that help organize templates and renders. |
| `TEMPLATED_LIST_FOLDER_TEMPLATES` | List Folder Templates | Tool to list all templates in a specific folder. Use when you need to retrieve templates contained in a folder. |
| `TEMPLATED_LIST_FONTS` | List Fonts | Tool to list all available fonts including Google Fonts and user-uploaded custom fonts. Use when you need to retrieve the names and metadata of fonts available in the account. |
| `TEMPLATED_LIST_GALLERY_TEMPLATES` | List Gallery Templates | Tool to list templates from the public gallery. Use when you need to browse available templates that can be cloned for use. |
| `TEMPLATED_LIST_RENDERS` | List All Renders | Tool to list all renders in the account. Use when you need to retrieve all available renders for the authenticated user. |
| `TEMPLATED_LIST_TEMPLATE_CLONES` | List Template Clones | Tool to list all cloned templates in the account. Use when you need to retrieve templates that were cloned from the gallery or other sources, with optional filtering by source template ID or external ID. |
| `TEMPLATED_LIST_TEMPLATE_RENDERS` | List Template Renders | Tool to list all renders of a specific template. Use after obtaining a template ID when you need paginated render results. |
| `TEMPLATED_LIST_UPLOADS` | List Uploads | Tool to list all uploaded images in the account. Returns upload details including URLs and metadata. Use when you need to retrieve available uploads with optional pagination. |
| `TEMPLATED_MERGE_RENDERS` | Merge Template Renders | Tool to merge multiple renders into a single PDF output. Use when combining multiple images or pages into a unified document. When host=true, returns a URL to the hosted file. When host=false, returns the PDF binary for immediate download. |
| `TEMPLATED_MOVE_RENDER_TO_FOLDER` | Move Render to Folder | Tool to move a render to a specific folder. Use when you need to organize renders by moving them into folders. |
| `TEMPLATED_MOVE_TEMPLATE_TO_FOLDER` | Move Template to Folder | Tool to move a template to a folder. Use when you need to organize templates by moving them into specified folders. |
| `TEMPLATED_REMOVE_TEMPLATE_TAGS` | Remove Template Tags | Tool to remove specific tags from a template. Use when you have a template ID and want to untag existing tags. |
| `TEMPLATED_RETRIEVE_RENDER` | Retrieve Template Render | Tool to retrieve details of a specific render by its ID. Use after obtaining the render ID when you need details of a render. |
| `TEMPLATED_RETRIEVE_TEMPLATE` | Retrieve Template | Tool to retrieve a single Template by its unique ID. Use after obtaining the template ID. |
| `TEMPLATED_UPDATE_FOLDER` | Update Folder | Tool to update an existing folder's properties. Use when you need to change a folder's name or other attributes. |
| `TEMPLATED_UPDATE_TEMPLATE` | Update Template | Tool to update an existing template including its properties and layers. Use replaceLayers=true to replace all layers (layers not in array will be removed), or false/omit to update existing layers and add new ones. |
| `TEMPLATED_UPDATE_TEMPLATE_TAGS` | Update Template Tags | Tool to overwrite all tags on a template. Use when you need to replace the entire tag list for a specific template. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Templated MCP server is an implementation of the Model Context Protocol that connects your AI agent to Templated. It provides structured and secure access so your agent can perform Templated operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 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 Templated account and project
- Basic familiarity with async Python/Typescript

### 1. Getting API Keys for OpenAI, Composio, and Templated

No description provided.

### 2. Installing dependencies

No description provided.
```python
pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv
```

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

### 3. Set environment variables

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 Templated access
```bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id
```

### 4. Import modules

No description provided.
```python
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()
```

```typescript
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();
```

### 5. Load environment variables and initialize Composio

No description provided.
```python
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")
```

```typescript
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");
```

### 6. Create a Tool Router session and build the agent function

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, templated)
- 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 Templated tools.
- The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
```python
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=["templated"],
    )

    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 Templated actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Templated actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)
```

```typescript
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: ["templated"],
    },
  );

  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 Templated actions." ,
    llm,
    tools,
  });

  return agent;
}
```

### 7. Create an interactive chat loop

No description provided.
```python
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}")
```

```typescript
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();
}
```

### 8. Define the main entry point

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 Templated
```python
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!")
```

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

main();
```

### 9. Run the agent

When prompted, authenticate and authorise your agent with Templated, then start asking questions.
```bash
python llamaindex_agent.py
```

```typescript
npx ts-node llamaindex-agent.ts
```

## Complete Code

```python
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=["templated"],
    )

    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 Templated actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Templated 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!")
```

```typescript
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: ["templated"],
    },
  );

  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 Templated 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 Templated to LlamaIndex through Composio's Tool Router MCP layer.
Key takeaways:
- Tool Router dynamically exposes Templated 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 Templated MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/templated/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/templated/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/templated/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/templated/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/templated/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/templated/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/templated/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/templated/framework/cli)
- [Google ADK](https://composio.dev/toolkits/templated/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/templated/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/templated/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/templated/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/templated/framework/crew-ai)

## Related Toolkits

- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.
- [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease.
- [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training.
- [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses.
- [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files.
- [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently.
- [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price.
- [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere.
- [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code.
- [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more.
- [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place.
- [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work.
- [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems.
- [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project.
- [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks.
- [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API.
- [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Templated MCP?

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

### Can I manage the permissions and scopes for Templated while using Tool Router?

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)