How to Use the DocuSign MCP in CrewAI

Q: Can a CrewAI agent autonomously send a DocuSign contract using MCP?

Yes, you can assign the sendenvelope tool to a specialized sending agent. The agent reviews the contract details prepared by other crew members and executes the tool to dispatch the document.

Q: Can my crew locate specific signing folders?

Yes, your agents can call listfolders to scan your account directory structure. This allows them to organize completed contracts or retrieve documents from specific departments.

Deploy a multi-agent crew to autonomously draft, track, and void DocuSign envelopes without human intervention.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect DocuSign MCP to CrewAI

Create your Vinkius account to connect DocuSign to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup DocuSign with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Delegate contract tracking using `list_recipients`

The `list_recipients` tool exposes who has signed and who is holding up a contract. In a CrewAI setup, your dedicated auditor agent runs this tool to monitor pending signatures and pass the bottlenecks to a coordinator agent. Because your agents share memory, the coordinator knows exactly which recipient needs a reminder. The crew handles follow-ups autonomously, keeping your deal pipeline moving without manual tracking.

Search agreement histories using this MCP Server

The `search_envelopes` tool lets your agent find specific contracts using text search queries. Your research agent uses this tool to locate historical agreements when analyzing client accounts. This MCP Server connection allows your crew to pull old terms and compare them with new proposals. Your agents make decisions based on actual contract data instead of guessing.

Manage templates dynamically with `list_templates`

The `list_templates` tool retrieves all available document layouts from your account. Your operations agent uses this list to select the correct document format before handing the task to a sending agent. This division of labor prevents errors in document preparation. The operations agent matches the client request to the template ID, and the sending agent executes the delivery.

Setup guide

Set up DocuSign MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke DocuSign tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="DocuSign Analyst",
    goal="Access and analyze DocuSign data via MCP.",
    backstory="Expert analyst with direct DocuSign access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent DocuSign transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="DocuSign Analyst",
        goal="Access and analyze DocuSign data via MCP.",
        backstory="Expert analyst with direct DocuSign access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent DocuSign transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DocuSign. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect DocuSign now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about DocuSign MCP in CrewAI

Yes, you can assign the `send_envelope` tool to a specialized sending agent. The agent reviews the contract details prepared by other crew members and executes the tool to dispatch the document.

If a contract is sent with incorrect parameters, a monitoring agent can invoke `void_envelope` to cancel it. The crew then analyzes the error, corrects the input data, and triggers a new sending sequence.

You use the MCPServerHTTP class from CrewAI's tool library to apply an MCP tool filter. This lets you restrict your research agent to `list_envelopes` while reserving `send_envelope` for your executive agent.

Yes, your agents can call `list_folders` to scan your account directory structure. This allows them to organize completed contracts or retrieve documents from specific departments.

Your template IDs and envelope configurations are handled via secure, direct API calls mediated by the Vinkius MCP gateway. The platform enforces strict network isolation, preventing your sensitive legal schemas from being exposed to external web environments.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript