LeadFast

npx add-mcp 'https://leadfast.vip/mcp'

MCP

Ask your coding agent for today's buyer matches.

LeadFast supports the Model Context Protocol (MCP) over Streamable HTTP. Your agent can guide signup, research your website and read the available setup threads. With your approval, it can edit your product, set up alerts. LeadFast never acts on Reddit.

Matches are new Reddit posts with a score of 50 or more. A match can appear before any destination accepts its alert.

The Suggested Reply is the saved text for the match, when available. A read request returns that text without a new reply or alert.

Ordinary conversations, product settings and integrations require an active 7-day trial or subscription. Setup progress, available setup threads and subscription status require a verified account. Without either, the app stays closed. After your trial ends without a subscription, every new thread appears locked. Your conversations, settings and destinations stay stored until you subscribe. An existing OAuth connection with leadfast:integrations:write can still pause or disconnect integrations.

Connect

Use https://leadfast.vip/mcp as the endpoint. Authenticate with OAuth or an lf_ API key as a bearer token. OAuth uses dynamic client registration (DCR) and proof key for code exchange (PKCE). Add the configuration for your client below.

{
  "mcpServers": {
    "leadfast": { "url": "https://leadfast.vip/mcp" }
  }
}

{
  "mcpServers": {
    "leadfast": { "url": "https://leadfast.vip/mcp" }
  }
}

[mcp_servers.leadfast]
url = "https://leadfast.vip/mcp"

{
  "mcp": {
    "leadfast": { "type": "remote", "url": "https://leadfast.vip/mcp" }
  }
}

{
  "mcpServers": {
    "leadfast": { "url": "https://leadfast.vip/mcp" }
  }
}

Tools

Tool	Returns
get_research, list_threads, get_subscription	Setup progress, available threads and subscription status
start_research, retry_research, correct_research, refresh_threads	Prepare setup or a thread refresh
start_trial	Open secure trial Checkout after approval
list_matches	Recent matches with score, band, subreddit and time
get_match	One match with reason, Suggested Reply and delivery result
get_product	The product profile LeadFast understood
get_monitoring_status	Monitoring state, last website review, destinations
get_product_settings	Website and a pending product review
list_integrations	Connection status and safe details for each integration
correct_product_facts, apply_product_facts	Prepare a facts correction or apply its reviewed profile
replace_product_website, select_website_offering	Start a website review or choose one offering
correct_website_facts, apply_website_review	Correct or apply a pending website review
cancel_website_review, retry_website_review	Cancel or retry a pending website review
connect_email, connect_slack, connect_telegram, connect_webhook	Prepare an integration connection
test_email, test_telegram, test_webhook	Send a real test after its preview is approved
pause_integration, resume_integration, disconnect_integration	Manage one configured integration
get_change_status	The proposal and its saved execution result
cancel_change	Cancellation of an unexecuted proposal

Ask your agent

The REST API exposes read-only matches, the product profile and monitoring status: see the API overview.

Permissions

API keys and existing OAuth permissions remain read-only. Writing requires OAuth and explicit consent to the relevant scope:

• leadfast:read: read relevant posts, product settings and safe integration status.
• leadfast:product:write: edit product facts and the website.
• leadfast:integrations:write: configure, test, pause, resume or disconnect supported integrations.
• leadfast:billing:write: open trial Checkout.
• leadfast:onboarding:write: research and correct the product website during setup.

Request these scopes through your client's OAuth authorization flow. An insufficient_scope response identifies the missing permission. Granting connection access does not approve individual changes.

New connections start with read-only permissions. If a client requests write access, the consent page also offers a read-only connection.

Use https://leadfast.vip/mcp as the OAuth resource in authorization, token exchange and refresh requests. Use PKCE S256. LeadFast issues opaque access tokens.

Revoke an agent

During your trial or subscription, open Integrations → API & agents → Agent connections. Select Revoke access on the agent. Revocation invalidates its access and refresh tokens. It also removes consent and cancels unexecuted proposals. Your product and alert destinations stay connected.

Without a plan, the app stays closed. Use the OAuth revocation endpoint below or contact support for help. Reconnect the agent with fresh consent when you want to use it again.

OAuth clients can use the discovery document's revocation_endpoint, with the token and client identifier in a form-encoded POST. Confidential clients must also authenticate. An unknown token returns success without revealing whether it exists.

Change approval

Tool effects

Product changes, integration setup, pause, resume, disconnect and cancel_change are writes. A disconnect can revoke provider access. Resuming a destination enables future alert delivery.

connect_email, test_email, test_telegram and test_webhook can send a real message or POST to an external endpoint. A different email address can receive a verification code.

Each tool prepares a preview before it sends anything. Every change and test requires its own approval in the agent chat.

Approve one change

1. Read settings with get_product_settings or list_integrations.
2. Call the concrete operation tool with its fields to prepare a change. Show its complete preview to the user.
3. Wait for explicit approval in the agent chat.
4. Call the same operation tool with only the returned proposal_id and approved: true.

Proposals expire after 10 minutes and belong to one account and OAuth client. Settings changes invalidate older proposals. Confirm with the proposal ID and approval only. The agent client asks for your approval. LeadFast checks the permissions and proposal before the change.

Repeated confirmations return the saved result. If an operation is still running or has an uncertain outcome, inspect its status before preparing another change. A test sends a real message and needs its own approved proposal.

Product changes

correct_product_facts accepts description, audience, problems, exclusions and an optional product name.

replace_product_website prepares a new product. Read its status. Choose a discovered offering with select_website_offering when needed. Review the profile before apply_website_review. Use correct_website_facts, retry_website_review or cancel_website_review to manage that review. Current alerts continue until the replacement is applied. Your subscription, destinations and history are preserved.

A facts correction also prepares a profile for review. Read the profile. Prepare apply_product_facts to apply it after approval. Acquisition searches stay internal.

Signup, setup and subscriptions

Connect through OAuth. If you have no account, use Sign in or create your account on the consent page. Complete Google sign-in or the email code on LeadFast, then return to your agent.

1. Ask your agent to prepare start_research with your public product website. Approve its preview.
2. Use get_research to check progress. Use list_threads to read the available setup threads.
3. Ask for start_trial. Approve its preview, then open the secure Checkout link yourself.
4. Return to the agent. Use get_subscription to check access.

The first 5 setup threads open when ready. Other results show only the community, age and a short title preview. An account that used its trial sees new threads locked.

retry_research retries a failed website analysis. correct_research prepares corrections during setup. refresh_threads follows the same cooldown as the setup screen.

start_trial uses the monthly plan and the existing 7-day trial rules. Each account and email can use 1 trial. An account that used its trial chooses a plan on LeadFast. Complete payment and subscription changes on Stripe. Never enter payment details in the chat.

Integration setup

• Slack: approve connection, open the authorization link, then invite the bot to channels inside Slack. Channel invitation runs its real test. An agent can disconnect the installation; channel management stays in Slack.
• Telegram: approve connection, open the bot link and press Start or add it to a group. Approve a separate test to activate the destination.
• Email: the verified account address connects directly. Another address receives a code; enter it on the authenticated page returned by the tool. Keep the code out of chats and tool arguments.
• Webhook: approve a public HTTPS endpoint. Copy its signing secret from the authenticated LeadFast page into your receiver configuration. Approve a separate test to activate it. Tools never return the signing secret.

Pause, resume and disconnect use integration proposals. Resume requires an active trial or subscription. Disconnect Slack through LeadFast. Manage its channels inside Slack.

This documentation is built and hosted on Mintlify, a developer documentation platform.