LeadFast
Encuentra hilos relevantes de Reddit para tu producto. Investiga tu sitio web y gestiona la configuración del producto y las alertas mediante OAuth, con aprobación para los cambios.
Servidor MCP alojado
npx add-mcp 'https://leadfast.vip/mcp'Se instala en Claude Code, Codex, Cursor y más
Documentación
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 threads of its first search. With your approval, it can edit your product and set up alerts. LeadFast never acts on Reddit.
Matches are the thread conversations of the current product. Every match comes from your Conversations rows, so a post from a community that forbids the promotion and a duplicate never appear. 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.
The MCP is free for every account with a verified email. An account without a verified email receives email_unverified. The balance pays for alerts and for opening locked threads. A tool never spends the balance: a top-up and a paid search start only in the app. 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 | First search progress and the threads in Conversations |
get_balance | Balance, alerts left, unlimited flag and automatic top-up |
add_balance | A link to the in-app picker for $10, $25 or $50. Never charges |
start_research, retry_research, correct_research, refresh_threads | Prepare setup or a thread refresh |
list_matches | Open and locked conversations with score, band, community and time |
get_match | One open conversation 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 |
Matches and the balance
list_matches returns an open conversation with every field. A conversation the account did not pay for returns an opaque id, locked: true, the age, the community and the first words of the title. Never the title, the link, the reply or the post id. get_match has no detail for a locked thread.
get_balance reads balanceUsd, alertsLeft, unlimited and autoTopUp. Reading never spends the balance.
add_balance returns status: action-required, a message and the link to /balance?amount=N in the app. The person picks $10, $25 or $50 there and pays in Stripe Checkout. The tool never opens Checkout, never charges a payment method and never spends the balance. Only the person turns on the automatic top-up, from the balance page.
A search that costs $3 starts only in the app. refresh_threads, replace_product_website and start_research with another website return **Search again · $3 in the app** with the app link. The first search of a new account on a website that nobody searched stays free.
Ask your agent
The REST API exposes read-only matches, the product profile and monitoring status: see the API overview.
Permissions
API keys are read-only. Writing requires OAuth and explicit consent to the relevant scope:
leadfast:read: read relevant posts, the balance, 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: get the link to add balance to the account. The scope never moves money.leadfast:onboarding:write: start the first search and correct the product website while it runs.
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
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.
You can also 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
- Read settings with
get_product_settingsorlist_integrations. - Call the concrete operation tool with its fields to prepare a change. Show its complete preview to the user.
- Wait for explicit approval in the agent chat.
- Call the same operation tool with only the returned
proposal_idandapproved: 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 balance, destinations and history are preserved. A new website is a paid search of $3, so the tool returns the app link where the person pays and starts it.
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, first search and the balance
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.
- Ask your agent to prepare
start_researchwith your public product website. Approve its preview. - Use
get_researchto check progress. Uselist_threadsto read the threads. - Use
get_balanceto read the balance and the alerts it pays for. - Ask for
add_balancewith $10, $25 or $50. Open the returned link in the app and pay in Stripe Checkout.
The first search reads the posts from the last 48 hours. Every thread it finds opens free. When it ends, the account gets $5 of balance for new threads. After that, a thread without balance shows only the community, age and a short title preview, and opens for $1 in the app. An account with a verified email keeps the app.
retry_research retries a failed website analysis. correct_research prepares corrections during the first search. refresh_threads returns the app link for the paid search.
Each alert costs $1 and a prepaid balance pays for it. Complete payments in the app. 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. Disconnect Slack through LeadFast. Manage its channels inside Slack.
This documentation is built and hosted on Mintlify, a developer documentation platform.