Flowershow

app.flowershowPublished by flowershow.appOfficial publisherv1.0.0Updated Nov 2, 2026

Publish Markdown and HTML from your AI session as a live website. No account needed.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Flowershow publishes Markdown and HTML from an AI session as a live website, with no account required according to the registry description.

What you can do
  • Publish Markdown or HTML content from the session as a live website
  • Turn notes, docs and knowledge bases into published pages
  • Work alongside the Flowershow CLI and other publishing routes such as drag-and-drop, Obsidian or GitHub
  • The manifest lists no individual tools, so exact operations are not documented here
When to use it
Useful when you want an assistant to turn Markdown notes, documentation or a knowledge base into a shareable live site without setting up a static-site pipeline yourself.
Requirements
A remote MCP endpoint at flowershow.app over streamable HTTP; no packages, environment variables or headers are declared. The README's other publishing routes mention signing up on the website and logging in with the fl CLI.
Before you install
Publishing makes content publicly available on the web, so check what is being shared before publishing. The README mentions signing up and logging in for other publishing routes; the manifest declares no authentication.

Installation

In SourceWeft

  1. Open Flowershow 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/app.flowershow%2Fflowershow/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": {
    "flowershow": {
      "type": "http",
      "url": "https://flowershow.app/api/mcp"
    }
  }
}

README

[skills.sh]

Flowershow 💐

Publish markdown quickly and easily - for docs, knowledgebases, websites and more

Try it out now and sign up at https://flowershow.app/

Want to see it in action? 🎉 https://flowershow.app itself is built and published with Flowershow 💐

Flowershow is proudly open-source.

Flowershow is a product of Datopian - dedicated to democratising the power of data & knowledge.

Publish

Just login in the website and you can publish in seconds by drag and drop, from Obsidian (plugin), from Github and more.

Command line (for AI)

The CLI is a single binary called fl.

bash
# Install (macOS / Linux)curl -fsSL https://raw.githubusercontent.com/flowershow/flowershow/main/apps/cli/install.sh | sh
# Log in and publish a folder or filefl loginfl ./my-notes

Windows: download fl_windows_amd64.zip from the latest release and put fl.exe on your PATH. Full details: CLI reference.

Using an AI agent (Claude, ChatGPT, Codex, Cursor)? See https://flowershow.app/publish-with-ai.

For Developers (contributing to Flowershow itself)

You do not need anything below to use Flowershow. To install and publish, see Install and publish above. This section is only for people developing the Flowershow platform from source.

Monorepo Structure

This is a Turborepo monorepo managed with pnpm workspaces.

apps/  flowershow/           # Next.js web application (flowershow.app)  cli/                  # Go CLI (`fl`) — publish markdown files from the terminal or AI agentspackages/  api-contract/         # @flowershow/api-contract — Zod schemas, TS types, OpenAPI 3.1 spec  cloudflare-worker/    # Markdown processing Cloudflare worker  remark-wiki-link/     # @flowershow/remark-wiki-link — remark plugin for wiki-style linkscontent/  flowershow-app/       # Marketing site content (Obsidian vault, not a workspace package)

Development setup

Prerequisites (for platform development only): Node.js 22+, pnpm, and Docker.

bash
# Clone (include the e2e test-site submodule)git clone --recurse-submodules https://github.com/flowershow/flowershow.gitcd flowershow
# Install dependenciespnpm install
# Copy env template (then edit apps/flowershow/.env with your secrets)cp apps/flowershow/.env.example apps/flowershow/.env
# Start everything: Postgres, MinIO, Inngest, Cloudflare Worker, Next.js apppnpm dev

Visit http://cloud.localhost:3000 once it's running.

If you already cloned without --recurse-submodules, run git submodule update --init to fetch the e2e test site.

Commands

bash
pnpm dev --stripe              # Also start Stripe webhook forwardingpnpm dev --github              # Also start Smee (GitHub webhook proxy)pnpm dev --search              # Also start Typesensepnpm dev:all                   # Start everything including all optional services
pnpm dev:local                 # Start dev servers only (no Docker infrastructure)pnpm dev:local:all             # Start dev servers only + all optional servicespnpm dev:down                  # Stop Docker containers (keep data)pnpm dev:nuke                  # Stop containers + delete all data volumes
pnpm build                     # Build all packagespnpm test                      # Run tests across all packagespnpm lint                      # Lint all packages (ESLint for app, Biome for packages)pnpm format                    # Check formatting (Biome)pnpm format:write              # Auto-fix formatting

For web app setup (database, storage, auth, etc.), see apps/flowershow/README.md.

Tooling

ToolScopePurpose
BiomeEntire repoFormatting (single quotes, 2-space indent) and linting for packages/
ESLintapps/flowershowNext.js-specific linting via eslint-config-next
Vitestpackages/remark-wiki-linkUnit tests
Playwrightapps/flowershowE2E tests
TurborepoRootTask orchestration and caching
Changesetspackages/Versioning and npm publishing
HuskyRootGit hooks (pre-commit runs lint-staged)

A pre-commit hook automatically formats staged files via lint-staged before each commit.

Releasing packages

bash
pnpm changeset                 # Create a changeset describing your changepnpm version-packages          # Bump versions based on changesetspnpm release                   # Build all packages and publish to npm

Documentation

  • Web app: apps/flowershow/README.md — architecture, local dev setup, environment config, testing, troubleshooting
  • REST API contract: packages/api-contract/README.md — Zod schemas, TypeScript types, and OpenAPI 3.1 spec for the Flowershow REST API. The contract is the single source of truth for the API surface; the Next.js API routes, CLI, and Obsidian plugin all consume it.
  • Interactive API docs: With the dev server running, visit http://cloud.flowershow.local:3000/api/docs for Swagger UI, or /api/docs/openapi.json for the raw spec. In production: flowershow.app/api/docs.
  • CLI: apps/cli/README.md — Go CLI for publishing markdown files. Also the interface for AI agent integration — see the Flowershow skill.
  • User docs: flowershow.app/docs

Community

Contributing

We're working on opening up parts of Flowershow for community contributions. While this isn't ready yet, we're excited to welcome contributors soon.

You can already contribute by adding pull requests for demos or tests of Flowershow markdown features:

Development Workflow

  1. Create feature branch from staging
  2. Implement changes
  3. Submit PR to staging
  4. After approval, changes are merged to main

We use squash merges to staging with conventional commit messages.

Source: README.md at commit 9ca45c0

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

50% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts