How to Use the Yousign MCP in CrewAI

Q: How can I initiate a signature process with Yousign and CrewAI?

An agent starts by calling createsignaturerequest. Once that's done, the team can collaborate to define participants using addsignertorequest and attach files via adddocumenttorequest.

Q: Can CrewAI check the status of a request with Yousign?

Yep. An agent calls getsignaturerequest to get the current state. Another can follow up by calling listsignaturerequests to see if there are other documents needing attention.

Q: What tools handle contact data for Yousign and CrewAI?

The system uses createyousigncontact and listyousigncontacts. These functions keep the agent's address book current, making it easy to assign roles without manual input.

Build autonomous signing operations using Yousign MCP Server with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Yousign MCP to CrewAI

Create your Vinkius account to connect Yousign 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 Yousign with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Orchestrate Signature Requests Across Agents

You can assign one agent to handle the setup by calling `create_signature_request`. Another specialized agent can then be assigned the task of adding necessary documents via `add_document_to_request`, ensuring the operation is fully documented. The shared memory mechanism allows these agents to pass context seamlessly, making the workflow highly reliable.

Monitor and Verify Signature Status

One agent can monitor progress by repeatedly calling `get_signature_request`. A second agent can then be tasked with fetching the evidence link using `get_audit_trail_link` once the status is 'completed'. This role-based specialization ensures that verification steps only run when appropriate, saving computational cycles.

Manage and Clean Up Draft Requests

If a signing process stalls or needs to be restarted, agents can collaborate. One agent might call `delete_signature_request` if the document was never needed, while another uses `list_signature_requests` to confirm all drafts are accounted for. This ability to manage the lifecycle of requests autonomously prevents system clutter.

Setup guide

Set up Yousign 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 Yousign tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Yousign 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="Yousign Analyst",
        goal="Access and analyze Yousign data via MCP.",
        backstory="Expert analyst with direct Yousign access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Yousign 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 Yousign. 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 Yousign 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 Yousign MCP in CrewAI

An agent starts by calling `create_signature_request`. Once that's done, the team can collaborate to define participants using `add_signer_to_request` and attach files via `add_document_to_request`.

Yep. An agent calls `get_signature_request` to get the current state. Another can follow up by calling `list_signature_requests` to see if there are other documents needing attention.

The system uses `create_yousign_contact` and `list_yousign_contacts`. These functions keep the agent's address book current, making it easy to assign roles without manual input.

It does. You can get overall organizational context by calling `get_workspace_details`, which provides the necessary metadata for agents to operate within defined boundaries.

The server touches signature request metadata, including participant details and document IDs. When using CrewAI, make sure that the agent responsible for calling `get_workspace_details` only handles necessary account information.

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