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.
Status and evidence
Status is the same word the Connect page shows, for every client. Evidence is how we know: Automated (a clean install runs in Mediafier's CI on every relevant change), Manual (a person connected the client and completed a governed call on the date shown), Configuration shape (the setup follows the client's documented format; not yet run against Mediafier by us), or Untested (not yet verified with Mediafier). Setup links to the client's steps on the client bootstrap.
Matrix
Supported
Tested with Mediafier and ready to connect.
Preview
Setup is available while we complete compatibility testing.
Temporarily unavailable
There's a known compatibility issue with this client.
Coming soon
Support for this client isn't available yet.
Perplexity
Assistant apps
Browser sign-in
Coming soon
Untested
—
—
Microsoft 365 Copilot (declarative agent)
Assistant apps
Pre-issued OAuth client
Preview
Configuration shape
2026-09-26
Microsoft 365 Copilot (custom federated connector)
Assistant apps
Pre-issued OAuth client
Coming soon
Untested
—
—
Raycast
Assistant apps
Browser sign-in
Coming soon
Configuration shape
2026-09-24
—
Cline
IDEs
Browser sign-in
Coming soon
Configuration shape
2026-09-24
—
OpenAI Agents SDK
Your own code and agent platforms
Access token
Preview
Configuration shape
2026-05-15
Anthropic MCP connector (API)
Your own code and agent platforms
Access token
Preview
Configuration shape
2026-05-15
AWS Bedrock AgentCore
Your own code and agent platforms
Pre-issued OAuth client
Preview
Configuration shape
2026-05-15
What "Sign-in" means
"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. 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 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
Setting up a specific client
Choosing how your agent will authenticate
Planning for change
Last updated