Skip to main content
Common issues and fast fixes when connecting Slashy MCP.
Fully quit and reopen the client. Some clients only trigger the OAuth flow on a fresh launch. If it still doesn’t open, check that your default browser is set and that popups aren’t blocked for slashy.ctrlcenter.ai.
Disconnect and reconnect the MCP server. In Claude Desktop, toggle the Slashy connector off and on in Settings → Connectors. In Claude Code, run claude mcp remove slashy then re-add it. In Cursor and Codex, delete the cached auth and restart.
Sign out of Slashy in your browser, then reconnect from your client. The OAuth flow will ask you to pick a Google account again.
Confirm the URL is exactly https://slashy.ctrlcenter.ai/mcp - no trailing slash, no typos. Check status.slashy.com for incidents. Try curl -I https://slashy.ctrlcenter.ai/mcp to confirm DNS and TLS reach the server.
Reconnect the MCP server in your client. A new browser OAuth flow will issue a fresh token. No data is lost.

Still stuck?

Overview

Re-check prerequisites and requirements.

Contact support

Email support@slashy.com with your client and error message.