How to integrate Dropbox sign MCP with LlamaIndex

This guide walks you through connecting Dropbox sign to LlamaIndex using the Composio tool router. By the end, you'll have a working Dropbox sign agent that can send nda for signature to new hire, get status of recent signature requests, download signed contract from last week through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Dropbox sign account through Composio's Dropbox sign MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Dropbox sign logoDropbox sign
Api KeyOauth2

Dropbox Sign is an electronic signature platform for sending, signing, and managing legally binding documents online. It streamlines business workflows by making signature collection fast, secure, and effortless.

56 Tools

Introduction

This guide walks you through connecting Dropbox sign to LlamaIndex using the Composio tool router. By the end, you'll have a working Dropbox sign agent that can send nda for signature to new hire, get status of recent signature requests, download signed contract from last week through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Dropbox sign account through Composio's Dropbox sign MCP server.

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

Also integrate Dropbox sign 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 Dropbox sign
  • Connect LlamaIndex to the Dropbox sign MCP server
  • Build a Dropbox sign-powered agent using LlamaIndex
  • Interact with Dropbox sign 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 Dropbox sign MCP server, and what's possible with it?

The Dropbox sign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dropbox Sign account. It provides structured and secure access to your e-signature workflows, so your agent can prepare signature requests, manage documents, track signing progress, and automate agreement workflows on your behalf.

  • Automated signature requests: Have your agent create, send, and manage legally binding signature requests to one or multiple recipients, streamlining document approval processes.
  • Template-based document preparation: Let your agent generate documents from templates, pre-fill fields, and quickly send out repeat agreements without manual editing.
  • Status tracking and reminders: Ask your agent to monitor the progress of signature requests, check who has signed, and send automated reminders to outstanding signers as needed.
  • Secure document storage and retrieval: Effortlessly fetch completed, pending, or archived documents, download signed agreements, and keep your workflow organized and compliant.
  • Audit trails and activity logs: Access detailed audit trails and event histories for every document, so you can maintain compliance and always know who did what, and when.

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

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 Dropbox sign account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Dropbox sign

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
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

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 Dropbox sign access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called dropbox sign_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

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

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["dropbox_sign"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Dropbox sign actions." ,
    llm,
    tools,
  });

  return agent;
}

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, dropbox sign)
  • 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 Dropbox sign tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Dropbox sign
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Dropbox sign tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

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 Dropbox sign
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Dropbox sign, then start asking questions.

Complete Code

Here's the complete code to get you started with Dropbox sign and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["dropbox_sign"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Dropbox sign actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Dropbox sign to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Dropbox sign 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.
TOOLS

Supported Tools

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

Invite User to Team

Tool to invite a user to your Team.

Add User to Template

Tool to grant a specified account access to a template.

Bulk create embedded signature request with template

Tool to create a BulkSendJob for embedded templated signature requests.

Bulk send with template

Tool to create a BulkSendJob for templated signature requests.

Cancel Signature Request

Cancels an incomplete signature request.

Create Dropbox Sign Account

Tool to create a new Dropbox Sign account associated with a specified email address.

Create API App

Tool to create a new Dropbox Sign API App.

Create Embedded Signature Request

Tool to create an embedded signature request for signing in an iFrame.

Create Embedded Signature Request With Template

Tool to create an embedded signature request based on a template.

Create Embedded Template Draft

Tool to create an embedded template draft.

Create Embedded Unclaimed Draft with Template

Tool to create an embedded unclaimed draft using saved templates.

Create Report

Request creation of CSV report(s) for a specified date range.

Create Template

Tool to create a reusable template for document signing workflows.

Create Unclaimed Draft

Tool to create an unclaimed draft that can be claimed via a unique URL.

Delete API App

Tool to delete an API App from your Dropbox Sign account by its client_id.

Delete Fax

Tool to delete a fax from the system by its fax_id.

Delete Template

Permanently deletes a template from your Dropbox Sign account by its template_id.

Download Signature Request Files

Download files for a signature request as PDF (merged) or ZIP (individual documents).

Edit and Resend Embedded Signature Request

Tool to edit and resend an embedded signature request.

Edit and Resend Signature Request

Edits and resends an existing non-templated signature request with updated documents, signers, or settings.

Edit and Resend Unclaimed Draft

Tool to edit and resend a previously created unclaimed draft.

Edit and Resend Embedded Signature Request With Template

Tool to edit and resend an embedded signature request using templates.

Get Dropbox Sign Account

Retrieves detailed information about a Dropbox Sign account including quotas, payment status, and settings.

Get API App

Tool to retrieve information about an API App by its client ID.

Get Bulk Send Job

Tool to retrieve the status of a bulk send job.

Get Current Team Membership

Tool to get the current team membership status and details.

Get Embedded Sign URL

Retrieves an embedded signing URL for a specific signer's signature.

Get Embedded Template Edit URL

Tool to generate an edit URL for embedded template editing.

Get Available Fax Line Area Codes

Tool to retrieve available fax line area codes for a given country, state/province, and city.

Get Signature Request

Retrieves the current status and complete details of a signature request by ID.

Get Signature Request Files as Data URI

Tool to download signature request files as a base64-encoded data URI.

Get Signature Request Files as File URL

Retrieves a copy of the current documents and returns a JSON object with a URL to the file (PDFs only).

Get Team Info

Retrieves information about a Dropbox Sign team, including team name, member count, and sub-team count.

Get Template

Tool to return the specified template.

Download Template Files

Tool to download documents associated with a template.

Get Template Files as Data URI

Tool to retrieve template documents as base64-encoded data URI.

Get Template Files as File URL

Tool to retrieve a copy of template documents and return a JSON object with a URL to the file (PDFs only).

List API Apps

Tool to list API Apps.

List Bulk Send Jobs

Tool to list bulk send jobs.

List Faxes

Tool to list faxes and their properties.

List Fax Lines

Tool to list fax lines and their properties.

List Signature Requests

Tool to list signature requests.

List Sub-Teams

Lists all sub-teams belonging to a parent team with pagination support.

List Team Members

Lists all members and their roles for a specific team.

List All Teams

Lists all Dropbox Sign teams accessible to the authenticated user, including the current team and its sub-teams.

List Templates

Tool to list templates.

Generate OAuth Authorization URL

Tool to generate an OAuth authorization URL.

Release Signature Request Hold

Release a held signature request to send it to signers.

Remove User from Template

Tool to remove an account's access to a template.

Send Signature Request

Tool to create and send a new signature request with documents.

Send Request Reminder

Sends an email reminder to a signer about a pending signature request.

Update Dropbox Sign Account

Tool to update Dropbox Sign account properties and settings.

Update API App

Tool to update an existing API App in Dropbox Sign.

Update Signature Request

Updates the email address and/or name for a specific signer on a signature request.

Update Template Files

Tool to update files for an existing template.

Verify Dropbox Sign Account

Tool to verify whether a Dropbox Sign account exists for the given email.

FAQ

Frequently asked questions

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

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 Dropbox sign tools.

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

Start with Dropbox sign.It takes 30 seconds.

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

Start building