# How to integrate Paradym MCP with LlamaIndex

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

## Introduction

This guide walks you through connecting Paradym to LlamaIndex using the Composio tool router. By the end, you'll have a working Paradym agent that can issue sd-jwt verifiable credential for a user, verify authenticity of a presented credential, list all credentials issued to an email address through natural language commands.
This guide will help you understand how to give your LlamaIndex agent real control over a Paradym account through Composio's Paradym MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Paradym with

- [OpenAI Agents SDK](https://composio.dev/toolkits/paradym/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/paradym/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/paradym/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/paradym/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/paradym/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/paradym/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/paradym/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/paradym/framework/cli)
- [Google ADK](https://composio.dev/toolkits/paradym/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/paradym/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/paradym/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/paradym/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/paradym/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 Paradym
- Connect LlamaIndex to the Paradym MCP server
- Build a Paradym-powered agent using LlamaIndex
- Interact with Paradym 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 Paradym MCP server, and what's possible with it?

The Paradym MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Paradym account. It provides structured and secure access to your verifiable credential workflows, so your agent can perform actions like issuing credentials, verifying identity claims, managing credential lifecycles, and supporting interoperability across digital identity standards.
- Automated credential issuance: Instruct your agent to issue new verifiable credentials to users or systems, supporting protocols like SD-JWT VCs and AnonCreds.
- Seamless credential verification: Enable your agent to verify the authenticity and validity of credentials presented by others, streamlining onboarding and trust checks.
- Credential lifecycle management: Allow your agent to update, revoke, or renew existing credentials, ensuring full control over your digital identity assets.
- Interoperability with identity standards: Leverage your agent to work across OpenID4VC, DIDComm, and other standards for maximum compatibility and flexibility.
- Audit and usage tracking: Task your agent to retrieve detailed logs or status reports on credential activity, helping you maintain compliance and visibility.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `PARADYM_ACTIVATE_CERTIFICATE` | Activate Certificate | Tool to activate a certificate for use in a project. Use when you need to enable a certificate that is in pending activation status. |
| `PARADYM_ARCHIVE_ANONCREDS_CREDENTIAL_TEMPLATE` | Archive AnonCreds Credential Template | Tool to archive an AnonCreds credential template in a project. Use when you need to remove or deactivate a credential template. Returns success status upon archival. |
| `PARADYM_ARCHIVE_MDOC_CREDENTIAL_TEMPLATE` | Archive mDoc Credential Template | Tool to archive an mDoc credential template. Use when you need to archive a template that is no longer needed. |
| `PARADYM_ARCHIVE_PRESENTATION_TEMPLATE` | Archive Presentation Template | Tool to archive a presentation template in a project. Use when you need to remove or deactivate a presentation template. Returns success status upon archival. |
| `PARADYM_ARCHIVE_SD_JWT_VC_CREDENTIAL_TEMPLATE` | Archive SD-JWT VC Credential Template | Tool to archive an SD-JWT VC credential template in a project. Use when you need to remove or deactivate an SD-JWT VC credential template. |
| `PARADYM_CREATE_ANONCREDS_CREDENTIAL_TEMPLATE` | Create AnonCreds Credential Template | Tool to create a new AnonCreds credential template. Use when you have a project ID and want to define a credential schema with specific attributes. |
| `PARADYM_CREATE_CERTIFICATE` | Create Certificate | Tool to create a new self-signed X.509 certificate for a project. Use when you need to create a root certificate for verifying or issuing credentials. |
| `PARADYM_CREATE_DIDCOMM_CONNECTION_INVITATION` | Create DIDComm Connection Invitation | Tool to create a DIDComm connection invitation. Use when you need to establish a new DIDComm connection for a project. |
| `PARADYM_CREATE_DIDCOMM_ISSUANCE_OFFER` | Create DIDComm Issuance Offer | Tool to create a DIDComm credential issuance offer. Use when you need to offer credentials via DIDComm protocol after obtaining a project ID and credential template. |
| `PARADYM_CREATE_OPENID4VC_CREDENTIAL_OFFER` | Create OpenID4VC Credential Offer | Tool to create an OpenID4VC credential offer. Use when you need to issue verifiable credentials using OpenID4VC protocol. Note: Only works with SD-JWT VC and mDoc credential templates. |
| `PARADYM_CREATE_OPENID4VC_VERIFICATION_REQUEST` | Create OpenID4VC Verification Request | Tool to create an OpenID4VC verification request. Use when you need to initiate a credential verification flow with a presentation template. |
| `PARADYM_CREATE_PRESENTATION_TEMPLATE` | Create Presentation Template | Tool to create a new presentation template. Use when you have a project ID and template definition ready. |
| `PARADYM_CREATE_PROJECT_WEBHOOK` | Create Project Webhook | Tool to create a new webhook for a project. Use after obtaining the project ID to subscribe to specific project events. |
| `PARADYM_CREATE_SD_JWT_VC_CREDENTIAL_TEMPLATE` | Create SD-JWT VC Credential Template | Tool to create a new SD-JWT VC credential template with selective disclosure capabilities. Use when you have a project ID and want to define a credential with attributes that can be selectively disclosed. |
| `PARADYM_CREATE_TRUSTED_ENTITY` | Create Trusted Entity | Tool to create a new trusted entity for a project. Use when you need to add trusted DIDs or X509 certificates to establish trust relationships. |
| `PARADYM_DEACTIVATE_CERTIFICATE` | Deactivate Certificate | Tool to deactivate a certificate in a project. Use when you need to deactivate an active certificate, changing its status to inactive. |
| `PARADYM_DELETE_DID_COMM_CONNECTION` | Delete DIDComm Connection | Tool to delete a DIDComm connection from a project. Use when removing a connection that is no longer needed. |
| `PARADYM_DELETE_DIDCOMM_INVITATION` | Delete DIDComm Invitation | Tool to delete a DIDComm invitation from a project. Use when removing an invitation that is no longer needed. |
| `PARADYM_DELETE_TRUSTED_ENTITY` | Delete Trusted Entity | Tool to delete a trusted entity from a project. Use when you need to remove a trusted entity that is no longer needed. |
| `PARADYM_DELETE_WEBHOOK` | Delete Project Webhook | Tool to delete a webhook endpoint from a project. Use when removing a webhook no longer needed. Returns the deletion status. |
| `PARADYM_GET_ANONCREDS_CREDENTIAL_TEMPLATE` | Get AnonCreds Credential Template | Tool to retrieve a specific AnonCreds credential template by ID. Use when you need to view details of a specific credential template after obtaining the project ID and template ID. |
| `PARADYM_GET_ANONCREDS_CREDENTIAL_TEMPLATE_JSON_SCHEMA` | Get AnonCreds Credential Template JSON Schema | Tool to retrieve the JSON schema for an AnonCreds credential template. Use when you need to understand the structure and validation rules of a credential template. |
| `PARADYM_GET_DID_COMM_CONNECTION` | Get DIDComm Connection | Tool to retrieve a specific DIDComm connection by ID. Use when you need to fetch details of a particular connection. |
| `PARADYM_GET_DID_COMM_CONNECTIONS` | Get DIDComm Connections | Tool to retrieve a list of DIDComm connections for a project. Use when you need to fetch connections after obtaining the project ID. |
| `PARADYM_GET_DIDCOMM_INVITATION` | Get DIDComm Invitation | Tool to retrieve a specific DIDComm invitation by ID. Use when you need to get details of an existing invitation after obtaining the project ID and invitation ID. |
| `PARADYM_GET_DIDCOMM_ISSUANCE_SESSION` | Get DIDComm Issuance Session | Tool to retrieve a specific DIDComm issuance session by ID. Use when you need to check the status or details of a credential issuance session. |
| `PARADYM_GET_DI_DS` | Get DIDs | Tool to retrieve a list of Decentralized Identifiers (DIDs) for a specific project. Use after project creation when you need to list or paginate through DIDs. |
| `PARADYM_GET_MDOC_CREDENTIAL_TEMPLATE` | Get mDoc Credential Template | Tool to retrieve a specific mDoc credential template by ID. Use when you need to fetch details of an existing mDoc credential template for a project. |
| `PARADYM_GET_MDOC_CREDENTIAL_TEMPLATE_JSON_SCHEMA` | Get mDoc Credential Template JSON Schema | Tool to retrieve the JSON schema for an mDoc credential template. Use when you need to understand the structure and validation rules of an mDoc credential template. |
| `PARADYM_GET_OPENID4VC_ISSUANCE_SESSION` | Get OpenID4VC Issuance Session | Tool to retrieve a specific OpenID4VC issuance session by ID. Use when you need to check the status or details of an issuance session. |
| `PARADYM_GET_OPENID4VC_VERIFICATION_SESSION` | Get OpenID4VC Verification Session | Tool to retrieve a specific OpenID4VC verification session by ID. Use when you need to check the status or details of an existing verification session. |
| `PARADYM_GET_PRESENTATION_TEMPLATE` | Get Presentation Template | Tool to retrieve a specific presentation template by ID. Use when you need to fetch details of an existing presentation template for a project. |
| `PARADYM_GET_PRESENTATION_TEMPLATES` | Get Presentation Templates | Tool to retrieve a list of presentation templates for a project. Use when you need to list presentation templates after obtaining the project ID. |
| `PARADYM_GET_PROJECT_MEMBERS` | Get Project Members | Tool to retrieve a list of project members. Use after confirming the project ID exists. |
| `PARADYM_GET_PROJECT_PROFILE` | Get Project Profile | Tool to retrieve the default profile for a project. Use after confirming the project ID exists when you need to get profile details such as DID, display name, logo, and wallet configuration. |
| `PARADYM_GET_PROJECTS` | Get Projects | Tool to retrieve a list of all projects accessible to the authenticated user. Use after authentication when you need to list available projects. |
| `PARADYM_GET_PROJECT_WEBHOOKS` | Get Project Webhooks | Tool to retrieve a list of webhooks configured for a specific project. Use when you need to list configured webhooks before managing or auditing them. |
| `PARADYM_GET_SD_JWT_VC_CREDENTIAL_TEMPLATE` | Get SD-JWT VC Credential Template | Tool to retrieve a specific SD-JWT VC credential template by ID. Use when you need to fetch details of an existing SD-JWT VC credential template for a project. |
| `PARADYM_GET_SD_JWT_VC_CREDENTIAL_TEMPLATE_JSON_SCHEMA` | Get SD-JWT VC Credential Template JSON Schema | Tool to retrieve the JSON schema for an SD-JWT VC credential template. Use when you need to understand the structure and validation rules of an SD-JWT VC credential template. |
| `PARADYM_GET_TRUSTED_ENTITIES` | Get Trusted Entities | Tool to retrieve trusted entities for a specific project. Use when you need to list all trusted entities associated with a Paradym project after authentication. |
| `PARADYM_GET_TRUSTED_ENTITY` | Get Trusted Entity | Tool to retrieve a specific trusted entity by ID. Use when you need to get detailed information about a particular trusted entity including its certificates and DIDs. |
| `PARADYM_ISSUE_DIRECT_SD_JWT_VC` | Issue Direct SD-JWT VC | Tool to directly issue an SD-JWT VC credential without exchange protocol. Use when you need to create a verifiable credential with selective disclosure capabilities for a specific credential template. |
| `PARADYM_LIST_ANON_CREDS_CREDENTIAL_TEMPLATES` | List AnonCreds Credential Templates | Tool to retrieve all AnonCreds credential templates for a project. Use when you need to list available credential templates for issuing AnonCreds verifiable credentials. |
| `PARADYM_LIST_CERTIFICATES` | List Certificates | Tool to retrieve all X.509 certificates for a project. Use when you need to list certificates with optional filtering by type, key type, status, or other attributes. |
| `PARADYM_LIST_CERTIFICATE_SIGNING_REQUESTS` | List Certificate Signing Requests | Tool to retrieve all certificate signing requests for a project. Use when you need to list or audit CSRs for certificate management. |
| `PARADYM_LIST_DIDCOMM_INVITATIONS` | List DIDComm Invitations | Tool to retrieve all DIDComm invitations for a project. Use when you need to inspect or paginate through connection invitations after obtaining the project ID. |
| `PARADYM_LIST_DIDCOMM_ISSUANCE_OFFERS` | List DIDComm Issuance Offers | Tool to list all DIDComm issuance offers within a project. Use when you need to retrieve or paginate issuance offers after obtaining a project ID. |
| `PARADYM_LIST_DIDCOMM_MEDIATOR_CONNECTIONS` | List DIDComm Mediator Connections | Tool to retrieve connections for a DIDComm mediator. Use when you need to list all connections associated with a specific mediator in a project. |
| `PARADYM_LIST_DIDCOMM_MEDIATORS` | List DIDComm Mediators | Tool to retrieve all DIDComm mediators for a project. Use when you need to list available mediators for routing DIDComm messages. |
| `PARADYM_LIST_DIDCOMM_VERIFICATION_REQUESTS` | List DIDComm Verification Requests | Tool to list all DIDComm verification sessions for a project. Use when you need to fetch DIDComm verification requests after obtaining the project ID. |
| `PARADYM_LIST_ISSUED_CREDENTIALS` | List Issued Credentials | Tool to list metadata for all issued credentials within a project. Use after confirming a valid project ID to fetch credentials, optionally filtering by status. |
| `PARADYM_LIST_MDOC_CREDENTIAL_TEMPLATES` | List mDoc Credential Templates | Tool to retrieve all mDoc credential templates for a project. Use when you need to list mDoc format credential templates after obtaining the project ID. |
| `PARADYM_LIST_OPENID4VC_ISSUANCE_SESSIONS` | List OpenID4VC Issuance Sessions | Tool to retrieve all OpenID4VC issuance sessions for a project. Use when you need to list credential issuance sessions, optionally filtering by ID or status. |
| `PARADYM_LIST_OPENID4VC_VERIFICATION_SESSIONS` | List OpenID4VC Verification Sessions | Tool to retrieve all OpenID4VC verification sessions for a project. Use when you need to list OpenID4VC verification sessions after obtaining the project ID. |
| `PARADYM_LIST_SD_JWT_VC_CREDENTIAL_TEMPLATES` | List SD-JWT VC Credential Templates | Tool to retrieve all SD-JWT VC credential templates for a project. Use when you need to list credential templates in SD-JWT VC format, with optional filtering by ID, type, revocable status, or archived status. |
| `PARADYM_RECEIVE_DIDCOMM_INVITATION` | Receive DIDComm Invitation | Tool to receive and process an external DIDComm invitation. Use when you need to accept a connection invitation from another party. |
| `PARADYM_REVOKE_CERTIFICATE` | Revoke Certificate | Tool to revoke a certificate in a project. Use when you need to invalidate a certificate. Returns the updated certificate details with revoked status. |
| `PARADYM_SEND_DIDCOMM_BASIC_MESSAGE` | Send DIDComm Basic Message | Tool to send a basic DIDComm message to a connection. Use when you need to send a text message through an established DIDComm connection. |
| `PARADYM_SEND_DID_COMM_CUSTOM_MESSAGE` | Send Custom DIDComm Message | Tool to send a custom DIDComm message to a connection. Use when you need to send custom protocol messages over an established DIDComm connection. |
| `PARADYM_UNARCHIVE_ANONCREDS_CREDENTIAL_TEMPLATE` | Unarchive AnonCreds Credential Template | Tool to unarchive an archived AnonCreds credential template. Use when you need to restore an archived credential template to active status. |
| `PARADYM_UNARCHIVE_MDOC_CREDENTIAL_TEMPLATE` | Unarchive mDoc Credential Template | Tool to unarchive an archived mDoc credential template. Use when you need to restore an archived credential template to active status. |
| `PARADYM_UNARCHIVE_SD_JWT_VC_CREDENTIAL_TEMPLATE` | Unarchive SD-JWT VC Credential Template | Tool to unarchive an archived SD-JWT VC credential template. Use when you need to restore an archived credential template to active status. |
| `PARADYM_UPDATE_DID_COMM_CONNECTION` | Update DIDComm Connection | Tool to update a DIDComm connection. Use when you need to modify connection details like display name. |
| `PARADYM_UPDATE_MDOC_CREDENTIAL_TEMPLATE` | Update mDoc Credential Template | Tool to update an existing mDoc credential template. Use when you need to modify template name, attributes, validity period, or styling for an mDoc credential. |
| `PARADYM_UPDATE_PRESENTATION_TEMPLATE` | Update Presentation Template | Tool to update an existing presentation template. Use when you need to modify template name, description, credentials, or verifier configuration. |
| `PARADYM_UPDATE_PROJECT` | Update Project | Tool to update an existing project's name and verification data access settings. Use when you need to modify project details. |
| `PARADYM_UPDATE_PROJECT_PROFILE` | Update Project Profile | Tool to update the default profile for a project. Use when you need to modify profile display settings, logo, OpenID4VC version, or wallet configuration. |
| `PARADYM_UPDATE_SD_JWT_VC_CREDENTIAL_TEMPLATE` | Update SD-JWT VC Credential Template | Tool to update an existing SD-JWT VC credential template. Use when you need to modify template name, attributes, validity periods, or styling for an SD-JWT VC credential. |
| `PARADYM_UPDATE_TRUSTED_ENTITY` | Update Trusted Entity | Tool to update an existing trusted entity in a project. Use when you need to modify the name, certificates, or DIDs of a trusted entity. |

## Supported Triggers

None listed.

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

The Paradym MCP server is an implementation of the Model Context Protocol that connects your AI agent to Paradym. It provides structured and secure access so your agent can perform Paradym 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 Paradym account and project
- Basic familiarity with async Python/Typescript

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

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 Paradym 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, paradym)
- 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 Paradym 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=["paradym"],
    )

    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 Paradym actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Paradym 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: ["paradym"],
    },
  );

  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 Paradym 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 Paradym
```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 Paradym, 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=["paradym"],
    )

    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 Paradym actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Paradym 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: ["paradym"],
    },
  );

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

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

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.
- [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.
- [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease.
- [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data.

## Frequently Asked Questions

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

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

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

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

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