Koskamo

Flowershow MCP

An official MCP server that allows AI agents to publish Markdown and HTML content as live websites directly from chat applications like Claude and ChatGPT, providing live links and claim URLs for site management.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Flowershow MCP logo, by FlowershowVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by Flowershow
MCP endpoint (Streamable HTTP)
https://flowershow.app/api/mcp
Vendor documentation

What you can do with it

  • Publish Markdown or HTML pages as live websites from AI chats
  • Update existing sites by republishing changed files to the same address
  • List sites and manage claims using personal access tokens
  • Delete or replace entire sites via agent commands

Source and maintenance

Vendor evidenceRegistry 1.0.0
Maintenance checked

Protocol and capabilities

Server
flowershow 1.0.0
MCP protocol
2025-06-18
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

1 advertised

publish — Publish to Flowershow
Advertised by the server during the last successful anonymous check.
Advertised destructiveOpen-world

Publish files as a live website on Flowershow and get a shareable URL. Use when the user says "publish this", "put this online", "make this a website", "share this as a page" or "host this". Accepts Markdown (.md, rendered as a styled page with navigation), HTML (.html, served as-is) and supporting files such as CSS, JS, JSON and images: one page or a small site, up to 50 files and 3 MB per call. Name the home page index.md or index.html. Without an account this creates a new site that expires in 7 days and returns a claim link: always show the user the live URL and the claim link exactly as returned, so they can keep the site. To update that site later in the conversation, call publish again with its siteId and claimToken and only the files you changed or added: files you don't send are kept as they are. To remove pages or files, list their paths in delete (files can then be empty). Only when the user explicitly asks to start the site over, set replaceWholeSite to true: the files you send become the whole site and every other file is removed. If that would remove existing files, the call is refused and tells you how many and which; ask the user, then call again with confirmDeleteCount set to that number. For bigger sites, suggest the Flowershow CLI (fl).

publish input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "files"
  ],
  "properties": {
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path"
        ],
        "properties": {
          "path": {
            "type": "string",
            "description": "Relative path, e.g. \"index.html\" or \"img/logo.png\""
          },
          "content": {
            "type": "string",
            "description": "Text content (UTF-8)"
          },
          "contentBase64": {
            "type": "string",
            "description": "Binary content, base64-encoded (images etc.)"
          }
        }
      },
      "description": "Files to add or update. When updating a site, send only the files that changed; other files are kept. Can be empty when only deleting."
    },
    "delete": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 1000,
      "description": "Paths of existing files to remove from the site (with siteId), e.g. [\"old-page.md\"]"
    },
    "siteId": {
      "type": "string",
      "description": "Update this existing site instead of creating a new one"
    },
    "claimToken": {
      "type": "string",
      "description": "The claimToken returned when the anonymous site was created (needed with siteId when not signed in)"
    },
    "replaceWholeSite": {
      "type": "boolean",
      "description": "Set true only when the user asks to start the site over: the files sent become the whole site and all other files are permanently removed. Never use it to update a few pages. Default false."
    },
    "confirmDeleteCount": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "With replaceWholeSite: the number of existing files the replace will remove, as reported by the refused first call. Set it only after the user has confirmed."
    }
  }
}
publish output schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "liveUrl",
    "siteId",
    "message"
  ],
  "properties": {
    "siteId": {
      "type": "string"
    },
    "liveUrl": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "claimUrl": {
      "type": "string"
    },
    "expiresAt": {
      "type": "string"
    },
    "claimToken": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
publish annotations
{
  "title": "Publish to Flowershow",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1865 ms
95th percentile latency
1865 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1865 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http flowershow-mcp https://flowershow.app/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add flowershow-mcp --url https://flowershow.app/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable flowershow-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "flowershow-mcp": {
      "url": "https://flowershow.app/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "flowershow-mcp": {
      "type": "streamableHttp",
      "url": "https://flowershow.app/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start flowershow-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "flowershow-mcp": {
      "type": "http",
      "url": "https://flowershow.app/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http flowershow-mcp https://flowershow.app/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "flowershow-mcp": {
      "url": "https://flowershow.app/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "flowershow-mcp": {
      "serverUrl": "https://flowershow.app/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Flowershow MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Flowershow MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing