SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Ignisign MCP with Google ADK

Connect Google ADK to Ignisign MCP. Start a new signature request for a contract, add a new signer to this application, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Ignisign logoIgnisign
Api Key

Ignisign is an electronic signature platform for secure online document signing and management. Streamline agreements and digital paperwork with advanced workflow tools.

32 Tools

Introduction

This guide walks you through connecting Ignisign to Google ADK using the Composio tool router. By the end, you'll have a working Ignisign agent that can create and publish signature requests, add signers, upload documents, download signed documents, and manage webhooks through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Ignisign account through Composio's Ignisign MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Ignisign with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get a Ignisign account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Ignisign
  • Build an agent that connects to Ignisign through MCP
  • Interact with Ignisign 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 Ignisign MCP server, and what's possible with it?

The Ignisign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ignisign account. It provides structured and secure access to your electronic signature workflows, so your agent can perform actions like sending signature requests, managing documents, onboarding signers, and handling signature operations on your behalf.

  • Automated signature request management: Let your agent create, cancel, or delete signature requests, streamlining the entire e-signature process from start to finish.
  • Document initialization and deletion: Have the agent initialize new documents for signing or permanently delete documents when they're no longer needed.
  • Signer onboarding and removal: Effortlessly add new signers to your application environment or remove existing ones as your workflows change.
  • Webhook endpoint management: Allow your agent to create or delete webhook endpoints, enabling real-time notifications and integrations for signature events.
  • Application context retrieval: Fetch global application settings and environment configurations so your agent always works with up-to-date information.

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 step09 STEPS
1

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
2

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.
3

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 Ignisign via MCP
  • python-dotenv loads environment variables
4

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
5

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
6

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
7

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

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
8

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 Ignisign 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
9

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 Ignisign 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=["ignisign"],
)

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 Ignisign operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Ignisign 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.

TOOLS

Supported Tools

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

Ignisign API Authentication

Tool to authenticate an application over Ignisign API and retrieve a JWT.

Cancel Signature Request

Cancel (close) a signature request to terminate it.

Initialize Document

Tool to initialize a document for a signature request.

Create Signer

Tool to create a new signer.

Create Webhook Endpoint

Tool to create a new webhook endpoint for an application.

Delete Document

Tool to delete a specific document by its ID.

Delete Ignisign Signature Request

Permanently deletes a signature request from Ignisign by its ID.

Delete Signer

Tool to revoke/delete a signer from an Ignisign application environment.

Delete Webhook Endpoint

Deletes a webhook endpoint by ID.

Get application context

Tool to retrieve the global context of an application.

Get Document Information

Tool to retrieve document metadata by ID.

Get Missing Signer Inputs

Retrieve missing inputs for a signer and profile.

Get Signature Request Details

Tool to retrieve detailed information for a specific signature request.

Get Signature Request Document

Downloads a document's original file.

Get Signature Requests

Retrieves a paginated list of signature requests for a specific Ignisign application and environment.

Get Signed Document

Tool to download the signed document (signature proof) for a signature request.

Get Signer Input Constraints

Tool to get signer input constraints.

Get Signer Inputs

Retrieve available signer input values from a signature request's context.

Get Signer Profile

Retrieve detailed information about a specific signer profile by its ID.

Get Signer Profiles

Retrieve all signer profiles for a specific Ignisign application environment.

Get Webhooks

Retrieves all webhook endpoints configured for a specific Ignisign application environment.

Initialize Ignisign Signature Request

Initialize a new signature request in Ignisign.

List Documents

Tool to retrieve documents linked to a signature request.

Provide Document Content Data JSON

Provides JSON content to an existing document in Ignisign.

Provide Document Content File

Tool to provide file content for a document.

Provide Document Content Private File

Provides private document content by submitting its SHA-256 hash to IgniSign.

Publish Signature Request

Tool to publish a draft signature request.

Search Signers

Tool to search for signers within an application environment with pagination support.

Update Document Information

Tool to update document metadata.

Update Signature Request

Tool to partially update a signature request in DRAFT state.

Update Signer

Updates an existing signer's profile assignment.

Update Webhook Endpoint

Updates an existing webhook endpoint's destination URL and optionally its description.

FRAMEWORKS

How to build Ignisign MCP Agent with another framework

Claude Code logo

Claude Code

Use Ignisign MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Ignisign MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Ignisign MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Ignisign MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Ignisign MCP with Grok Bot

Codex logo

Codex

Use Ignisign MCP with Codex

OpenClaw logo

OpenClaw

Use Ignisign MCP with OpenClaw

Hermes logo

Hermes

Use Ignisign MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Ignisign MCP with Atomic Agent

LangChain logo

LangChain

Use Ignisign MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Ignisign MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Ignisign MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Ignisign MCP with LlamaIndex

CrewAI logo

CrewAI

Use Ignisign MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Ignisign MCP with Pydantic AI

AutoGen logo

AutoGen

Use Ignisign MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Ignisign MCP server, the agents and LLMs can only access a fixed set of Ignisign tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ignisign and many other apps based on the task at hand, all through a single MCP endpoint.

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 Ignisign tools.

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

Start with Ignisign.It takes 30 seconds.

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

Start building