flingflyers

com.flingflyersPublished by flingflyers.comOfficial publisherv1.0.1Updated Oct 24, 2026

Share an HTML page or PDF as a short public link. No account or API key, expires on its own.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Publishes an HTML document at a short public URL, lets the assistant update it in place, and revokes it on request.

What you can do
The server exposes three tools for sharing generated pages. publish_flyer uploads an HTML document and returns a short public link that anyone holding it can open in a browser. update_flyer replaces the contents of an already published flyer while keeping the same URL, so previously shared links show the new version. revoke_flyer takes a flyer down immediately, after which the link returns gone and the stored document is deleted.
When to use it
Use it when the user wants to view a page the assistant made in a real browser, send it to someone, or open it on another device, and raw markup is not good enough. It also suits iterative revisions of a live page, since the link stays stable across updates.
Requirements
A remote endpoint at flingflyers.com over streamable HTTP. No account, API key, environment variable or header is declared. The assistant needs network access to the endpoint, and revoking requires the id and owner_token returned at publish time.
Before you install
Published flyers are public: the link works for anyone who has it, so do not publish secrets or private data. There are no accounts, so the owner_token is the only proof of ownership and is not recoverable if lost; without it a flyer cannot be updated or revoked. Revoking deletes the stored document.

Installation

In SourceWeft

  1. Open flingflyers in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.flingflyers%2Fflingflyers/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "flingflyers": {
      "type": "http",
      "url": "https://flingflyers.com/mcp"
    }
  }
}

Tools

3

publish_flyer

Publish a flyer

Publish an HTML document at a short public URL and return the link. Use this when the user wants to view a page you made in a real browser, send it to someone, or open it on another device — anywhere handing back raw markup is not good enough. The link works for anyone who has it, with no account and no sign-in, and expires on its own (7 days by default). It is public: anyone with the URL can read the page, so do not publish anything the user would not post openly, and confirm first unless they have asked you to share it. Plain (unencrypted) only. The document reaches the server as text, so this cannot produce an encrypted flyer — for that the user runs `npx flingflyers <file> -e --persist` on their own machine, where the key is generated locally and never sent. Say so rather than implying this is private. Single self-contained document: inline the CSS, JS and images, or use data URIs. External file references will not resolve.

Parametershtmlrequiredttl_hours

update_flyer

Update a published flyer

Replace the contents of a flyer you already published, keeping the same URL. Use this for every revision to a page that is already live — a fix, a new section, a chart the user asked you to add — so the link they may have already sent to someone keeps working and shows the new version. Prefer this over publishing again. A second publish_flyer call mints a different URL and leaves the old page live and out of date, which is almost never what the user meant by "update it". Needs the id and owner_token returned when it was published; there are no accounts, so that token is the only proof of ownership. Send the complete replacement document, not a patch or a fragment — the old contents are overwritten and cannot be recovered. The expiry is left alone unless you pass ttl_hours, so editing a page does not quietly extend how long its link stays alive.

Parametersidrequiredhtmlrequiredttl_hoursowner_tokenrequired

revoke_flyer

Take down a flyer

Take down a flyer immediately: the link starts returning "gone" and the stored document is deleted. Needs the id and owner_token returned when it was published — there are no accounts, so that token is the only proof of ownership and it is not recoverable if lost.

Parametersidrequiredowner_tokenrequired

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.