Add Zignature to Cursor's MCP client and send NDAs, SOWs, and license agreements right from your IDE. 57 tools for the entire document lifecycle.
Connect Cursor to Zignature in less than 2 minutes using our MCP server.
Log in to the Zignature Developer Portal to generate your unique API token.
Open Developer PortalAdd the Zignature MCP server to your Cursor configuration. You can edit your ~/.cursor/mcp.json file or use the simpler streamable-http format:
{
"mcpServers": {
"zignature": {
"url": "https://app.zignature.io/mcp",
"headers": { "X-Auth-Token": "YOUR_API_KEY" }
}
}
}
{
"mcpServers": {
"zignature": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-fetch"],
"env": {
"MCP_SERVER_URL": "https://app.zignature.io/mcp",
"MCP_AUTH_HEADER": "X-Auth-Token YOUR_API_KEY"
}
}
}
}
Cursor now has access to 57 Zignature tools. Try asking Cursor to "Send the NDA template to Alice".
Send software license agreements or CLA to contributors while you're deploying your latest build.
Send SOWs and project contracts without leaving your code. Keep your focus where it belongs.
Invite new developers to your team or send contractor NDAs instantly through Cursor chat.
Open Cursor Settings → Features → MCP. Click "Add Server", name it "zignature", and provide the URL: https://app.zignature.io/mcp along with your API key in the headers.
The Model Context Protocol (MCP) was introduced in Cursor version 0.40. Please ensure your IDE is updated to the latest version to use these features.
No. While Cursor Pro offers more AI features, the ability to connect MCP servers is available to all users.
Cursor supports both direct HTTP MCP servers and stdio-based servers. We recommend the direct HTTP URL for the best performance and easiest setup.
Yes! Cursor's "Agent" mode is particularly powerful with Zignature. It can chain multiple tools together, like listing your templates, choosing the right one, and sending it to multiple recipients.