← All docs

    Connect to Claude

    Before you start

    You need a Lexomat account with MCP access (trial, starter, or plus — see Access tiers). You'll sign in to that account during setup.

    Steps

    1. Open Claude and go to Settings / Customize → Connectors.

    2. Click "+ Add custom connector".

    3. Paste the server URL:

      https://mcp.lexoma.sk/mcp

      The connector appears in Claude as Lexoma. Add only this one connector — if you already added the older lexomat connector, it keeps working and you do not need a second one.

    4. Under Advanced settings, leave OAuth Client ID and OAuth Client Secret blank. Claude registers itself with Lexomat's sign-in server automatically — this is the correct setup, not a temporary one.

    5. Confirm. You'll be redirected to sign in at lexomat.sk (OAuth) — Lexoma is the connector's name, and you sign in with the same Lexomat account. Approve the connection.

    That's it — Claude can now call the Lexomat tools described in Overview.

    How sign-in works (and why both fields stay blank)

    Lexomat's connector uses standard OAuth: Claude sends you to lexomat.sk to sign in, and the token it receives is valid only for Lexomat's MCP connector. Before that redirect, Claude needs an OAuth client identity. The MCP specification (revision 2026-07-28) allows three ways to obtain one, in this order of preference:

    1. Pre-registered client credentials — a Client ID the server operator issues, entered under Advanced settings. Lexomat does not issue these, so there is nothing to enter here.
    2. Client ID Metadata Documents — Claude identifies itself with a URL it hosts. Lexomat's sign-in server (Supabase Auth) does not advertise support for this yet, so Claude does not use it here.
    3. Dynamic Client Registration — Claude registers a fresh OAuth client on every new connection. This is what happens when you leave the fields blank. It works, but the 2026-07-28 revision marks it deprecated — retained for backwards compatibility with authorization servers that do not support Client ID Metadata Documents.

    So blank fields are the right setup, not a stopgap. Nothing to copy, nothing to store, nothing to rotate.

    Team / Enterprise

    An organization owner can add the connector once under Organization settings → Connectors, making it available to the whole workspace.