How to integrate Paradym MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Paradym logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Paradym to Google ADK 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 Google ADK 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:
  • Get a Paradym account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Paradym
  • Build an agent that connects to Paradym through MCP
  • Interact with Paradym using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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 starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Paradym via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["paradym"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Paradym operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Paradym and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["paradym"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Paradym operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Paradym with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Paradym using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Paradym tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Paradym MCP Agent with another framework

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 Google ADK?

Yes, you can. Google ADK 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.