> For the complete documentation index, see [llms.txt](https://docs.mediafier.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediafier.ai/connect/compatibility.md). # Compatibility Which agent harnesses, IDEs, connectors, SDKs and cloud runtimes connect to Mediafier today, how each was verified, and when. > **Any MCP-aware client can connect. Here is what we have actually verified, and how.** Every row carries the date and the method, so a claim is never older than it looks. Mediafier speaks standard MCP over one canonical endpoint (`POST https://mcp.mediafier.ai/mcp`). Compatibility therefore rests on the client, not on Mediafier-specific code. The table separates what is proven in an automated clean-install check, what a person verified by hand on a given date, and what is documented from the client's own configuration format without a Mediafier-specific run. > **Each row carries its own date, and that date is the only freshness claim this page makes.** There is deliberately no single page-level "verified on" stamp: one date in front of seventeen differently-aged claims reads as freshness the rows do not have. A row dated months ago is telling you something true — read the date, not the page. ## How to read the verification column | Verification | Meaning | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | **Automated** | A clean install of the client against Mediafier runs in Mediafier's CI on every relevant change. | | **Manual (date)** | A person connected this client to Mediafier and completed a governed call on the date shown. | | **Configuration shape** | The setup shown in [MCP Access](/connect/mcp-access.md) follows the client's documented format; not yet run against Mediafier by us. | | **Untested** | Known to accept a custom remote MCP server by URL; not exercised with Mediafier. | ## Matrix | Client | Kind | Sign-in | Verification | Last checked | | ------------------------------ | --------------- | --------------------------------------------------------------- | ------------------------------------------------- | ------------ | | Claude Code (HTTP) | CLI harness | Browser OAuth or pre-issued OAuth client | **Automated** | 2026-08-28 | | Claude Code (stdio) | CLI harness | Access token from the environment | **Automated** | 2026-08-28 | | Mediafier CLI | First-party CLI | Browser OAuth (PKCE) — **staging only today** — or access token | **Automated** — staging release checks | 2026-09-12 | | Claude Connectors (add-by-URL) | Connector | Browser OAuth (dynamic client registration) | Configuration shape — sign-in observed 2026-08-22 | 2026-09-12 | | Claude Desktop | Desktop app | Access token | Manual — 2026-05-15 | 2026-05-15 | | Cursor | IDE | Browser OAuth | Configuration shape | 2026-05-15 | | VS Code (GitHub Copilot MCP) | IDE | Browser OAuth or pre-issued OAuth client | Configuration shape | 2026-05-15 | | Windsurf | IDE | Browser OAuth | Configuration shape | 2026-05-15 | | Codex CLI | CLI harness | Browser OAuth or access token | Configuration shape | 2026-05-15 | | Claude CoWork | Workspace | Browser OAuth | Configuration shape | 2026-05-15 | | OpenClaw | Agent harness | OAuth via the harness's login command | Configuration shape | 2026-05-15 | | Hermes Agent | Agent harness | Access token | Configuration shape | 2026-05-15 | | OpenAI Agents SDK | SDK | Access token from the environment | Configuration shape | 2026-05-15 | | Anthropic MCP connector (API) | SDK / API | Access token | Configuration shape | 2026-05-15 | | AWS Bedrock AgentCore | Cloud runtime | OAuth credential provider | Configuration shape | 2026-05-15 | | ChatGPT (developer mode) | Assistant | OAuth custom connector | Untested | — | | Perplexity | Assistant | OAuth custom remote connector | Untested | — | ### Production vs staging sign-in One caveat this table cannot express in a single column. The **Mediafier CLI**'s browser (PKCE) sign-in is registered for **staging only** today — its production native OAuth client is not yet provisioned. Access-token sign-in works in both environments, and every other row's sign-in path is environment-independent. How the CLI behaves today, stated precisely, because the two halves differ: * `mediafier mcp configure`, `mediafier mcp stdio` and `mediafier verify claude-code` **refuse** `--env production` with a clear error rather than acting against the wrong environment. * `mediafier auth login` **does not yet honour `--env` at all.** It signs you into **staging** regardless of the flag. If you need a production token today, use access-token sign-in; do not rely on `--env production` here. "Sign-in" names the path a person or agent uses to obtain the access token the client presents; the token itself is always what reaches Mediafier — see [Authentication & Agent Credentials](/connect/authentication.md). Headless clients obtain it with the machine-credential contract published in the Agent Card. ## What compatibility does not mean * A row marked **Configuration shape** is not a promise that the client works today with Mediafier; it is the setup we expect to work, from the client's own documentation, awaiting a run. * Client software changes. A row's date is the last time we checked; if a client's configuration format moves, the setup in [MCP Access](/connect/mcp-access.md) may lag until the next check. * Compatibility says nothing about what a given organization can call: authenticated discovery (`tools/list`, `resources/list`) is the authority for that. ## Where to go next | If you're… | Read next | | ----------------------------------------- | ---------------------------------------------------------------- | | Setting up a specific client | [MCP Access](/connect/mcp-access.md) | | Choosing how your agent will authenticate | [Authentication & Agent Credentials](/connect/authentication.md) | | Planning for change | [Releases & Deprecation](/connect/release-and-deprecation.md) |