Connect Claude

Claude registers itself with LeadsAgent. You do not need a client ID. Team and Enterprise workspaces may require an Owner to add the connector first.

1. In Claude, go to Customize → Connectors. Click “+ Add”, then “Add custom connector”.
2. For the name, type LeadsAgent. For the remote MCP server URL, paste the address below, then click “Continue”.
   Remote MCP server URLCopy

   https://leadsagent.io/mcp/v1

3. Review the authentication settings and click “Continue”. Choose “Sign in now”.
4. Keep the default OAuth client option. Leave Request headers empty and click “Add”.
5. A LeadsAgent window opens. Sign in with your LeadsAgent account and approve access.
6. In a chat, click “+” → “Connectors” and switch LeadsAgent on.
7. Team or Enterprise: an Owner goes to Organization settings → Connectors, clicks “Add”, hovers over “Custom”, selects “Web”, and enters the same name and URL. Each member then opens Customize → Connectors, finds LeadsAgent and clicks “Connect”.

Static request-header authentication is beta for a limited set of organizations. Use it only if Claude offers this option for your account.

1. On the LeadsAgent setup page, select “Create an API key”. Name it for this app and set its expiry and limits. Copy it once; it starts with la_.
2. In Claude, open Customize → Connectors → “+ Add” → “Add custom connector”. Name it LeadsAgent, paste the URL and click “Continue” twice.
   Remote MCP server URLCopy

   https://leadsagent.io/mcp/v1

3. Under Authentication, choose “No sign in”.
4. Under Request headers, add X-API-Key and enter your key in Claude. Then click “Add”. Team and Enterprise workspaces need an Owner to add the connector.
   Request headerCopy

   X-API-Key: la_your_key

5. In a chat, click “+” → “Connectors” and switch LeadsAgent on.

The claude command in a terminal.

1. Add LeadsAgent for all your projects. Use --scope project instead to share it through the project’s .mcp.json.
   TerminalCopy

   claude mcp add --transport http --scope user leadsagent https://leadsagent.io/mcp/v1

2. Start sign-in. Or, inside Claude Code, type /mcp, choose leadsagent and choose Authenticate.
   TerminalCopy

   claude mcp login leadsagent

3. A browser opens. Sign in with your LeadsAgent account and approve access.
4. Check it. /mcp shows ✔ Connected.
   TerminalCopy

   claude mcp get leadsagent

1. On the LeadsAgent setup page, select “Create an API key”. Name it for this app and set its expiry and limits. Copy it once; it starts with la_.
2. Set LEADSAGENT_API_KEY in the environment used by this app. Restart the app so it reads the variable. Keep the value out of chats and shared files.
   TerminalCopy

   LEADSAGENT_API_KEY

3. Merge this server into your project’s .mcp.json. Claude Code fills in ${LEADSAGENT_API_KEY} from the environment, so the key stays out of the file.
   .mcp.json · projectCopy

   {
     "mcpServers": {
       "leadsagent": {
         "type": "http",
         "url": "https://leadsagent.io/mcp/v1",
         "headers": {
           "X-API-Key": "${LEADSAGENT_API_KEY}"
         }
       }
     }
   }

4. Check it. /mcp shows ✔ Connected.
   TerminalCopy

   claude mcp get leadsagent

The Code tab of the Claude desktop app. It reads the same configuration as the terminal.

1. Easiest: add LeadsAgent once in Claude under Customize → Connectors (see the Claude connector page). Connectors from your Claude account show in the Code tab.
2. Or run the terminal command once. The Code tab reads ~/.claude.json, the same file the terminal writes.
   TerminalCopy

   claude mcp add --transport http --scope user leadsagent https://leadsagent.io/mcp/v1

3. In the Code tab, click + next to the prompt box, open Connectors, find leadsagent and connect it.
4. A browser opens. Sign in with your LeadsAgent account and approve access.
5. Start a new session. Ask Claude to check your LeadsAgent account.

1. On the LeadsAgent setup page, select “Create an API key”. Name it for this app and set its expiry and limits. Copy it once; it starts with la_.
2. Set LEADSAGENT_API_KEY in the environment used by this app. Restart the app so it reads the variable. Keep the value out of chats and shared files.
   System environmentCopy

   LEADSAGENT_API_KEY

3. Merge this server into the project’s .mcp.json. The Code tab reads it when you open that project folder.
   .mcp.json · projectCopy

   {
     "mcpServers": {
       "leadsagent": {
         "type": "http",
         "url": "https://leadsagent.io/mcp/v1",
         "headers": {
           "X-API-Key": "${LEADSAGENT_API_KEY}"
         }
       }
     }
   }

4. Restart the Claude desktop app so it reads the variable, then start a new session in the Code tab.

The Claude Code extension in VS Code or JetBrains. It reads the same configuration as the terminal.

1. In the Claude Code panel, type /mcp and choose Add (VS Code extension 2.1.261 or later). Or run the terminal command in the editor’s terminal.
   TerminalCopy

   claude mcp add --transport http --scope user leadsagent https://leadsagent.io/mcp/v1

2. In the panel, type /mcp, choose leadsagent and choose Authenticate.
   In Claude CodeCopy

   /mcp

3. A browser opens. Sign in with your LeadsAgent account and approve access.
4. Start a new conversation. MCP changes apply to new conversations only.

1. On the LeadsAgent setup page, select “Create an API key”. Name it for this app and set its expiry and limits. Copy it once; it starts with la_.
2. Set LEADSAGENT_API_KEY in the environment used by this app. Restart the app so it reads the variable. Keep the value out of chats and shared files.
   Editor environmentCopy

   LEADSAGENT_API_KEY

3. Merge this server into the project’s .mcp.json.
   .mcp.json · projectCopy

   {
     "mcpServers": {
       "leadsagent": {
         "type": "http",
         "url": "https://leadsagent.io/mcp/v1",
         "headers": {
           "X-API-Key": "${LEADSAGENT_API_KEY}"
         }
       }
     }
   }

4. Restart the editor so it reads the variable. In the panel, /mcp shows Connected.