How do I find my eSign App ID and Secret?

Log in to the [eSign Open Platform](https://open.esign.cn/), create a new application, and you will find your App ID and App Secret in the application credentials section.

Can I retrieve the signing URL for a participant?

Yes. Use the `get_execute_url` tool with the flow ID and the signer's account ID. Your agent will retrieve the unique URL where the participant can perform the signature.

Is it possible to download the signed documents?

Yes! Once a sign flow is completed, you can use the `download_docs` tool to retrieve temporary download links for all documents included in that flow.

eSign (e签宝) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: eSign (e签宝)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to eSign (e签宝) through Vinkius, pass the Edge URL in the `mcps` parameter and every eSign (e签宝) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="eSign (e签宝) Specialist",
    goal="Help users interact with eSign (e签宝) effectively",
    backstory=(
        "You are an expert at leveraging eSign (e签宝) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in eSign (e签宝) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About eSign (e签宝) MCP Server

Empower your AI agent to orchestrate your digital agreement lifecycle with eSign (e签宝), the premier electronic signature platform in China. By connecting eSign to your agent, you transform complex contract workflows and document signing into a natural conversation. Your agent can instantly list your sign flows, create new signature tasks, manage document templates, and even retrieve signing URLs for participants without you ever needing to navigate the comprehensive eSign portal. Whether you are managing high-volume employee contracts or complex B2B agreements, your agent acts as a real-time legal operations assistant, keeping your documents secure and your business moving.

When paired with CrewAI, eSign (e签宝) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call eSign (e签宝) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Sign Flow Orchestration — Create and manage digital signature workflows with full support for documents and signers.
Template Management — Browse predefined document templates to accelerate your contract production.
Signature Tracking — Monitor the real-time status of active sign flows and retrieve execution URLs for participants.
Document Control — Add PDF documents to signature tasks and retrieve download links for completed agreements.
Organization Insights — Retrieve high-level information about your enterprise eSign account and authorization status.

The eSign (e签宝) MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect eSign (e签宝) to CrewAI via MCP

Follow these steps to integrate the eSign (e签宝) MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from eSign (e签宝)

Why Use CrewAI with the eSign (e签宝) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with eSign (e签宝) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

eSign (e签宝) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the eSign (e签宝) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries eSign (e签宝) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries eSign (e签宝), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain eSign (e签宝) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries eSign (e签宝) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

eSign (e签宝) MCP Tools for CrewAI (10)

These 10 tools become available when you connect eSign (e签宝) to CrewAI via MCP:

add_docs

Add documents to flow

add_signers

Add signers to flow

create_sign_flow

Create a new sign flow

download_docs

Download flow documents

get_execute_url

Get signature URL

get_org_info

Get organization details

get_sign_flow

Get sign flow details

list_sign_flows

List sign flows

list_templates

List sign templates

start_flow

Start sign flow

Example Prompts for eSign (e签宝) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with eSign (e签宝) immediately.

"List all active signature flows on eSign."

"Get the signing URL for account 'acc-8821' in flow 'flow-9920'."

"Show me all available document templates."

Troubleshooting eSign (e签宝) MCP Server with CrewAI

Common issues when connecting eSign (e签宝) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

eSign (e签宝) + CrewAI FAQ

Common questions about integrating eSign (e签宝) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.