Paradym with Claude Agent SDK

How to integrate Paradym MCP with Claude Agent SDK

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Paradym with TL;DR What is Claude Agent SDK What is the Paradym MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Paradym MCP Agent with another framework Explore Other Toolkits FAQ

Connect Paradym without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Paradym to the Claude Agent SDK 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 Claude Agent SDK 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 Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your Claude/Anthropic and Composio API keys
Install the necessary dependencies
Initialize Composio and create a Tool Router session for Paradym
Configure an AI agent that can use Paradym as a tool
Run a live chat session where you can ask the agent to perform Paradym operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

Native MCP Support: Built-in support for Model Context Protocol servers
Permission Modes: Control tool execution permissions
Streaming Responses: Real-time response streaming for interactive applications
Context Manager: Clean async context management for sessions

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:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:

Composio API Key and Claude/Anthropic API Key
Primary know-how of Claude Agents SDK
A Paradym account
Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key

Go to the Anthropic Console and create an API key. You'll need credits to use the models.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

composio-anthropic provides Composio integration for Anthropic
claude-agent-sdk is the core agent framework
python-dotenv loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID identifies the user for session management
ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

What's happening:

We're importing all necessary libraries including the Claude Agent SDK and Composio
The load_dotenv() function loads environment variables from your .env file
This setup prepares the foundation for connecting Claude with Paradym functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Paradym
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["paradym"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

What's happening:

The function checks for the required COMPOSIO_API_KEY environment variable
We're creating a Composio instance using our API key
The create method creates a Tool Router session for Paradym
The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Paradym tools via Composio.",
    max_turns=10
)

What's happening:

We're configuring the Claude Agent options with the MCP server URL
permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
The system prompt instructs the agent that it has access to Paradym
max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()

What's happening:

The Claude SDK client is created using the async context manager pattern
The agent processes each query and streams the response back in real-time
The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

What's happening:

This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Paradym and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Paradym
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["paradym"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Paradym tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Paradym through Composio's Tool Router.

Key features:

Native MCP support through Claude's agent framework
Streaming responses for real-time interaction
Permission bypass for smooth automated workflows

You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Paradym MCP Agent with another framework

OpenAI Agents SDK

Use Paradym MCP with OpenAI Agents SDK

Claude Code

Use Paradym MCP with Claude Code

Claude Cowork

Use Paradym MCP with Claude Cowork

Codex

Use Paradym MCP with Codex

OpenClaw

Use Paradym MCP with OpenClaw

Hermes

Use Paradym MCP with Hermes

CLI

Use Paradym MCP with CLI

Google ADK

Use Paradym MCP with Google ADK

LangChain

Use Paradym MCP with LangChain

Vercel AI SDK

Use Paradym MCP with Vercel AI SDK

Mastra AI

Use Paradym MCP with Mastra AI

LlamaIndex

Use Paradym MCP with LlamaIndex

CrewAI

Use Paradym MCP with CrewAI

Explore Other Toolkits

Supabase

Oauth2Api Key

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

No Auth

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

Oauth2

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.

TOOLKIT MARKETPLACE

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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

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 free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate Paradym MCP with Claude Agent SDK

Table of Contents

Connect Paradym without Auth hassles

Introduction

Also integrate Paradym with

TL;DR

What is Claude Agent SDK?

What is the Paradym MCP server, and what's possible with it?

Supported Tools & Triggers

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for Claude/Anthropic and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio instance and Tool Router session

Configure Claude Agent with MCP

Create client and start chat loop

Run the application

Complete Code

Conclusion

How to build Paradym MCP Agent with another framework

OpenAI Agents SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Supabase

Codeinterpreter

GitHub

FAQ

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

Can I use Tool Router MCP with Claude Agent SDK?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability