Skip to the document

Support

Email hello@lymi.app for help with Lymi. The notes below solve the most common sign-in and connection problems.

Last updated 13 September 2026

Contact Lymi

Email hello@lymi.app. If the problem involves an account, write from the email address you use to sign in. Include what you were trying to do, what happened, and the browser or connected app you were using.

Do not send passwords, API keys, OAuth tokens, private lesson text or a full export unless we specifically ask for a safe, limited example. A screenshot should hide private card content and account details that are not needed to explain the problem.

Sign-in help

  1. Open Lymi sign-in and choose the Google account that was invited.
  2. If you see that the app is private, check that you selected the approved email address.
  3. If sign-in returns to the wrong page, start again from the Lymi page you meant to open.
  4. If the problem continues, send us the exact message and the time it happened. Do not send the callback URL if it contains a code or token.

Connected-app help

  1. In Lymi Settings, confirm the app appears under Connected apps and has the permission you intended.
  2. If permissions are wrong, disconnect it, then connect again and choose read-only or read-and-write on the consent screen.
  3. If you do not recognize a connected app, disconnect it immediately and contact us.

See the MCP overview for how permissions work and the setup guides for Claude and ChatGPT and Codex.

API help

  1. Send the key in the x-api-key header, never in a URL.
  2. Check that the key still exists in Settings and has the scope the request needs.
  3. A 401 usually means the key is missing, wrong or revoked. A 403 means the key does not have permission for that action.
  4. If a key may have leaked, revoke it and create a new one before contacting support.

Use the authentication guide and API reference for request details.

MCP connection help

  1. Use https://my.lymi.app/mcp as the server URL.
  2. Complete Google sign-in and the Lymi consent screen in the browser window that opens.
  3. If the client says registration or authorization failed, check its Lymi setup guide and remove any older Lymi connection before adding it again.
  4. Send support the client name, the exact error text and the time it occurred. Never send its token.

Access, export, correction or deletion

These account-wide requests are handled by email while self-service tools are not available. Write to hello@lymi.app from your account address and say whether you want access, an export, a correction or deletion. We may ask you to verify your identity before acting. Removing a beta request can be requested the same way.

Security reports

If you believe you found a security issue, email hello@lymi.app with a concise description and safe reproduction steps. Do not access another person’s data or include live credentials.