Features

Download

Hosted MCP · OAuth 2.1

One endpoint. Your AI repairs with Fixo.

Q: What is Fixo MCP Server?

Fixo MCP Server is a Model Context Protocol implementation that allows AI agents to repair corrupted video, photo, document, archive, and audio files through 4 standardized MCP tools.

Q: Which AI clients support Fixo MCP?

Any MCP-compatible client supporting Streamable HTTP: Claude Desktop, Claude Code, Cursor, GitHub Copilot, ChatGPT, Google Gemini, Windsurf, Trae, Continue.dev, Cline, Roo Code, and 50+ more.

Q: Is Fixo MCP free to use?

Yes. All users get 1 free repair per day (100 MB max). EaseUS Pro account holders get unlimited repairs per day. Files over 100 MB require the desktop client.

Q: Do I need to install anything?

No. Fixo MCP is a cloud service accessed via the Streamable HTTP endpoint. You only need an MCP-compatible AI client.

Q: Where do I find my repaired files?

When a task reaches Completed, sign in with your account at repair.easeus.com/history-repair/ to preview and download the repaired file. No watermark, full original quality.

Q: How long does repair take?

Most files repair within 30–60 seconds. Larger or severely corrupted files may take a few minutes. The get_repair_status tool provides real-time progress (0–100).

Fixo lets compatible AI agents inspect and repair corrupted video, photos, documents, archives, and audio, then return a result link.

3 repair tools

100+ supported formats

Automatic OAuth refresh

MCP endpoint

            https://repair.easeus.com/fixo-mcp/v1

Copy endpoint

Fastest start · Prompt

            Add MCP server: https://repair.easeus.com/fixo-mcp/v1, OAuth 2.1 Authorization Code + PKCE (S256), no API key required. Then use the fixo MCP tool to repair {file path}.

Copy prompt

One connection, four repair domains

Fixo MCP gives compatible AI agents four tools for file health checks, video repair, photo repair, document and archive repair, audio repair, and repair-status tracking. It supports 100+ common camera, mobile, office, archive, and audio formats through one Streamable HTTP connection.

Video repair

repair

Repairs corrupted video containers, indexes, timestamps, tracks, headers, and playable stream structures when a recording will not open, seek, or finish correctly.

Pick your AI client

Get connected

Choose the setup method that matches your AI client. Configuration screens can change between client versions, so use the complete Fixo MCP guide when you need tool schemas, OAuth details, troubleshooting, or manual configuration.

Fixo MCP integration guide

Endpoint setup, OAuth flow, six tool schemas, supported formats, errors, and complete examples

Read the guide

Claude Desktop

Developer settings · JSON config

Open Settings → Developer → Edit Config, add the server below, then restart Claude Desktop. Type /mcp, select fixo, choose Authenticate, and follow the OAuth flow.

{ "mcpServers": { "fixo": { "type": "http", "url": "https://repair.easeus.com/fixo-mcp/v1" } } }

Copy config

Codex

CLI · one-line add

Add the server from your terminal, then complete the OAuth flow when Codex prompts you.

codex mcp add fixo --url https://repair.easeus.com/fixo-mcp/v1

Copy command

Claude web (claude.ai)

Go to Settings → Connectors, click Add in the top right → Add custom connector. Use fixo as the name and the endpoint as the URL, click Add, then complete OAuth.

ChatGPT

Create a custom app or connector in ChatGPT settings, add the endpoint as a developer MCP server, enable it for your workspace, then complete OAuth.

Cursor

Settings → MCP Servers → add a Remote MCP Server and paste the endpoint above.

Other clients

Any client implementing the MCP OAuth 2.1 standard can usually connect via "add custom MCP server / connector" with the endpoint above. Fixo MCP currently offers no alternative to browser-based authorization, so use a client that can open a browser; if connecting fails, update the client to its latest version first.

Standard OAuth 2.1, no API key needed

Fixo MCP uses standard OAuth 2.1, so you never hand an API key or token to the client. In most MCP clients the first tool call triggers authorization in your browser.

Start the connection

After adding the Fixo MCP configuration, the first tool call triggers authorization.

Browser handoff

The client opens a browser on the Fixo sign-in and consent page, with a short-lived device code.

Approve access

Review the requested repair scopes in the browser and approve access for the client.

Session established

Once authorized, the client holds the credentials and the MCP tools are ready.

Credential upkeep

Access tokens are valid for 12 hours; your client refreshes credentials automatically per the OAuth policy.

repair: read

Inspect files and read repair status

repair: write

Start repair tasks and write results

Check first. Repair second.

Every repair starts from a health check and works only on the file you select. Source files are deleted as soon as the repair completes; result files after 12 hours or the first download.