I'd like to add FLUJO to the existing MCP client selector with manual remote setup instructions.
The prepared change touches only McpUrlBuilder/clients.data.ts and clients.instructions.md.tsx: one Web Clients entry and one shared instruction tree for the dashboard and Markdown export. It uses the generated server URL verbatim, preserving project_ref, read_only, and features. It adds no config-file format or one-click installer.
Formatting, scoped-URL preservation, and isolated React/Markdown rendering checks pass. The hosted Supabase OAuth flow and a read-only tool call from FLUJO have not yet been tested, so this is a proposal rather than a compatibility claim.
CONTRIBUTING.md requests a Discussion before feature PRs. Is this client entry within scope, and is a recorded OAuth connection plus a bounded read-only call against a development project the validation you would expect before a PR?
Reviewable two-file draft and precise validation limits. Prepared with Codex assistance for the FLUJO project.
FLUJO proposes adding manual setup instructions for their project to the MCP client selector. The change involves modifying specific files for web clients and shared instructions, ensuring URL preservation and rendering checks. The proposal seeks feedback on whether the client entry is within scope and if specific validations are needed before a pull request.