Windsurf MCP signing with Atlas

Every hour in a competitor sandbox is an hour not shipping. Windsurf MCP signing with Atlas should take minutes: one config block, one test envelope, one review click.

Windsurf follows the same HTTP MCP pattern as Cursor and Cline. Bearer API key in local config. Endpoint https://atlaswork.ai/api/mcp.

> Share: "Same Atlas MCP config as Cursor. Windsurf agents send from chat."

Config shape

Windsurf MCP server entries accept HTTP transport with headers. Add Atlas to your Windsurf MCP settings (global or project-level depending on your build):

{
  "mcpServers": {
    "atlas": {
      "url": "https://atlaswork.ai/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Copy YOUR_API_KEY from Atlas dashboard Settings after signup. Reload Windsurf so tools register.

If your Windsurf build uses a different key name for the servers object, keep the URL and Authorization header identical. Atlas only requires a valid Bearer token.

First test envelope

Prompt:

Using Atlas, prepare a test NDA for signature.

Signer: my-email@company.com, Test Signer, Customer.

I have a PDF on disk. Request an upload link.

Walk upload session → review → Send → sign on your phone. That validates OAuth-free auth, field detection, and email delivery before you touch client docs.

When to use upload session vs URL

Windsurf agents cannot assume drag-and-drop file forwarding works. Default to upload session for repo-local files.

Lifecycle tools worth knowing

After create, most teams loop on:

• check_signing_status for lightweight polls
• remind_signer when someone stalls
• void_envelope when terms change mid-flight
• extract_contract_data after sign for CRM updates

Full table in MCP e-signature server.

Windsurf and Cursor together

Teams often run both editors. Share one Atlas API key or create separate keys per machine from dashboard Settings. Idempotency on write tools prevents duplicate sends when an agent retries.

REST when chat is not enough

Scheduled reminders from a cron job should call REST, not MCP. Example status poll:

curl https://atlaswork.ai/api/envelope/$ENVELOPE_ID/status \
  -H "Authorization: Bearer $ATLAS_API_KEY"

See e-signature API guide.

Windsurf-specific reload steps

After editing MCP config, fully reload the Windsurf window. Partial hot reload sometimes leaves stale tool lists. Start a new agent thread and ask "list available Atlas tools" as a smoke test before client work.

Team rollout checklist

1. One engineer validates upload session plus review Send on a test PDF.
2. Document the prompt template in your internal wiki.
3. Share API key rotation policy.
4. Pin a template for the contract type you send most often.

Comparing Windsurf to Claude Desktop on signing

Windsurf uses API keys like Cursor. Claude Desktop uses OAuth. If your team mixes both, use Windsurf for repo-adjacent prep and Claude Desktop for legal chat with external counsel. Same Atlas account, same templates.

Troubleshooting stalls

If check_signing_status shows pending for days, ask Windsurf to remind_signer. If terms changed, void_envelope and create a fresh envelope rather than resending stale PDFs.

Integration with issue trackers

Paste envelope id into Linear or Jira when Windsurf prepares a contract from a ticket. Status polls close the loop without switching to email search.

Performance expectations

First create on a large PDF may take seconds while detection runs. Agents should tell users to wait for review_url before promising signers a timeline.

Long-running deals

Windsurf agents can store envelope ids in a signing-state.json file at repo root for multi-week closes. Poll status when the branch updates. Clear the file when status reaches signed.

Vendor security review

Security teams ask where PDFs live. Atlas stores documents in encrypted object storage with audit logs on Send and sign events. Include Atlas SOC2 request in vendor packet when required.

FAQ

Does Atlas accept PDF and DOCX?

Yes. Upload either format when you create an envelope. DOCX files become PDF before anyone signs.

How do I sign in?

Use a Bearer API key from your dashboard settings. MCP connectors in ChatGPT and Claude use OAuth instead.

When do credits get used?

One credit per send, not per upload. You get five free sends when you sign up.

Where should I start?

/mcp and API reference.

Related reading

• MCP setup
• E-signature API guide
• MCP electronic signatures