MCP · Connection guide

Connect leadli.me to your AI assistant

Updated October 6, 2026

View your leadli.me channels and reports in your assistant. Create an organization key, configure your client and check access before making changes.

1. Create and save a key

Open Organization settings → Access keys. An owner or admin can create a key: name it and select the permissions you need. Read access is enough for reports.

Copy the key to your password manager. It cannot be revealed again. If you lose it, regenerate it and update your client. Regeneration stops the old key from working; you can also revoke access.

MCP server URL

2. Connect Codex through the UI

Open Settings → MCP servers → Add server. Name the connection leadli_me, choose Streamable HTTP and paste the server URL from the previous step.

In Headers, add Authorization with the value Bearer YOUR_LEADLI_ME_ACCESS_KEY. Replace YOUR_LEADLI_ME_ACCESS_KEY with your key; keep Bearer and the space.
Save the server and select Restart. leadli.me does not require an OAuth login.
If your version has no Headers field, use the configuration below.

Or paste the key into your Codex configuration

Add this block to ~/.codex/config.toml and replace YOUR_LEADLI_ME_ACCESS_KEY with your key. If leadli.me is already configured, update the existing block.

The key will be stored in this file as plain text. Keep the file out of repositories and do not publish it.

Codex configuration

[mcp_servers.leadli_me]
url = "https://api.leadli.me/api/v1/mcp"
http_headers = { Authorization = "Bearer YOUR_LEADLI_ME_ACCESS_KEY" }

Desktop, CLI and IDE share this configuration on the same computer. Restart the MCP connection or client after saving.

If you use Claude Code

In ~/.claude.json, add leadli_me to the top-level mcpServers object and replace YOUR_LEADLI_ME_ACCESS_KEY with your key. Preserve other settings and servers: do not replace the whole file with this example.

This connection is available across your Claude Code projects. The key is also stored as plain text; keep the configuration local.

Claude Code configuration

{
  "mcpServers": {
    "leadli_me": {
      "type": "http",
      "url": "https://api.leadli.me/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_LEADLI_ME_ACCESS_KEY"
      }
    }
  }
}

Restart Claude Code. This example does not configure Claude web chat or Claude Desktop.

3. Check the connection

Open /mcp in your client and check the leadli_me connection. Then start with a read-only request and confirm that the response belongs to the intended organization.

First request

Show my leadli.me channels. Do not change anything.

Authentication failed: check Authorization, the Bearer prefix with a space and whether the key has been revoked.
An action is unavailable: review the key permissions and organization plan.
Server unavailable: compare the URL with Access keys and reconnect.
If the key is exposed, revoke it and create a replacement. Do not send your leadli.me key in assistant messages. Telegram or Meta tokens supplied for channel setup enter the assistant provider’s context.

Direct answers

Do I need to sign in to read the guide?

No. This guide is public. Sign in only when you need to create a key in your organization settings.

Can I reveal my key again?

No. leadli.me shows a key only when it is created or regenerated and stores only its hash. Save it in your password manager. If you lose it, regenerate it.

Do I need a terminal for Codex?

No. Add the server in Settings → MCP servers. If the form has no Headers field, paste your key into your local ~/.codex/config.toml using the example below.

Primary sources

Test attribution on one public channel.

Install the snippet on your landing page, make a test join, and verify the complete path to Meta.

Try leadli.me