SignNow MCP Server Logo

SignNow MCP Server

Official

https://github.com/signnow/sn-mcp-server MCP server for SignNow e-signature: templates, invites, emb...

18 views
0 installs
Updated Jan 30, 2026
Not audited
Tools I Recommend
https://github.com/signnow/sn-mcp-server MCP server for SignNow e-signature: templates, invites, embedded signing/editor, status & downloads.
  1. Click the "Install Now" button and open the FastMCP connection interface — you will enter the environment variable values there.

  2. Create (or sign in to) your SignNow account.

    • If you don’t have an account, sign up at SignNow to get a developer account first. (signnow.com)
  3. Open the SignNow API / Applications dashboard (the “API” or plug icon in your SignNow account).

    • In the dashboard click “Add App” (or open an existing app). The dashboard shows your app’s Client ID, Client Secret and the Basic Authorization Token (a.k.a. Basic token). (signnow.com)
  4. Copy the Basic Authorization Token and paste it into the FastMCP interface as SIGNNOW_API_BASIC_TOKEN.

    • Field name to set in FastMCP: SIGNNOW_API_BASIC_TOKEN. (signnow.com)
  5. Enter your SignNow account credentials in FastMCP:

    • SIGNNOW_USER_EMAIL — the email you registered with SignNow.
    • SIGNNOW_PASSWORD — your SignNow account password.
    • (These let the MCP server authenticate on your behalf for typical desktop/dev flows.) (blog.signnow.com)
  6. (Optional) If you prefer to provide a short-lived access token directly instead of user/password, generate an access (Bearer) token and set SIGNNOW_TOKEN:

    • Use the Basic token plus your account credentials to request a bearer token:
      curl -X POST "https://api.signnow.com/oauth2/token"
      -H "Authorization: Basic "
      -F "username="
      -F "password="
      -F "grant_type=password"
      -F "scope=*"
    • The response contains an access token (Bearer) you can place as SIGNNOW_TOKEN in FastMCP. Note: access tokens expire (≈30 days), so the server flow using Basic token + user/password is usually preferred for auto-refresh. (signnow.com)
  7. (Optional / advanced) If you intend to run the server in OAuth mode or in production:

    • From the same API dashboard copy the Client ID and Client Secret and set:
      • SIGNNOW_CLIENT_ID
      • SIGNNOW_CLIENT_SECRET
    • Also supply any OAUTH_RSA_PRIVATE_PEM / OAUTH_JWK_KID if you use the server’s OAuth features. (signnow.com)
  8. Save the environment variables in the FastMCP connection UI and install/apply them via the Install flow.

  9. Test the MCP server connection:

    • For local/dev use the recommended fields (SIGNNOW_USER_EMAIL, SIGNNOW_PASSWORD, SIGNNOW_API_BASIC_TOKEN) so the server can obtain and refresh access tokens automatically.
    • Start or reconnect the MCP and call a simple tool (for example list_all_templates) to verify authentication and connectivity. (blog.signnow.com)
  10. Notes / reminders:

  • Basic Authorization Token is created per-app in the SignNow API dashboard; keep it secret. (signnow.com)
    - Access tokens returned from /oauth2/token expire (about 30 days); either let the MCP manage refresh via credentials or update SIGNNOW_TOKEN periodically. (signnow.com)

Quick Start

View on GitHub

More for API Development

View All →

More for Developer Tools

View All →

Similar MCP Servers

Report Issue

Thank you! Your issue report has been submitted successfully.