
BoldSign MCP Server
The BoldSign MCP Server connects Large Language Models (LLMs) to the BoldSign API, enabling AI-powered agents to automate electronic signature workflows, manage...
Integrate and automate electronic contract workflows with FlowHunt’s eSignatures MCP Server, enabling AI-driven creation, management, and collaboration on digital contracts and templates.
The eSignatures MCP Server connects AI assistants with the eSignatures platform to streamline and automate electronic signature workflows. By integrating this server, developers and AI agents can interact programmatically with eSignatures.com, enabling advanced operations such as creating, managing, and sending contracts, handling templates, and managing collaborators. This connection allows for seamless automation of contract lifecycle processes, including drafting, reviewing, sending, and tracking contracts and templates, directly from AI-driven workflows. The server plays a crucial role in enhancing productivity by facilitating tasks like database queries, file management, and API interactions related to electronic signatures, empowering developers to build robust contract management solutions.
No explicit prompt templates are listed in the repository or documentation.
No explicit resource primitives are documented in the repository or README.
No setup instructions for Windsurf are provided in the repository.
~/Library/Application Support/Claude/claude_desktop_config.json
; on Windows, edit %APPDATA%/Claude/claude_desktop_config.json
."mcpServers": {
"mcp-server-esignatures": {
"command": "uvx",
"args": [
"mcp-server-esignatures"
],
"env": {
"ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token"
}
}
}
No setup instructions for Cursor are provided in the repository.
No setup instructions for Cline are provided in the repository.
Store your secret token securely using environment variables:
"env": {
"ESIGNATURES_SECRET_TOKEN": "your-esignatures-api-secret-token"
}
Using MCP in FlowHunt
To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:
Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:
{
"mcp-server-esignatures": {
"transport": "streamable_http",
"url": "https://yourmcpserver.example/pathtothemcp/url"
}
}
Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “mcp-server-esignatures” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.
Section | Availability | Details/Notes |
---|---|---|
Overview | ✅ | |
List of Prompts | ⛔ | No explicit prompt templates found |
List of Resources | ⛔ | No explicit resource primitives found |
List of Tools | ✅ | 13 tools for contracts, templates, collaborators |
Securing API Keys | ✅ | Use ESIGNATURES_SECRET_TOKEN in environment |
Sampling Support (less important in evaluation) | ⛔ | Not mentioned |
Based on the tables above, the eSignatures MCP Server is well-documented regarding its tools and setup for Claude but lacks explicit information on prompts, resources, and Roots/Sampling support. Its tooling and authentication are clear, but broader MCP features could be better covered.
This MCP server is robust for contract and template management but would benefit from more explicit resource/prompt documentation and broader setup instructions. Rating: 6/10 for overall completeness and developer readiness.
Has a LICENSE | ✅ (MIT) |
---|---|
Has at least one tool | ✅ |
Number of Forks | 8 |
Number of Stars | 15 |
The eSignatures MCP Server integrates AI agents with eSignatures.com, enabling programmatic automation of contract drafting, management, sending, template handling, and collaboration—streamlining end-to-end electronic signature workflows.
It provides 13 tools for contract and template operations: create, query, withdraw, delete, and list contracts; create, update, query, delete, and list templates; and manage template collaborators.
Store your API secret token as an environment variable (e.g., ESIGNATURES_SECRET_TOKEN) in your MCP configuration to prevent accidental exposure of sensitive data.
Yes! Add the MCP component to your FlowHunt workflow, provide the server details, and your AI agents will gain access to all contract and template management functionalities.
Automate contract drafting and sending, manage templates, control the contract lifecycle, enable collaborative editing, and handle contracts in bulk—all from your AI-powered flows.
Automate your digital signature processes and contract management with FlowHunt's eSignatures MCP Server for enhanced productivity and seamless integration with your AI agents.
The BoldSign MCP Server connects Large Language Models (LLMs) to the BoldSign API, enabling AI-powered agents to automate electronic signature workflows, manage...
The Email MCP Server for FlowHunt bridges AI assistants with email systems, enabling automated email composition, attachment searching, and streamlined communic...
The Markitdown MCP Server bridges AI assistants with markdown content, enabling automated documentation, content analysis, and markdown file management for enha...