Connect Cursor to eContract

Connect eContract to Cursor so its agent can prepare and send contracts from the editor.

Sign in with OAuth

Recommended for personal use: you sign in once and the client keeps the connection alive.

  1. 1Add eContract to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
  2. 2Reload Cursor and, when it asks you to authenticate the server, sign in to eContract in the browser.
~/.cursor/mcp.json
{
  "mcpServers": {
    "econtract": {
      "url": "https://api.econtract.online/mcp"
    }
  }
}

Use an API key

For unattended runs. Create a key, store it in the ECONTRACT_API_KEY environment variable and keep it out of shared files. Create an API key

  1. 1Set the ECONTRACT_API_KEY environment variable to your API key.
  2. 2Use this configuration instead. Cursor reads the key from the environment variable.
~/.cursor/mcp.json
{
  "mcpServers": {
    "econtract": {
      "url": "https://api.econtract.online/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ECONTRACT_API_KEY}"
      }
    }
  }
}

Try it

Once connected, ask your agent in plain language, for example:

  • “Send the attached NDA to [email protected] for signature and give me the signing link.”
  • “Which of my contracts are still waiting for signatures? Remind the signers.”
  • “Check whether the signatures in this PDF are valid and summarise its key terms.”

Agents prepare and send contracts, but they cannot sign or decline for anyone: each signer signs through their own link after confirming a code sent to their email.

These steps follow the official Cursor documentation as of 2026-10. If the menus have changed since, see the documentation below.

Cursor MCP documentation