SmoothSign MCP

The SmoothSign MCP server enables AI assistants to manage electronic signature workflows. It allows users to send PDF documents to specific signers via email, check the real-time signing status of documents, list recent documents, and confirm when signed PDFs have been delivered. It integrates directly with the SmoothSign platform without storing documents locally.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-18Operated by SmoothSign

MCP endpoint (Streamable HTTP)

https://smoothsign.cc/mcp

Vendor documentation

What you can do with it

Send a PDF contract to specific email addresses for electronic signature
Check the current signing status of a document
List recent documents and their statuses
Confirm if a signed PDF has been delivered to all signers

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http smoothsign-mcp https://smoothsign.cc/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add smoothsign-mcp --url https://smoothsign.cc/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable smoothsign-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "smoothsign-mcp": {
      "url": "https://smoothsign.cc/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "smoothsign-mcp": {
      "type": "streamableHttp",
      "url": "https://smoothsign.cc/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start smoothsign-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "smoothsign-mcp": {
      "type": "http",
      "url": "https://smoothsign.cc/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http smoothsign-mcp https://smoothsign.cc/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "smoothsign-mcp": {
      "url": "https://smoothsign.cc/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "smoothsign-mcp": {
      "serverUrl": "https://smoothsign.cc/mcp"
    }
  }
}

See all 2,329

Do you run SmoothSign MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing