Connect with MCP

The account page is a notebook

Signed-in people can keep notes at Account → MCP: a platform name, a connection summary, and subscription notes. Those notes sync to the account. Keep keys, tokens, and passwords out of that page. Ludwitt does not host the third-party servers you write down. The Ludwitt server is the URL below.

Practice loop

Supported subjects are math, reading, Latin, Greek, and logic. Pass both when you want math and reading together. Writing stays on the website; the adaptive MCP tools do not serve it.

1. basics_get_progress
2. basics_get_current_problems with subject set to math, reading, latin, greek, logic, or both
3. Show the item in chat. The payload omits the answer. Use the item Ludwitt returned.
4. Collect the learner’s answer in chat.
5. basics_check_answer with the same problemId. The grade can include a reveal after the attempt.
6. Repeat.

alc_get_progress reads Developer Training progress. It is separate from the Basics loop.

Connect by signing in

Point an OAuth-capable client at the Ludwitt server. No API key is required for this path.

{
  "mcpServers": {
    "ludwitt": {
      "type": "http",
      "url": "https://pitchrise.ludwitt.com/api/mcp"
    }
  }
}

1. The client calls https://pitchrise.ludwitt.com/api/mcp.
2. Ludwitt answers with the public discovery documents /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. The authorization server is this site.
3. The client registers if it needs to (/api/mcp/oauth/register) and opens the browser at /oauth/mcp/authorize. The person signs in, if they are not already, and allows the requested access. The client finishes the sign-in itself, including PKCE, at /api/mcp/oauth/token.
4. Later tool calls run as that person.

If a tool returns missing_scope and asks you to reauthorize, sign in again and allow that access.

API key fallback

Use a key only when the client cannot complete sign-in.

1. Sign in and open Account → API Keys.
2. Create a key. Ludwitt shows the full value once. Store it in the client’s own secret store. Leave it out of Account → MCP, and out of any file you commit. A test key is the one to use while you are trying the connection. Test keys are rate-limited more tightly than live keys.
3. Choose scopes. For practice: basics:read, basics:write, and alc:read. For classes, add classes:read and classes:write. For institution setup, add orgs:write, invites:read, invites:write, billing:read, billing:write, and progress:read.

A key created with an empty scope list can call the other tools. It does not include billing:write. Add that scope when the agent should create a payment link or set a student cap. The class, invite, and credit steps are in the instructor quickstart.

Check the connection

• Listing tools includes basics_get_progress, basics_get_current_problems, basics_check_answer, and alc_get_progress. Educator tools appear for an account that is allowed to use them.
• basics_get_progress returns progress for math, reading, Latin, Greek, and logic.
• basics_get_current_problems returns a problem and omits the correct answer.
• basics_check_answer grades a practice answer and may then include a reveal.
• A missing or rejected credential fails closed.

If something fails

Unauthorized

Finish sign-in, or replace the key in the client’s secret store.

Sign-in repeats or is denied

Sign in on Ludwitt and approve the scopes on the consent screen.

Missing scope

Sign in again and allow basics:read, basics:write, or alc:read, or add the scope to the key. Institution tools need the educator scopes above.

Too many requests

Wait, then retry. Test keys hit this sooner.

Writing is rejected

The adaptive MCP loop covers the five subjects listed above. Writing stays on the website.