Skip to the page
Lymidocs

Assistants

Claude

Claude connects to Lymi as a custom connector on the web and in the desktop app, and as a remote MCP server in Claude Code. All three use the same URL and the same sign-in.

MCP server URL
https://my.lymi.app/mcp

Once connected, ask Claude to add the cards from a lesson, list what is due, or find a card. What it can and cannot do is on Connect an assistant.

Claude Desktop and claude.ai

Custom connectors live in the same place in the app and on the web.

  1. Open the connector list

    Go to Settings → Connectors. On a Team or Enterprise plan an owner adds it once under Organization settings → Connectors, and everyone else then connects to it.

  2. Add a custom connector

    Choose Add custom connector and paste the URL above. Leave the advanced OAuth fields empty: Lymi tells Claude where to sign in through the protocol, so there is no client id or secret to fill in.

  3. Sign in

    Claude opens Lymi in your browser. Sign in with the Google account your Lymi uses, then approve the connection. Untick write on the consent screen if you want Claude to read your decks and nothing more.

  4. Turn it on in a conversation

    Connectors are per conversation. Click + in the composer, choose Connectors, and enable Lymi.

Claude Code

Add the server once, then authenticate from inside a session.

Terminal
claude mcp add --transport http lymi https://my.lymi.app/mcp

Start Claude Code and run /mcp. It lists Lymi as needing authentication and opens the browser for you. From v2.1.186 you can do the same without the slash command:

Terminal
claude mcp login lymi     # sign in
claude mcp logout lymi    # forget the tokens

Tokens are stored by Claude Code and refreshed on their own. To disconnect for good, revoke the grant in Lymi as well as running logout.

When it does not connect

  • Sign-in is refused. Lymi is private. Only the accounts on its allowlist can sign in, whatever the Claude account is.
  • The connector never gets past the URL. Lymi has no dynamic client registration, by design. A client that cannot use a Client ID Metadata Document has no way to identify itself here.
  • Claude says it can only read. The token was granted read only. Reconnect and leave write ticked at the consent screen.