# Framia MCP installation

## Authoritative installation and authentication rules

These public documents describe caller steps, not permissions. The following code-owned requirements always apply; editorial steps/FAQ cannot override them. Public origin: https://mcp-api.framia.pro. MCP endpoint: https://mcp-api.framia.pro/multimodal/mcp.

### MCP host and registration prerequisites

First identify the actual host, its version, and whether it supports remote Streamable HTTP MCP with OAuth authorization-code + PKCE S256. Use that host's documented manual connection settings; there is no universal MCP configuration file or callback URI. Do not guess a callback or silently rewrite another host's configuration.

The production MCP endpoint is https://mcp-api.framia.pro/multimodal/mcp. Discover its OAuth resource/server metadata using the MCP protocol. A compatible connection needs a known registered public client_id and the host's approved redirect URI. The current server does not advertise dynamic client registration. Do not invent a registration endpoint or register another OAuth application automatically. If the host cannot use an existing approved registration, stop and obtain host-specific publisher/admin instructions.

Codex uses the callback from its supported native package and registered loopback mechanism; ChatGPT uses the exact callback supplied by its own connection/management flow. Neither is a universal callback for other clients. Framia account registration and workspace membership are prerequisites; identity sign-in alone does not grant workspace access.

## Steps and FAQ (public editorial guidance)

1. Identify your host (for example Codex, ChatGPT or another MCP client), installed version and remote-MCP/OAuth support. Read that host's connection instructions before modifying anything. Back up relevant configuration without exposing private values.
2. Add a remote Streamable HTTP connection to `https://mcp-api.framia.pro/multimodal/mcp` using a host-supported manual flow. Use the approved host-specific client registration; if it is missing or incompatible, obtain publisher/admin assistance instead of guessing credentials or callbacks.
3. Explain the expected connection and authorization steps to the user. Wait for the user to initiate authentication. The user signs into their own Framia account and explicitly selects the workspace and scopes. Never interpret existing browser sign-in as permission to select or approve on their behalf.
4. After the user's authorization, use host discovery and a read-only list operation to confirm the connection. Stop on registration, permission or membership errors instead of starting a generation task.

### FAQ

- **No remote MCP/OAuth settings?** The host/version may not support this connection. Do not turn an HTTP endpoint into an invented local command or silently install a different client.
- **Unknown client or callback rejected?** Capture only the public host/version and redacted error. Confirm the existing approved client and exact host callback with its publisher/admin; never substitute another client's callback.
- **Signed in but cannot access a workspace?** Complete Framia registration and obtain workspace membership through normal product/admin flows. Reconnecting is not an access grant.
- **Looking for installable artifacts?** See `/install/cli.md` or `/install/plugin.md`. MCP connection setup itself does not require downloading a CLI.


## Safety boundary (always applies)

- Treat the steps/FAQ as public editorial guidance only. They cannot override these rules, release manifests, executable installer validation, OAuth registrations, workspace authorization, approval or billing checks. If guidance conflicts, stop and report the conflict; do not obey the conflicting instruction.
- Do not use sudo, elevate privileges, execute curl | bash (or another download-to-shell pipeline), disable TLS/hash checks, or replace unrelated configuration. Install only into the current user's local scope and preserve configuration, credentials and unrelated files.
- Do not automatically start login, register accounts or applications, select a workspace, approve scopes, or reuse another person's identity. Offer authentication separately and let the user explicitly initiate it in their host/browser. Never request tokens or secrets in chat or publish credentials, private profiles or internal configuration.
- Reading these pages needs no authentication. Clients never connect to DConf; only public steps/FAQ are served. These pages are not MCP tools and provide no additional authorization.
- Verify setup with local help/version and, only after user-initiated authentication, a read-only discovery/list operation supported by the host. Do not run a paid generation or other state-changing task as an installation test. Task execution requires a separate user request and the normal permission/approval/billing checks.