AlgoReps

AI + MCP

AlgoReps can now travel from an AI assistant into the website.

The public value of MCP is not that it magically makes ChatGPT rank AlgoReps. The value is that AI clients can use AlgoReps as a real tool, let someone start an anonymous Blind 75 review session, and then hand that progress into the site when they want to keep going.

What MCP does

It gives AI clients a tool surface.

MCP is a protocol that lets an AI client call real tools instead of only talking about them. In AlgoReps, that means an MCP-capable client can start a Blind 75 session, review problems, and generate a continue link back to the website.

Think of it as a distribution surface and a workflow bridge, not a guaranteed recommendation engine.

What the public gets

A lower-friction path into real interview practice.

Someone talking with an AI assistant about coding interview prep can use AlgoReps without creating an account first. If the flow is helpful, they can continue on the website with the same anonymous Blind 75 progress instead of starting over.

  • Anonymous Blind 75 only
  • No account required to start
  • Website handoff keeps the practice moving

How the handoff works

Start in an AI assistant, continue on AlgoReps.

  1. An MCP-capable AI client starts an anonymous Blind 75 session.
  2. AlgoReps stores that guest progress on the server.
  3. The client generates a continue link for the user.
  4. The user opens the link on algoreps.io.
  5. AlgoReps imports that session into anonymous browser progress and opens the homepage.

That keeps the website conversion path low-friction. People can try the workflow first, then decide whether they want synced progress and paid features later.

For discoverability

`llms.txt` and MCP do different jobs.

`llms.txt` helps models understand what AlgoReps is. MCP helps compatible clients use AlgoReps as a tool. Together, they make AlgoReps easier to understand, easier to integrate, and easier to continue using on the website.

For developers

The protocol endpoint is machine-first.

The human-readable explanation lives on this page. The actual MCP endpoint is /mcp, which is meant for clients, not for a normal browser landing page.

Current scope is intentionally narrow: anonymous only, Blind 75 only, plus public search and fetch tools.

An unhandled error has occurred. Reload x

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please reload the page.