Connect another MCP client

Choose the connection your client supports

• Local MCP: your client launches the installed Tutor MCP binary with --local over standard input and output.
• Remote hobby service: add the public HTTPS endpoint ending in /mcp, sign in and authorise your client through OAuth.
• Native institution: use Tutor ACP’s authorised public-key identity and institution-origin connection in the Windows app guide.

The OAuth instructions on this page apply to the hobby profile. The current native institution profile uses its own signed-identity connection.

Client plans, extensions and administrator policies can affect availability. The examples describe connection routes; they are not a claim that every product and account has been tested end to end.

Claude Code: add the local server

First install the server. If tutor-mcp is available on PATH, add a user-scoped connection:

claude mcp add --transport stdio --scope user tutor -- tutor-mcp --local

If the command is unavailable, use the full installed executable path in its place. Follow Claude Code’s MCP configuration guide for its current connection checks and project-scoped settings.

Claude Desktop and clients using MCP JSON

Merge this entry into the client’s existing MCP configuration, then restart the client. Replace the example path with the installed Tutor binary. Claude Desktop exposes its configuration through Settings → Developer → Edit Config.

{
  "mcpServers": {
    "tutor": {
      "command": "/absolute/path/to/tutor-mcp",
      "args": [
        "--local"
      ]
    }
  }
}

For Windows, use a path such as C:/Users/you/AppData/Local/Programs/tutor-mcp/tutor-mcp.exe. Keep the --local argument as a separate array item.

Gemini CLI also supports an mcpServers configuration. Other clients can use a different schema; consult the client configuration map and the selected product’s documentation before copying settings.

Hermes: use its YAML configuration

Add the server to ~/.hermes/config.yaml, using an absolute command path if required, then start Hermes:

mcp_servers:
  tutor:
    command: tutor-mcp
    args: ["--local"]

See the Hermes MCP guide for client-specific behaviour. Pi uses an MCP extension or bridge; its extension determines the configuration format.

Remote connectors: use HTTPS and authorise access

Cloud-hosted assistants need a reachable remote service. For a hobby VPS, give the client this endpoint:

https://tutor.example.org/mcp

1. Add the endpoint using the client’s MCP or custom-connector settings.
2. Complete Tutor’s sign-in flow with your invited hobby account.
3. Review and approve the client’s requested access.
4. Return to the assistant and check that the Tutor tools are available.

A publicly trusted HTTPS certificate is required. Clients such as ChatGPT, Claude on the web and Le Chat have their own connector availability and account requirements; use the current product links in the client guide.

In Tutor ACP’s institutional settings, the address is instead the origin https://tutor.example.org, without /mcp, so the application can discover and verify the institution.

Check the learning loop and resume later

Use Tutor MCP to help me learn Go. Find out what I already know, create a learning plan and guide me through a first 20-minute session. Save my progress when we finish.

The assistant must use Tutor’s tools to obtain context and record work. A conversation that does not call the learning service does not update its learning record.

Later, ask “Resume my Go learning with Tutor MCP.” Connect to the same server or local profile to retain that history. Multiple local clients can share the same profile; independent profiles are not automatically synchronised.

Keep going.