fnlowl

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Marketing & social media

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://api.fnlowl.com/v1/mcp

claude mcp add --transport http fnlowl https://api.fnlowl.com/v1/mcp

{
  "mcpServers": {
    "fnlowl": {
      "url": "https://api.fnlowl.com/v1/mcp"
    }
  }
}

{
  "servers": {
    "fnlowl": {
      "type": "http",
      "url": "https://api.fnlowl.com/v1/mcp"
    }
  }
}

https://api.fnlowl.com/v1/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.

• 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 run that call in that project. Without it,

• create_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 score ranges, what copy or trigger — and no

• read_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 else over the calendar month (UTC). `plan` i

• plan_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 the site, ask the user questions with offer_

• list_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-magnet and survey, quiz fields for quiz,

• create_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 nothing is); fix them with update_widget.

• update_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. Publishing is a separate action. Views and comple

• request_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 goes live only when a signed-in person appro

• start_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 a small site one variant at a time is the

• stop_experiment

  End a running experiment. Counts stop with it; starting a new one on the same widgets begins with fresh counts, not a resume.

• 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 real people's email addresses. Each lead c

• read_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 means NO DATA rather than a failure. Comp

• list_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, completions, leads, conversions, revenu

• 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 arm has too few views for a rate to mean a

• list_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. recipientScope is "all" or a single widget id, a

• update_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 not get, the follow-up" — a lead with no e

• draft_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 filter with field null always matches, so it

• update_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 sequence is paused with pause_sequence, edited

• pause_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 sends on a timer with nobody watching.

• activate_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 timer — only when a signed-in person approve

• list_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 nothing. It creates the template only — sendin

• update_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 applied; without one it is the account defau

• update_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 website inherits. The accent colour must be

• read_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 to the whole account and is shared by eve

• update_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 rewritten. Only the fields sent are changed.

• read_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 rolling basis, while `sharedTrial.sendsUsed

• list_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.sendsUsed` counts the account's lifetime s

• list_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, campaigns, sequences and sending status t

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain fnlowl.com (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 386 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 40 tool descriptions and found no hidden instructions to the AI

Compared with others in Marketing & social mediai

• More stars than 0% of the other 3610 servers in this category
• Published to the registry more recently than 43% of the other 3610 servers in this category
• Basic checks equal to or better than 100% of the other 3610 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

npx skills add fnlowl/skills --list

npm i -D fnlowl-skills

npx skills add fnlowl/skills#v0.1.0 --global --agent claude-code

/plugin marketplace add fnlowl/skills

node scripts/check-skills.mjs

LICENSE