How to integrate Paradym MCP with LlamaIndex

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.

Paradym logoParadym
Api Key

Paradym is an API-first platform for issuing, verifying, and managing verifiable credentials. It streamlines credential workflows using standards like SD-JWT VCs and AnonCreds.

69 Tools

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

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.

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

Getting API Keys for OpenAI, Composio, and Paradym

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 Paradym 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 paradym_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: ["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;
}

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.
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 Paradym
  • 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 Paradym 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 Paradym
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with Paradym 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: ["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.
TOOLS

Supported Tools

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

Activate Certificate

Tool to activate a certificate for use in a project.

Archive AnonCreds Credential Template

Tool to archive an AnonCreds credential template in a project.

Archive mDoc Credential Template

Tool to archive an mDoc credential template.

Archive Presentation Template

Tool to archive a presentation template in a project.

Archive SD-JWT VC Credential Template

Tool to archive an SD-JWT VC credential template in a project.

Create AnonCreds Credential Template

Tool to create a new AnonCreds credential template.

Create Certificate

Tool to create a new self-signed X.

Create DIDComm Connection Invitation

Tool to create a DIDComm connection invitation.

Create DIDComm Issuance Offer

Tool to create a DIDComm credential issuance offer.

Create OpenID4VC Credential Offer

Tool to create an OpenID4VC credential offer.

Create OpenID4VC Verification Request

Tool to create an OpenID4VC verification request.

Create Presentation Template

Tool to create a new presentation template.

Create Project Webhook

Tool to create a new webhook for a project.

Create SD-JWT VC Credential Template

Tool to create a new SD-JWT VC credential template with selective disclosure capabilities.

Create Trusted Entity

Tool to create a new trusted entity for a project.

Deactivate Certificate

Tool to deactivate a certificate in a project.

Delete DIDComm Connection

Tool to delete a DIDComm connection from a project.

Delete DIDComm Invitation

Tool to delete a DIDComm invitation from a project.

Delete Trusted Entity

Tool to delete a trusted entity from a project.

Delete Project Webhook

Tool to delete a webhook endpoint from a project.

Get AnonCreds Credential Template

Tool to retrieve a specific AnonCreds credential template by ID.

Get AnonCreds Credential Template JSON Schema

Tool to retrieve the JSON schema for an AnonCreds credential template.

Get DIDComm Connection

Tool to retrieve a specific DIDComm connection by ID.

Get DIDComm Connections

Tool to retrieve a list of DIDComm connections for a project.

Get DIDComm Invitation

Tool to retrieve a specific DIDComm invitation by ID.

Get DIDComm Issuance Session

Tool to retrieve a specific DIDComm issuance session by ID.

Get DIDs

Tool to retrieve a list of Decentralized Identifiers (DIDs) for a specific project.

Get mDoc Credential Template

Tool to retrieve a specific mDoc credential template by ID.

Get mDoc Credential Template JSON Schema

Tool to retrieve the JSON schema for an mDoc credential template.

Get OpenID4VC Issuance Session

Tool to retrieve a specific OpenID4VC issuance session by ID.

Get OpenID4VC Verification Session

Tool to retrieve a specific OpenID4VC verification session by ID.

Get Presentation Template

Tool to retrieve a specific presentation template by ID.

Get Presentation Templates

Tool to retrieve a list of presentation templates for a project.

Get Project Members

Tool to retrieve a list of project members.

Get Project Profile

Tool to retrieve the default profile for a project.

Get Projects

Tool to retrieve a list of all projects accessible to the authenticated user.

Get Project Webhooks

Tool to retrieve a list of webhooks configured for a specific project.

Get SD-JWT VC Credential Template

Tool to retrieve a specific SD-JWT VC credential template by ID.

Get SD-JWT VC Credential Template JSON Schema

Tool to retrieve the JSON schema for an SD-JWT VC credential template.

Get Trusted Entities

Tool to retrieve trusted entities for a specific project.

Get Trusted Entity

Tool to retrieve a specific trusted entity by ID.

Issue Direct SD-JWT VC

Tool to directly issue an SD-JWT VC credential without exchange protocol.

List AnonCreds Credential Templates

Tool to retrieve all AnonCreds credential templates for a project.

List Certificates

Tool to retrieve all X.

List Certificate Signing Requests

Tool to retrieve all certificate signing requests for a project.

List DIDComm Invitations

Tool to retrieve all DIDComm invitations for a project.

List DIDComm Issuance Offers

Tool to list all DIDComm issuance offers within a project.

List DIDComm Mediator Connections

Tool to retrieve connections for a DIDComm mediator.

List DIDComm Mediators

Tool to retrieve all DIDComm mediators for a project.

List DIDComm Verification Requests

Tool to list all DIDComm verification sessions for a project.

List Issued Credentials

Tool to list metadata for all issued credentials within a project.

List mDoc Credential Templates

Tool to retrieve all mDoc credential templates for a project.

List OpenID4VC Issuance Sessions

Tool to retrieve all OpenID4VC issuance sessions for a project.

List OpenID4VC Verification Sessions

Tool to retrieve all OpenID4VC verification sessions for a project.

List SD-JWT VC Credential Templates

Tool to retrieve all SD-JWT VC credential templates for a project.

Receive DIDComm Invitation

Tool to receive and process an external DIDComm invitation.

Revoke Certificate

Tool to revoke a certificate in a project.

Send DIDComm Basic Message

Tool to send a basic DIDComm message to a connection.

Send Custom DIDComm Message

Tool to send a custom DIDComm message to a connection.

Unarchive AnonCreds Credential Template

Tool to unarchive an archived AnonCreds credential template.

Unarchive mDoc Credential Template

Tool to unarchive an archived mDoc credential template.

Unarchive SD-JWT VC Credential Template

Tool to unarchive an archived SD-JWT VC credential template.

Update DIDComm Connection

Tool to update a DIDComm connection.

Update mDoc Credential Template

Tool to update an existing mDoc credential template.

Update Presentation Template

Tool to update an existing presentation template.

Update Project

Tool to update an existing project's name and verification data access settings.

Update Project Profile

Tool to update the default profile for a project.

Update SD-JWT VC Credential Template

Tool to update an existing SD-JWT VC credential template.

Update Trusted Entity

Tool to update an existing trusted entity in a project.

FAQ

Frequently asked questions

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.

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.

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.

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.

Start with Paradym.It takes 30 seconds.

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

Start building