Troubleshooting
Resolve common endpoint, OAuth authorization, email verification, and MCP tool discovery issues.
Common issues
These solutions apply across supported AI assistants.
Confirmation email did not arrive
Check your Spam or Junk folder and verify that the email address was entered correctly. If the message still does not arrive, start the sign-in flow again and request a new confirmation email.
Confirmation link is expired or does not open
Start the sign-in flow again and request a new verification email. Confirmation links are time-limited and should be opened in the same browser session where possible.
The client asks to sign in again
Complete the OAuth flow in the same browser window opened by the client. Allow cookies and popup windows, then return to the client only after sign-in has completed.
The server cannot be added
Check that the public OAuth endpoint is exactly https://mcp.glushkov-modelling.com/mcp-oauth. Do not use the legacy /mcp endpoint, a Keycloak URL, or an API key.
Tools do not appear after OAuth
Close and reopen the chat or application, then check the connector status in the client settings. Confirm that the connector is connected and enabled for the current chat or Agent session.
Perplexity
Connection issues that may apply when using Glushkov Modelling MCP with Perplexity.
Connection to MCP server expired
This is normal if you haven’t used the MCP connection for a long time. Click “Reconnect” in the email you received, then complete the authentication using the username and password you created during registration.
Visual Studio Code
Connection issues that may apply when using Glushkov Modelling MCP with Visual Studio Code.
“Client not found” message
Uninstall MCP server. Remove authentication providers using command in Command Palette [Authentication: Remove Dynamic Authentication Providers], then Add MCP server again.