Skip to content

DulySigned e-signature

Make contracts from templates, send them for e-signature by email, and track who has signed.

build.protocol_tooling.mcp

Install DulySigned e-signature in your MCP client

DulySigned e-signature is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.

  1. Locate your client's MCP config file.
    • Cursor: ~/.cursor/mcp.json
    • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
    • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
    • VS Code: Settings → Extensions → MCP
    • Windsurf: Settings → MCP Servers
  2. Add DulySigned e-signature to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing mcpServers object.
  3. Restart your client so it picks up the new server.
  4. Verify — ask the assistant to list available tools; DulySigned e-signature's tools should appear.

DulySigned e-signature does not publish an install package in the MCP Registry, so there is no snippet to copy here. Use the connection details from the server's own setup page.

Transport

DulySigned e-signature supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.

streamable-http

Other Model Context Protocol servers in the same space as DulySigned e-signature. Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.

Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.