leadli.me

Official

Telegram subscriber reports, Meta/TikTok ad attribution and channel setup through 47 MCP tools. Hosted Streamable HTTP; requires an organization Bearer access key.

About leadli.me MCP Server

Telegram subscriber reports, Meta/TikTok ad attribution and channel setup through 47 MCP tools. Hosted Streamable HTTP; requires an organization Bearer access key.

Features

Tools

Transport

streamable-http
Getting Started

Connect to https://api.leadli.me/api/v1/mcp using Streamable HTTP. Send Authorization: Bearer <organization-access-key>. Create your key in the leadli.me app under Organization settings → Access keys. The placeholder is not a credential. Start with leadli_get_context, then use the tools returned by authenticated tools/list. Without a key the endpoint returns HTTP 401 with a Bearer challenge. Domain actions require an active trial or paid plan; effective access depends on key permissions and its creator’s role. 47 documented tools cover subscriber and attribution reports; channel, bot and landing setup; Meta/TikTok connections; and subscriber ban/unban actions. Public tool reference: https://leadli.me/en/guides/mcp-server Known connection guides: Codex and Claude Code. Support: support@mail.leadli.me. Hosted private-source service.

Tools (47)
Functions this server exposes to AI clients

leadli_get_context

Get this key’s organization, effective permissions, available tools and plan access.

leadli_list_channels

List a bounded page of channels accessible to the key creator.

leadli_get_channel

Get channel details and safe Telegram setup metadata.

leadli_get_analytics

Get attribution aggregates. Clicks, confirmed joins and delivered conversions use click-time cohorts; membershipFlow uses observed event times. Hour/day/week ranges are capped at 31/90/365 days, with breakdowns available for 7/31/90 days.

leadli_list_joins

List observed join/rejoin events in the half-open UTC interval [from,to), up to 365 days. Filter before pagination. Missing ad attribution is unknown, not proof of organic traffic. Membership is the current observed state. landingId is the exact analytics landingPageUrl key.

leadli_list_subscribers

List observed subscribers only; this is not a complete Telegram member roster. Membership is the current observed state.

leadli_get_report_status

Get own report and the anonymous multiple-reports signal for up to 100 observed subscriber IDs.

leadli_save_report

Save or replace the organization report for one observed subscriber. Reports do not ban subscribers.

leadli_withdraw_report

Withdraw the organization report for one observed subscriber.

leadli_list_organization_reports

List a bounded page of reports belonging to the current organization.

leadli_withdraw_organization_report

Withdraw one report belonging to the current organization.

leadli_ban_subscriber

Ban one observed person from the current Telegram channel; bots cannot be banned.

leadli_unban_subscriber

Remove the ban for one observed person in the current Telegram channel. This does not automatically rejoin the person.

leadli_create_channel

Create a draft Telegram channel. Plan capacity is checked on activation. For a Telegram bot use leadli_create_bot.

leadli_create_bot

Create a draft Telegram bot from its @username or t.me link. Then connect an ad platform and a landing, install the code from leadli_get_bot_code, and activate it with leadli_activate_channel.

leadli_get_bot_code

Read what the bot's own server needs: forward private /start and my_chat_member updates unchanged to updatesPath, report successful payments to eventsPath, then have the user open verifyStartUrl. Both paths are relative to this MCP server's origin. botKey is private: keep it in the bot's server configuration and never show it in answers. Telegram bots only; channels answer BOT_ONLY_OPERATION.

leadli_connect_bot_token

Optional: store the BotFather token of the same bot to show its exact name and photo. The token is a secret input and is never returned; the bot's webhook and updates are not touched. Telegram bots only; channels answer BOT_ONLY_OPERATION.

leadli_update_channel

Update the channel name.

leadli_connect_telegram_bot

Connect and verify a Telegram bot. The token is a secret input and is never returned. Telegram channels only; bot channels answer CHANNEL_ONLY_OPERATION.

leadli_set_telegram_destination

Set the Telegram channel reference and reset its verification. Telegram channels only; bot channels answer CHANNEL_ONLY_OPERATION.

leadli_verify_telegram_destination

Verify the bot permissions for the configured Telegram channel. Telegram channels only; bot channels answer CHANNEL_ONLY_OPERATION.

leadli_get_setup_status

Read current channel readiness checks. `ready` is the answer: metaVerified or tiktokVerified is enough, so one of them may stay false on a ready channel.

leadli_activate_channel

Activate the channel only when current setup and plan capacity allow it.

leadli_disable_channel

Disable channel attribution and release its active plan slot.

leadli_set_meta_connection

Verify and save a Meta dataset connection using its required test event code. The access token is never returned.

leadli_remove_meta_connection

Disconnect the channel from Meta.

leadli_set_tiktok_connection

Verify and save a TikTok pixel connection for the Events API using its required test event code. The access token is never returned.

leadli_remove_tiktok_connection

Disconnect the channel from TikTok.

leadli_set_landing_url

Set an HTTP(S) landing URL without credentials, query parameters or fragments.

leadli_create_ready_made_landing

Create and publish the existing ready-made Telegram landing with current setup safeguards.

leadli_refresh_ready_made_landing

Refresh and publish ready-made landing content from the current Telegram channel.

leadli_get_ready_made_landing

Read the published ready-made landing metadata.

leadli_ensure_landing_installation

Ensure landing SDK setup and return its public installation instructions and expiring installation token.

leadli_get_landing_installation_status

Read the landing SDK installation status.

leadli_restart_landing_installation

Restart pending landing SDK installation, replacing the previous attempt and expiring token.

leadli_confirm_landing_installation

Confirm an observed, ready landing installation for its exact HTTP(S) origin.

leadli_list_landings

List the channel pages (own and ready-made), their state and plan usage.

leadli_add_landing

Add another HTTP(S) page to a channel that already has a confirmed page; query and fragment are ignored. Returns the page and its expiring installation token.

leadli_get_landing_installation

Read the SDK installation state of one channel page.

leadli_restart_landing

Issue a new installation token for a pending or disconnected own page, replacing the previous one.

leadli_confirm_landing

Confirm a page once its SDK and CTA were observed on the page origin; allows that origin.

leadli_disconnect_landing

Disconnect an own channel page; its history is kept and its slot is freed. The last confirmed page cannot be disconnected.

leadli_get_sdk_instructions

Read the public SDK script URL, subscription attribute and route key.

leadli_list_notification_receivers

Read the channel notification receivers. Requires configuration permission. Telegram channels only; bot channels answer CHANNEL_ONLY_OPERATION.

leadli_create_notification_start_link

Create a one-time, expiring Telegram notification subscription link. Telegram channels only; bot channels answer CHANNEL_ONLY_OPERATION.

leadli_update_notification_receiver

Enable or disable an existing notification receiver. Telegram channels only; bot channels answer CHANNEL_ONLY_OPERATION.

leadli_remove_notification_receiver

Remove an existing channel notification receiver. Telegram channels only; bot channels answer CHANNEL_ONLY_OPERATION.

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