Connect Your Assistant

Works on claude.ai and in the Claude desktop app.

1. Open Settings → Connectors.
2. Click Add custom connector.
3. Name it NextSign and paste the server address above.
4. Click Add — no key or password goes in here. Claude discovers the NextSign sign-in on its own.

Custom connectors require a paid plan, and on some plans Developer mode must be switched on first under Settings → Apps & Connectors → Advanced settings.

1. Open Settings → Apps & Connectors.
2. Click Create (or Add custom connector).
3. Name it NextSign, paste the server address above, and pick OAuth as authentication.
4. Save. ChatGPT sends you to the NextSign sign-in described in the next step.

Only needed if you prefer an API key over signing in — for example a shared machine that should always act as one specific key. Requires Node.js installed.

Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "nextsign": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.nextsign.dk/v3/mcp",
        "--header",
        "Authorization:${NEXTSIGN_AUTH}"
      ],
      "env": {
        "NEXTSIGN_AUTH": "Bearer key_YOUR_KEY_HERE"
      }
    }
  }
}

Replace key_YOUR_KEY_HERE with your key, then restart the app. (The env-var indirection is deliberate — a space inside --header arguments gets split by the bridge.)

Any MCP client that supports remote servers over Streamable HTTP works. Two ways in:

• OAuth (preferred): point the client at the server address and let it run the standard MCP authorization flow. Registration is dynamic — no pre-shared client id needed.
• API key: if the client can send custom headers, set Authorization: Bearer key_… with a key from Authorization.

Clients that only speak the older SSE transport cannot connect.