fnlowl
Read and manage fnlowl widgets, leads, email sequences and analytics from an AI assistant
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: find leads.Similar tools
Listed for the same task: find leadsReviews
No review yet. Used fnlowl? Be the first to help others choose.What it does
fnlowl is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to 2 capabilities: lead generation and outreach sequencing. That makes it a candidate for tasks such as find leads or find B2B partners.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://api.fnlowl.com/v1/mcpstreamable-http
In Claude Code: claude mcp add --transport http fnlowl https://api.fnlowl.com/v1/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"fnlowl": {
"url": "https://api.fnlowl.com/v1/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE fnlowl answered an MCP connection on 13 Nov 2026 and introduced itself as fnlowl 0.1.0 (MCP protocol 2025-06-18).
40 tools offered to AI assistants
list_projects· Lists the projects this credential can act on. A project is one site or brand under the account, and every widget, lead, campaign and sequence belongs to one. Every other tool takes an optional project argument: pass one of these ids to runcreate_project· Creates a project — one more site or brand under the account — and returns its id. Pass that id as the project argument on later calls to work inside it. Projects cannot be deleted from here.offer_choice· Presents the user with a choice between 2 to 4 options, each with a label and a one-line description, one optionally marked recommended. It is for decisions where reasonable options would build different things — which widget kind, what scoread_plan_usage· Reads the account's plan and what it has used of each monthly quota: leads captured, emails sent, AI messages, plus how many websites and widgets exist against the plan's limits. Leads are counted over the billing period and everything elseplan_site_strategy· Gives an agent what it needs to advise on a website's lead capture: a snapshot of the website's widgets (kind, live or draft, views, completions, conversion), the six widget kinds with where each appears, and the steps to follow — read thelist_widgets· Every widget in the current project, newest last. Returns summaries only — id, name, kind, type, status, article, views, completions. Use read_widget for one widget's full content.read_widget· One widget in full, plus `issues` — what is still missing before it could go live. Includes its questions, quiz questions and options, quiz tiers and calculator inputs. Which of those are meaningful depends on the kind: questions for lead-mcreate_widget· Create a widget in the current project. Six kinds: lead-magnet, popup, survey, announcement-bar, quiz, calculator. It is always created as a draft, and the result lists `issues` — what is still missing before it could go live (empty when noupdate_widget· Change a widget. Only the fields sent are changed, with one exception: sending ANY of questions, quizQuestions, quizTiers or calcInputs replaces ALL FOUR with exactly what is sent, so send the complete set you want to end up with. Publishinrequest_widget_publish· Ask for a draft widget to go live. This requests publication; it does not publish. Called over the API or MCP with a key it does NOT publish: it creates a pending approval carrying a before/after snapshot and returns it, and the widget goesstart_experiment· Split traffic between a control widget and 1 to 3 variants. The variants must already exist as their own live widgets, of the same kind and project as the control (created with create_widget and made live with request_widget_publish). On astop_experiment· End a running experiment. Counts stop with it; starting a new one on the same widgets begins with fresh counts, not a resume.
Show 28 more
list_leads· Captured leads for the current project, newest first. PAGED — at most 200 per call, and the limit is a hard cap, not a default you can raise; pass offset for the next page (limit 50 with offset 50 returns leads 51 onward). These rows are reread_lead· One lead with the answers it gave, and its quiz score and tier if it came from a quiz. The score is frozen at the moment of submission — it is what that visitor actually saw, not a recomputation against the quiz as it stands today.read_analytics· Totals for the current project: widget count, page views, completions, conversion percentage, lead count and how many have unsubscribed. Conversion is completions divided by views as a whole percentage; with no views yet it reads 0, which mlist_widget_analytics· The same numbers per widget, best-converting first. Use this to answer which magnet is working; use widget_results for where one widget's traffic came from.read_widget_results· One widget's views, completions, conversion, and its leads grouped by referrer. The referrer is whatever the visitor's browser reported when they submitted, so it is a rough attribution, not a tracked source. Also returns the funnel (views,read_experiment_results· The A/B experiment a widget is in (or last ran as control): per arm, assigned views, leads, conversion rate and 95% interval in basis points (1234 = 12.34%), and lift against the control arm. result "insufficient_data" means at least one arlist_campaigns· Campaigns in this project, newest first, with their status. Open and click numbers come from the sent-email ledger, not from a counter on the campaign.draft_campaign· Create a campaign AS A DRAFT. There is no tool that sends one: sending puts mail in thousands of real inboxes, spends deliverability reputation that cannot be bought back, and cannot be undone. A person sends it from the dashboard. recipienupdate_campaign· Change a draft campaign. A campaign that has already been sent cannot be edited — the ledger describes what actually went out, and editing it afterwards would make that a lie.list_sequences· Sequences in this project with their steps and branch. The shape is BOUNDED: a linear chain of steps, then at most one branch point, each path its own linear chain. No nesting, no rejoining, no parallel paths.list_sequence_enrollments· Who is running through which sequence: for a lead (leadId) or for a sequence (sequenceId), each enrolment's status (active, finished or stopped), the step it is on and when it is next due. This is how to answer "why did this lead get, or nodraft_sequence· Create a sequence AS A DRAFT. Steps are either an email or a delay in days — a delay is its own step, so two emails can run back to back. A branch may be added at the end; its paths are evaluated first-match-wins, left to right, and a filteupdate_sequence· Change a DRAFT sequence. Only the fields sent are changed, except that sending steps or branch replaces the whole of that part, so send the complete chain you want. It cannot edit an active sequence and cannot activate one: an active sequenpause_sequence· Move a sequence to draft, which stops new enrolments. Stopping mail is never the slower path, so this applies immediately. Starting one again is activate_sequence, which a person approves: an active sequence enrols every future lead and senactivate_sequence· Ask for a draft sequence to start sending. Called over the API or MCP this does NOT activate it: it creates a pending approval and returns its requestId, and the sequence starts — enrolling future matching leads and mailing them on its timelist_templates· Transactional templates in this account. Built-in starters are marked isCustom false and cannot be deleted.create_template· Create a transactional template. category is one of authentication, account, orders, notifications. Use {{name}} placeholders in the subject and body for values supplied when it is sent; a placeholder nobody supplies is replaced with nothinupdate_template· Change a template's name, category, subject or body — only the fields sent. Built-in starters can be rewritten too (they just cannot be deleted). It changes what later sends of this template say; it sends nothing.read_brand· The brand: site name, accent colour, sender name, logo and the postal address that every commercial email needs in its footer. With a project in scope this is that website's brand — the account defaults with the website's own overrides applupdate_brand· Change brand settings. Only the fields sent are changed. With a project in scope this sets that website's own override and leaves the account defaults — and every other website — alone; without one it changes the account defaults every websread_ai_context· The account's AI context: what the blog is about, its pricing tiers, value props, testimonials, design direction and tone presets. Every AI-personalised lead magnet is generated from exactly this plus the visitor's own answers. It belongs tupdate_ai_context· Change the AI context: the about text, design direction, value props, pricing tiers and testimonials that every AI-personalised lead magnet is generated from. Changes apply to generations from then on; lead magnets already sent are not rewrread_sending_status· Read account sending readiness, domain verification, daily usage, and recent reputation state. While the sending domain is not yet verified it also returns `records`: the DNS records to publish. `sentToday` counts the last 24 hours on a rollist_email_deliveries· List recent email outcomes for this account. Recipients are masked; use this to diagnose queued, delivered, opened, clicked, bounced, complained, or failed mail. `sentToday` counts the last 24 hours on a rolling basis, while `sharedTrial.selist_integrations· List native integration providers and connection health. Credentials are never returned.read_integration_delivery_status· Read recent queued ESP/webhook handoff outcomes and retry state. Lead identifiers, payloads, and credentials are not returned.read_ai_generation_status· Read recent AI lead-magnet generation outcomes by status and widget. Visitor answers, generated content, lead ids, and failure details are not returned.ask_question· Ask the fnlowl Advisor a question in plain English. It knows how fnlowl works — widgets and where each kind appears, the embed, sequences, campaigns, sending, credits, plans, MCP — and can read the account's own widgets, leads, analytics, c
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://api.fnlowl.com/v1/mcp | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Repository | https://github.com/fnlowl/skills | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Version | 1.0.1 | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Website | https://fnlowl.com/docs/agents/mcp-server/ | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
Change history
- VERSION02 Oct 20261.0.0 → 1.0.1
- NEW02 Oct 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is fnlowl still online?
Free alerts · no account▲ 0Do you run fnlowl? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about fnlowl
How do I connect fnlowl?
Use the hosted endpoint https://api.fnlowl.com/v1/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does fnlowl offer?
When Electra Index connected on 13 Nov 2026, it listed 40 tools: list_projects, create_project, offer_choice, read_plan_usage, plan_site_strategy, list_widgets, read_widget, create_widget and more. The full list is in "Live check" above.
Is fnlowl online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use fnlowl for?
Based on its description, it is most relevant to: find leads, find B2B partners, recruit developers, send personalized outreach.