Ship portable MCP integrations and platform distribution

[0xnavarro]

Goal

Make Brida Reflex installable from the same public, provider-neutral contract across major agent hosts without forking product behavior per vendor.

Canonical remote surface proposal: https://mcp.brida.ai/reflex.

The hosted auth/backend remains private. Public integration assets must contain only install metadata, thin adapters, examples, schemas and UI/instructions that are safe to publish.

Targets

ChatGPT

• package a ChatGPT app with the Apps SDK over the remote Reflex MCP surface;
• test in Developer Mode;
• provide directory metadata, privacy/terms URLs, test instructions and country availability;
• submit through the ChatGPT app submission flow only after launch auth/privacy QA is green.

Official reference: https://help.openai.com/en/articles/12515353-build-with-the-apps-sdk

Claude

• prove the same remote MCP endpoint as a Claude custom connector;
• validate OAuth/scopes and tool annotations;
• prepare Connectors Directory submission material if Brida chooses public directory distribution.

Official reference: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

Gemini

• prove remote MCP with Gemini CLI;
• prove Gemini custom Connected App where available;
• document current geography/account/language limitations instead of implying universal availability.

Official references:

• https://geminicli.com/docs/tools/mcp-server/
• https://support.google.com/gemini/answer/17209137

OpenCode

• provide a one-command remote MCP install;
• add a thin public plugin only if it materially improves discovery/configuration beyond native MCP;
• never embed a Brida API key in the plugin.

Official references:

• https://opencode.ai/v2/docs/mcp-servers
• https://opencode.ai/v2/docs/build/plugins

Meta Muse Code

• prove streamable_http MCP configuration and OAuth sign-in;
• provide a public install snippet/skill where useful.

Official reference: https://dev.meta.ai/docs/muse-code/extending

For the consumer Muse app, do not claim MCP/directory support until Meta documents a public integration/submission path we can verify.

Public artifacts

Start in this repository under a small integrations/ surface while assets are mostly manifests/config/docs. Split to a dedicated public integration repository if platform adapters become substantive packages.

Expected:

• generic MCP install guide;
• ChatGPT app source/metadata or a dedicated app package;
• Claude connector guide;
• Gemini CLI / Connected App guide;
• OpenCode MCP config and optional plugin;
• Muse Code config;
• conformance smoke fixtures shared across hosts.

Acceptance

• one canonical MCP tool contract across hosts;
• OAuth/scopes rather than copied long-lived API keys where host support allows it;
• no hosted provider keys, DB credentials, customer data or private routing policy in public source;
• each host gets an install smoke and documented current limitations;
• platform-specific UI/metadata is additive; Reflex semantics remain vendor-neutral;
• submission claims are backed by current official platform documentation.