Zignature
+
Windsurf

Document Signing in
Windsurf IDE

Connect Zignature to Windsurf's high-performance AI agent. Send NDAs, SOWs, and agreements right from your terminal or chat without context-switching.

Windsurf Native MCP 1.0 57 Tools Included

Quick Integration

Add the Zignature MCP server to your Windsurf configuration in seconds.

1 Locate Config File

Open your Windsurf MCP configuration file:

~/.codeium/windsurf/mcp_config.json

2 Add Zignature Server

Paste the following configuration, replacing YOUR_API_KEY with your token from the Developer Portal:

{
  "mcpServers": {
    "zignature": {
      "serverUrl": "https://app.zignature.io/mcp",
      "headers": { "X-Auth-Token": "YOUR_API_KEY" }
    }
  }
}

3 Restart Windsurf

Restart the IDE to enable the new Zignature tools in your agent sessions.

Windsurf Agent — Document Workflow
You: "I've finished the draft for the new SOW. Send it to the client for review and signature."
Windsurf: "I'll upload the SOW draft and send it via Zignature..."
✓ SOW uploaded and sent to client@example.com
Awaiting signature. Tracking ID: sub_sow_9912

Designed for Agentic Workflows

Windsurf's advanced agent can do more than just follow instructions—it can manage your entire document pipeline.

  • Automated followup reminders for unsigned documents.
  • Bulk sending project updates to all stakeholders.
  • Intelligent template selection based on file context.

Windsurf Integration FAQ

How do I add Zignature to Windsurf?

Open your ~/.codeium/windsurf/mcp_config.json file and add the Zignature server entry as shown in our setup guide above.

What is the MCP config format for Windsurf?

Windsurf requires a serverUrl field for HTTP-based MCP servers and optional headers for authentication.

Does Windsurf support all 57 Zignature tools?

Yes! Once connected, all 57 tools from our MCP server—from template management to deal desk analytics—are available to the Windsurf agent.

More AI Developer Integrations