Learn while the agent codes.

LearnThat gives your coding agent a small learning loop.

One MCP URL. Your normal coding agent.

Add LearnThat as a remote HTTP MCP server. The agent discovers the tools, opens OAuth when required, then weaves small learning moments into the work.

Run in a terminal

codex mcp add learnthat --url https://learnthat-mcp-3bqygzrtsa-uc.a.run.app/mcp
codex mcp get learnthat

After login, restart or open a fresh Codex session so the tools are available.

Add at user scope

claude mcp add --scope user --transport http learnthat https://learnthat-mcp-3bqygzrtsa-uc.a.run.app/mcp
# In Claude Code, run /mcp and choose Authenticate

User scope makes the server available across projects.

Remote MCP config

{
  "mcpServers": {
    "learnthat": {
      "url": "https://learnthat-mcp-3bqygzrtsa-uc.a.run.app/mcp"
    }
  }
}

Use this shape for clients that read an mcpServers JSON config.

HTTP server entry

{
  "servers": {
    "learnthat": {
      "type": "http",
      "url": "https://learnthat-mcp-3bqygzrtsa-uc.a.run.app/mcp"
    }
  }
}

If your client asks for a server URL directly, use https://learnthat-mcp-3bqygzrtsa-uc.a.run.app/mcp.

Pixel illustration of a learner and coding agent collaborating.

Agents can make people faster, but weaker at reasoning through code.

Coding agents remove friction. That is useful, but it can also skip the work where mental models form: predicting behavior, reading errors, writing the one line that matters, and explaining why a change works.

For new builders

The app ships, but the codebase stays opaque when the agent owns every decision.

For engineers

Velocity rises, but unfamiliar systems can still turn into copy-and-accept work.

Small checks, placed where they matter.

LearnThat does not take over the coding agent. It gives the agent one coaching tool: generate a short challenge when tests, builds, installs, searches, or deploys are already running.

  1. 1

    Before the change

    Ask for a prediction or risk call tied to the current task.

  2. 2

    During the change

    Invite the user to write or explain a tiny meaningful piece.

  3. 3

    After the change

    Record concepts, answers, snippets, and verification habits.

Pixel illustration of planning, prediction, code writing, and debugging moments.

Keep the flow, add a little resistance.

A good prompt is short enough to answer without derailing the task. The agent can ask a question, multiple-choice quiz, prediction, tiny snippet, debug prompt, or critique, then keep moving.

Soft prompts

Questions stay optional and tied to the file, error, or diff already in front of the user.

Useful memory

Answers and snippets become signals for the next challenge instead of dead chat history.

Soft by default. Different by level.

The agent keeps progress moving. Challenges adapt from the task, current concept, available wait time, and the amount of context already on screen.

Measure retained concepts, not just completed tasks.

Events land in a durable analytics store so schools, teams, and solo builders can see whether learning is improving over time.

Retention Concepts answered again after a delay.
Quiz quality Rolling score by topic, task type, and level.
AI dependency Skipped or weak checks compared with strong completions.

Test LearnThat in your coding agent.

Copy the MCP URL, add it to your client, and let your next coding session include small programming checks instead of passive code acceptance.

https://learnthat-mcp-3bqygzrtsa-uc.a.run.app/mcp