How to Use the eSign (e签宝) MCP in LlamaIndex

Q: How do I retrieve signing URLs dynamically in LlamaIndex?

After starting a contract run with startflow, your agent calls getexecuteurl to fetch the active signing link and presents it to the user.

Q: Can I download completed contracts into my vector index?

Yes. The agent checks if the flow is complete, calls downloaddocs to get the signed PDFs, and indexes the document text for future search.

Index, query, and trigger eSign (e签宝) contract actions based on your structured LlamaIndex knowledge bases.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect eSign (e签宝) MCP to LlamaIndex

Create your Vinkius account to connect eSign (e签宝) to LlamaIndex 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 eSign (e签宝) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Ground signature actions in real data

LlamaIndex excels at connecting live data to agent actions. By exposing tools like `list_sign_flows` and `get_sign_flow` to your index, the agent can query the status of active contracts and ground its decisions in actual eSign (e签宝) records. Instead of guessing if a contract is complete, your agent checks the index, verifies the status, and only triggers `download_docs` when the document is fully executed.

RAG-driven contract setup via LlamaIndex

This MCP Server lets your LlamaIndex agent use semantic search to find the right templates. The agent queries your knowledge base for standard terms, calls `list_templates` to find the matching layout, and uses `create_sign_flow` to start the transaction. You don't need to manually map user requests to template IDs. The agent handles the lookup and execution based on the context retrieved from your indexed files.

Index organization profiles with this MCP Server

Keep your business records aligned by indexing organization details directly. The agent can call `get_org_info` to retrieve official registration data and use it to populate signer details via `add_signers` before starting the flow. This eliminates manual entry errors when setting up corporate signers. The agent cross-references your internal database with eSign (e签宝) records to ensure legal compliance.

Setup guide

Set up eSign (e签宝) MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all eSign (e签宝) MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to eSign (e签宝) tools.",
)
response = await agent.run("List recent eSign (e签宝) data")

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 eSign (e签宝). 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 eSign (e签宝) 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 eSign (e签宝) MCP in LlamaIndex

You load the tool list from the MCP Server and pass them to your agent. The agent calls `list_sign_flows` and indexes the metadata into your vector store for easy querying.

Yes. The agent uses semantic search to match user intent to your templates retrieved via `list_templates`, then triggers `create_sign_flow` with the correct ID.

After starting a contract run with `start_flow`, your agent calls `get_execute_url` to fetch the active signing link and presents it to the user.

Yes. The agent checks if the flow is complete, calls `download_docs` to get the signed PDFs, and indexes the document text for future search.

Your contract metadata, signer names, and phone numbers are processed locally inside the Vinkius secure sandbox. The MCP Server never transmits your signing keys or document contents to external servers.

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