Connect an AI assistant

1. Sidebar → Customize → Connectors.

   The free Claude plan allows one custom connector. If yours is already taken, free it up or use another client.

   

2. Top right: Add → «Add custom connector».

   

3. Name — L-System (any name, it is only shown in the list). Address — https://www.lsystem.app/mcp.

   

4. Leave OAuth Client ID and Client Secret empty under «Advanced settings»: our server registers the client itself. Press Add.

5. A sign-in page opens, then a consent screen. Allow access.

   Restart Claude Desktop. Until you do, the tool list stays cached and the assistant honestly says it has no such tools.

   

If your screen looks different — tell us, the client has changed.

1. Sidebar → Customize → Connectors.

   The free Claude plan allows one custom connector. If yours is already taken, free it up or use another client.

   

2. Top right: Add → «Add custom connector».

   

3. Name — L-System. Address — https://www.lsystem.app/mcp. Client ID and Client Secret stay empty.

   

4. Sign in, allow access, then reload the tab.

If your screen looks different — tell us, the client has changed.

1. A paid ChatGPT plan is required.

   On the free plan the Plugins section exists and the app can even be created, but its tools never reach the conversation — the assistant then looks for a plugin by name in the public catalogue and reports plugin_not_found.

2. Sidebar → «Plugins». Top right: «+».

   

   

3. Name — LSystem. Connection — «Server URL», address https://www.lsystem.app/mcp. Authentication — OAuth. Client ID and Client Secret are not needed: our server registers the client itself.

   

4. The icon is optional. Ours is right below — PNG, under 10 KB, the size ChatGPT asks for.

   Download the icon for the connector (PNG, 64×64)

5. Tick «I understand and want to continue» and press «Create». ChatGPT scans the tools and offers to sign in — «Sign in with LSystem» — and then our consent screen opens.

   

6. In a new chat, pick L-System from the tools menu. A developer-mode app is not switched on by itself: without this the assistant sees no tools at all.

   

7. Permissions can stay at «allow low-risk actions»: our tools declare their nature, so reading and the ordinary steps of a lesson go through on their own. ChatGPT will ask you before a call that takes something back for good — issuing an exam link, which burns an attempt.

The screenshots were taken with a Ukrainian ChatGPT interface: your button labels will be in your own ChatGPT language, the layout is the same.

If your screen looks different — tell us, the client has changed.

1. Open the settings file and add the mcpServers block below. If the file already has other sections, keep them — add only mcpServers.

   The field is httpUrl, not serverUrl: with the wrong name the CLI starts silently and shows no tools.

   ~/.gemini/settings.json

   {
     "mcpServers": {
       "LSystem": {
         "httpUrl": "https://www.lsystem.app/mcp",
         "authProviderType": "dynamic_discovery",
         "oauth": {
           "enabled": true,
           "scopes": ["learner"]
         },
         "timeout": 30000,
         "trust": false,
         "description": "LSystem: каталог курсов, материалы и прогресс. Экзамен сюда не приходит."
       }
     }
   }

2. authProviderType: dynamic_discovery means sign-in happens through our site — no keys and no token in the file.

3. Restart the CLI. On the first call it opens a browser for sign-in.

   

If your screen looks different — tell us, the client has changed.

1. Settings → Customizations → «Installed MCP Servers» → «Open MCP Config».

   

   

2. Add the block below.

   Here the field is serverUrl — Antigravity names it differently from Gemini CLI. With the wrong name the client starts silently and shows no tools.

   ~/.gemini/config/mcp_config.json

   {
     "mcpServers": {
       "LSystem": {
         "serverUrl": "https://www.lsystem.app/mcp",
         "authProviderType": "dynamic_discovery",
         "oauth": {
           "enabled": true,
           "scopes": ["learner"]
         },
         "timeout": 30000,
         "trust": false
       }
     }
   }

3. Sign-in goes through our site: no token in the file. If your build of the client does not understand dynamic_discovery yet, use the token fallback described under these tabs.

4. Restart the client and allow access in the browser window that opens. The connector list should show the tools; their number is a good sanity check.

If your screen looks different — tell us, the client has changed.