How to integrate Paradym MCP with LlamaIndex

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Paradym logo
LlamaIndex logo
divider

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.

Supported Tools & Triggers

Tools
Activate CertificateTool to activate a certificate for use in a project.
Archive AnonCreds Credential TemplateTool to archive an AnonCreds credential template in a project.
Archive mDoc Credential TemplateTool to archive an mDoc credential template.
Archive Presentation TemplateTool to archive a presentation template in a project.
Archive SD-JWT VC Credential TemplateTool to archive an SD-JWT VC credential template in a project.
Create AnonCreds Credential TemplateTool to create a new AnonCreds credential template.
Create CertificateTool to create a new self-signed X.
Create DIDComm Connection InvitationTool to create a DIDComm connection invitation.
Create DIDComm Issuance OfferTool to create a DIDComm credential issuance offer.
Create OpenID4VC Credential OfferTool to create an OpenID4VC credential offer.
Create OpenID4VC Verification RequestTool to create an OpenID4VC verification request.
Create Presentation TemplateTool to create a new presentation template.
Create Project WebhookTool to create a new webhook for a project.
Create SD-JWT VC Credential TemplateTool to create a new SD-JWT VC credential template with selective disclosure capabilities.
Create Trusted EntityTool to create a new trusted entity for a project.
Deactivate CertificateTool to deactivate a certificate in a project.
Delete DIDComm ConnectionTool to delete a DIDComm connection from a project.
Delete DIDComm InvitationTool to delete a DIDComm invitation from a project.
Delete Trusted EntityTool to delete a trusted entity from a project.
Delete Project WebhookTool to delete a webhook endpoint from a project.
Get AnonCreds Credential TemplateTool to retrieve a specific AnonCreds credential template by ID.
Get AnonCreds Credential Template JSON SchemaTool to retrieve the JSON schema for an AnonCreds credential template.
Get DIDComm ConnectionTool to retrieve a specific DIDComm connection by ID.
Get DIDComm ConnectionsTool to retrieve a list of DIDComm connections for a project.
Get DIDComm InvitationTool to retrieve a specific DIDComm invitation by ID.
Get DIDComm Issuance SessionTool to retrieve a specific DIDComm issuance session by ID.
Get DIDsTool to retrieve a list of Decentralized Identifiers (DIDs) for a specific project.
Get mDoc Credential TemplateTool to retrieve a specific mDoc credential template by ID.
Get mDoc Credential Template JSON SchemaTool to retrieve the JSON schema for an mDoc credential template.
Get OpenID4VC Issuance SessionTool to retrieve a specific OpenID4VC issuance session by ID.
Get OpenID4VC Verification SessionTool to retrieve a specific OpenID4VC verification session by ID.
Get Presentation TemplateTool to retrieve a specific presentation template by ID.
Get Presentation TemplatesTool to retrieve a list of presentation templates for a project.
Get Project MembersTool to retrieve a list of project members.
Get Project ProfileTool to retrieve the default profile for a project.
Get ProjectsTool to retrieve a list of all projects accessible to the authenticated user.
Get Project WebhooksTool to retrieve a list of webhooks configured for a specific project.
Get SD-JWT VC Credential TemplateTool to retrieve a specific SD-JWT VC credential template by ID.
Get SD-JWT VC Credential Template JSON SchemaTool to retrieve the JSON schema for an SD-JWT VC credential template.
Get Trusted EntitiesTool to retrieve trusted entities for a specific project.
Get Trusted EntityTool to retrieve a specific trusted entity by ID.
Issue Direct SD-JWT VCTool to directly issue an SD-JWT VC credential without exchange protocol.
List AnonCreds Credential TemplatesTool to retrieve all AnonCreds credential templates for a project.
List CertificatesTool to retrieve all X.
List Certificate Signing RequestsTool to retrieve all certificate signing requests for a project.
List DIDComm InvitationsTool to retrieve all DIDComm invitations for a project.
List DIDComm Issuance OffersTool to list all DIDComm issuance offers within a project.
List DIDComm Mediator ConnectionsTool to retrieve connections for a DIDComm mediator.
List DIDComm MediatorsTool to retrieve all DIDComm mediators for a project.
List DIDComm Verification RequestsTool to list all DIDComm verification sessions for a project.
List Issued CredentialsTool to list metadata for all issued credentials within a project.
List mDoc Credential TemplatesTool to retrieve all mDoc credential templates for a project.
List OpenID4VC Issuance SessionsTool to retrieve all OpenID4VC issuance sessions for a project.
List OpenID4VC Verification SessionsTool to retrieve all OpenID4VC verification sessions for a project.
List SD-JWT VC Credential TemplatesTool to retrieve all SD-JWT VC credential templates for a project.
Receive DIDComm InvitationTool to receive and process an external DIDComm invitation.
Revoke CertificateTool to revoke a certificate in a project.
Send DIDComm Basic MessageTool to send a basic DIDComm message to a connection.
Send Custom DIDComm MessageTool to send a custom DIDComm message to a connection.
Unarchive AnonCreds Credential TemplateTool to unarchive an archived AnonCreds credential template.
Unarchive mDoc Credential TemplateTool to unarchive an archived mDoc credential template.
Unarchive SD-JWT VC Credential TemplateTool to unarchive an archived SD-JWT VC credential template.
Update DIDComm ConnectionTool to update a DIDComm connection.
Update mDoc Credential TemplateTool to update an existing mDoc credential template.
Update Presentation TemplateTool to update an existing presentation template.
Update ProjectTool to update an existing project's name and verification data access settings.
Update Project ProfileTool to update the default profile for a project.
Update SD-JWT VC Credential TemplateTool to update an existing SD-JWT VC credential template.
Update Trusted EntityTool to update an existing trusted entity in a project.

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

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

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

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

  • composio-llamaindex: Composio's LlamaIndex integration
  • llama-index: Core LlamaIndex framework
  • llama-index-llms-openai: OpenAI LLM integration
  • llama-index-tools-mcp: MCP client for LlamaIndex
  • python-dotenv: Environment variable management

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

Import modules

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()

Create a new file called paradym_llamaindex_agent.py and import the required modules:

Key imports:

  • asyncio: For async/await support
  • Composio: Main client for Composio services
  • LlamaIndexProvider: Adapts Composio tools for LlamaIndex
  • ReActAgent: LlamaIndex's reasoning and action agent
  • BasicMCPClient: Connects to MCP endpoints
  • McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

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")

What's happening:

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

Create a Tool Router session and build the agent function

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)

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.

Create an interactive chat loop

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}")

What's happening here:

  • We're creating a direct terminal interface to chat with your Paradym database
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

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!")

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

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 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!")

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 logo

OpenAI Agents SDK

Use Paradym MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Paradym MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Paradym MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Paradym MCP with Claude Cowork

Codex logo

Codex

Use Paradym MCP with Codex

OpenClaw logo

OpenClaw

Use Paradym MCP with OpenClaw

Hermes logo

Hermes

Use Paradym MCP with Hermes

CLI logo

CLI

Use Paradym MCP with CLI

Google ADK logo

Google ADK

Use Paradym MCP with Google ADK

LangChain logo

LangChain

Use Paradym MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Paradym MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Paradym MCP with Mastra AI

CrewAI logo

CrewAI

Use Paradym MCP with CrewAI

FAQ

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗