OAuth window didn't open
OAuth window didn't open
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.Tools aren't appearing in chat
Tools aren't appearing in chat
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. In Hermes, run hermes mcp test slashy, then /reload-mcp in your session.Hermes: added the server but it never connects
Hermes: added the server but it never connects
Two common causes. First, the entry must sit under the top-level
mcp_servers: key in ~/.hermes/config.yaml - not a nested mcp: servers:. Second, if you edited the config from inside a running Hermes session, the 30-second auto-reload timeout cuts the OAuth flow short. Run hermes mcp login slashy from a fresh terminal instead. See Hermes setup.Signed in with the wrong account
Signed in with the wrong account
Sign out of Slashy in your browser, then reconnect from your client. The OAuth flow will ask you to pick a Google account again.
MCP server not responding
MCP server not responding
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.Token expired or permission revoked
Token expired or permission revoked
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.