Skip to content

MCP Connector

The Aoexl MCP Connector lets you use Claude Desktop, Cursor, or any MCP-compatible AI client to create signing requests, check status, send reminders, and manage templates — all from natural language, without opening the Aoexl dashboard.

How It Works

The connector runs as a Cloudflare Worker at mcp.aoexl.com. Each customer authenticates with a personal API key scoped to their Aoexl account. All 10 signing tools are available once connected.

Claude Desktop  →  mcp.aoexl.com  →  Aoexl (your account only)

1. Generate an API Key

  1. Sign into aoexl.com and go to Settings → MCP API Keys
  2. Give the key a label (e.g. "My Laptop") and click Generate key
  3. Copy the key immediately — it is shown once and never stored in plaintext

Your key looks like: aok_live_a1b2c3d4...

2. Connect Claude Desktop

Open (or create) your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the Aoexl server entry:

json
{
  "mcpServers": {
    "aoexl-sign": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.aoexl.com/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Replace YOUR_API_KEY with the key you copied. The Settings page also shows this snippet pre-filled — just copy and paste.

Restart Claude Desktop. You should see aoexl-sign appear in the connected tools list.

3. Connect Cursor

In Cursor, go to Settings → MCP and add a new server with the same config above.

Available Tools

Once connected, the following tools are available to your AI client:

ToolWhat it does
create_signing_requestCreate a hosted signing link, optionally email the signer
get_signing_request_statusCheck request and signer session lifecycle state
list_signing_requestsList recent requests with optional status/query filters
send_signing_reminderResend a pending invite email
cancel_signing_requestCancel a pending request
duplicate_signing_requestClone a request into a fresh signing flow
reopen_signing_requestReopen a completed, cancelled, or expired request
list_templatesList your saved document templates
create_request_from_templateStart a signing flow from a saved template
get_audit_artifactsRetrieve the signed PDF and certificate URLs

Example Prompts

Once connected, you can ask Claude things like:

"Send the NDA to jane@example.com for signing. Use the NDA template."

"What's the status of my last 5 signing requests?"

"Remind everyone who hasn't signed the Q2 contractor agreement yet."

"Cancel the request I sent to john@example.com yesterday."

"Get me the signed PDF for token abc-123."

Manage Keys

Go to Settings → MCP API Keys to:

  • See all active keys (label, prefix, created date, last used)
  • Revoke any key instantly — it stops working on the next request
  • Generate additional keys for different machines or team members

Revoked keys cannot be restored. Generate a new one if needed.

Security

  • API keys are stored as SHA-256 hashes — the plaintext is never saved to the database
  • Each key is scoped strictly to your account — no access to other users' data
  • The mcp.aoexl.com endpoint requires a valid key for every request
  • Revoke a key immediately if it is exposed or no longer needed

Troubleshooting

"Invalid or revoked API key" — The key may have been revoked or miscopied. Generate a new one from Settings.

Claude doesn't show aoexl-sign tools — Restart Claude Desktop after editing the config file. Make sure npx is available in your shell (node must be installed).

Tools appear but calls fail — Check that your Aoexl account is active and your signing quota is not exhausted (visible in Settings).

Built for product, engineering, and operations teams shipping PDF signing flows.