Connect Cursor and other clients with a key

Any client that speaks MCP over streamable HTTP and can send a bearer header can use the connector with a key. There is nothing Adapt Leads specific to build.

Before you start

Create a key. See Keys, sign-in and permissions. A default key can search the book, read one record and read your account. For more, see the permission table in Permissions and limits.

Cursor

Put this in ~/.cursor/mcp.json, or in .cursor/mcp.json at the root of one project:

{
  "mcpServers": {
    "adaptleads": {
      "url": "https://mcp.adaptleads.co.uk",
      "headers": { "Authorization": "Bearer adl_your_key" }
    }
  }
}

Do not commit that file with a real key in it.

Any other client

Check it works

Ask your client to list the tools. You should see all of them, including ones your key cannot call. Call my_account to confirm the key works, and read today in the answer to see your call and row counts. A tool the key may not use returns forbidden.

What happens next

A key lasts 365 days unless you chose otherwise. Revoke it from the Stack page at any time, and the next call gets a 401.