10 articles tagged “Mcp”. Browse all articles →
A single send_contract tool is the most tempting mistake in agent tool design. Splitting the irreversible half into its own call is what keeps a misread instruction from reaching a counterparty's inbox.
Signvoy ships both an MCP server and a REST API, and they are not competing implementations. Which one fits depends on a single question: is a human present when the contract goes out?
Docusign, PandaDoc, SignNow, BoldSign, SignWell and Signvoy MCP servers compared on authentication, tool count, transport, embedded signing and free-tier access.
Connect Claude to Signvoy's MCP server and send contracts for signature from a conversation. No API key, no plugin — one URL and a consent click.
Model Context Protocol explained for e-signature workflows: what an MCP server is, how it differs from a REST API, and what an AI agent can safely do with your contracts.
Docusign's MCP connector needs an Integration Key, a Client Secret and two redirect URIs before it works. Signvoy needs one URL. A side-by-side comparison.
Static API keys leak, over-scope and never expire. How OAuth 2.1 with Dynamic Client Registration removes the credential from MCP setup entirely — and what it costs to build.
An AI agent that can send contracts is a prompt-injection target. How to bound the damage with tool design — separate create and send, review URLs, destructive annotations and agent attribution.
Add Signvoy's MCP server to Cursor and send contracts for signature without leaving your editor. Project vs global mcp.json, verification, and the workflows worth having.
A working architecture for an agent that drafts and routes contracts: the MCP server for the conversational half, @signvoy/node and webhooks for the deterministic half.
署名の催促をやめよう
Signvoyを使って取引を成立させ、クライアントをオンボーディングし、契約書に署名している数千のチームに参加しましょう — より速く。
クレジットカード不要 · 永久無料プラン · いつでもキャンセル可能
