How to integrate eSignatures MCP with OpenAI Agents SDK

This guide walks you through connecting eSignatures to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working eSignatures agent that can draft contracts, send contracts for signing, add signers, manage templates, and check contract details through natural language commands. This guide will help you understand how to give your OpenAI Agents SDK agent real control over a eSignatures account through Composio's eSignatures MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

eSignatures logoeSignatures
Api Key

eSignatures is an electronic signature platform for creating templates, sending contracts, and managing signers. It helps teams close agreements faster with trackable, paperless signing workflows.

28 Tools

Introduction

This guide walks you through connecting eSignatures to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working eSignatures agent that can draft contracts, send contracts for signing, add signers, manage templates, and check contract details through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a eSignatures account through Composio's eSignatures MCP server.

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

Also integrate eSignatures with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for eSignatures
  • Configure an AI agent that can use eSignatures as a tool
  • Run a live chat session where you can ask the agent to perform eSignatures operations

What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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

The eSignatures MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your eSignatures account. It provides structured and secure access to your contract templates, contracts, signers, and signing workflows, so your agent can create and send contracts, manage signers, update content, track signing status, and organize templates on your behalf.

  • Contract creation and delivery: Have your agent create contract drafts from templates or Markdown, send them for signature, or send an existing draft when it is ready.
  • Signer management: Let the agent add, update, or remove signers from editable contracts, resend signature requests, and adjust signer contact, delivery, authentication, or redirect details.
  • Template creation and collaboration: Direct your agent to create, duplicate, rename, label, or delete reusable templates, and manage the collaborators who can edit them.
  • Contract and template editing: Instruct your agent to preview and apply exact content changes, update contract placeholder values, and review template or contract Markdown.
  • Signing workflow tracking: Have your agent check contract details, current status, signers, completed field values, and signed documents when available, or withdraw an active unsigned contract.

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:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live eSignatures project
  • Some knowledge of Python or Typescript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
3

Install dependencies

npm install @composio/openai-agents @openai/agents dotenv

Install the Composio SDK and the OpenAI Agents SDK.

4

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

5

Import dependencies

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like eSignatures.
6

Set up the Composio instance

dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
What's happening:
  • dotenv.config() loads your .env file so COMPOSIO_API_KEY and USER_ID are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.
7

Create a Tool Router session

// Create Tool Router session for eSignatures
const session = await composio.create(userId as string, {
  toolkits: ['esignatures'],
});
const mcpUrl = session.mcp.url;

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only esignatures.
  • The router checks the user's eSignatures connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access eSignatures.
  • This approach keeps things lightweight and lets the agent request eSignatures tools only when needed during the conversation.
8

Configure the agent

// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access eSignatures. Help users perform eSignatures operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access eSignatures and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a hostedMcpTool that connects to the MCP server URL we created earlier.
  • The headers object includes the Composio API key for secure authentication with the MCP server.
  • requireApproval: 'never' means the agent can execute eSignatures operations without asking for permission each time, making interactions smoother.
9

Start chat loop and handle conversation

// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
What's happening:
  • The program prints a session URL that you visit to authorize eSignatures.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using run().
  • The responses are printed to the console.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with eSignatures and OpenAI Agents SDK:

import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['esignatures'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access eSignatures. Help users perform eSignatures operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});

Conclusion

This was a starter code for integrating eSignatures MCP with OpenAI Agents SDK to build a functional AI agent that can interact with eSignatures.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

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

Add Contract Signer

Add a signer to an editable contract without automatically sending a signature request.

Add Contract Signers

Add a non-empty list of signers to an editable contract by calling the provider's singular endpoint sequentially in request order.

Add Template Collaborator

Create a name-only collaborator who can edit a template.

Create and Send Contract

Create a contract from a template or from ad-hoc Markdown and immediately send signature requests to its signers.

Create Contract Draft

Create a test or production contract draft from a template or from ad-hoc Markdown, without sending signature requests or otherwise delivering it externally.

Create Template

Create a reusable Markdown contract template.

Delete Contract Signer

Permanently remove a signer from an editable contract.

Delete Template

Permanently delete a template.

Duplicate Template

Duplicate a template with a new title plus optional placeholder replacements.

Get Contract

Get one contract's current status, details, signers, signer field values, and temporary signed-PDF URL when available.

Get Contract Content

Return the Markdown content of one contract.

Get Contract Placeholder Fields

Return the current placeholder replacements for one contract.

Get Template

Get one template's metadata, placeholder keys, and signer-field IDs.

Get Template Content

Return the Markdown content of one template.

Invite Template Collaborator

Invite a collaborator to edit a template.

List Template Collaborators

Return all collaborators who can edit one template.

List Templates

Return all templates available to the connected account.

Preview Contract Content Update

Preview the prospective Markdown from exact find-and-replace edits without mutating the contract.

Preview Template Content Update

Preview the prospective Markdown from exact find-and-replace edits without mutating the template.

Remove Template Collaborator

Remove a collaborator's permission to edit a template.

Resend Sign Request

Resend a signature request to one signer.

Send Draft Contract

Send an existing draft to its signers.

Update Contract Content

Apply exact Markdown find-and-replace edits to a contract.

Update Contract Placeholder Fields

Update selected placeholder replacements on an unsigned contract.

Update Contract Signer

Update selected contact, delivery, authentication, or redirect details for a signer without resending the contract.

Update Template

Update a template's title and/or labels without changing its Markdown content.

Update Template Content

Apply exact Markdown find-and-replace edits to a template.

Withdraw Contract

Irreversibly withdraw an active unsigned contract so it can no longer be signed.

FAQ

Frequently asked questions

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

Yes, you can. OpenAI Agents 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 eSignatures tools.

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

Start with eSignatures.It takes 30 seconds.

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

Start building