> ## Documentation Index
> Fetch the complete documentation index at: https://help.slashy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slashy MCP Troubleshooting

> Fix common Slashy MCP setup issues: OAuth, missing tools, wrong account, and server errors.

Common issues and fast fixes when connecting Slashy MCP.

<Frame>
  <img src="https://mintcdn.com/karvixinc/Cf5d-qp20wjPdVvk/images/mcp/codex-verify.png?fit=max&auto=format&n=Cf5d-qp20wjPdVvk&q=85&s=99de768d37f14bbdb94cb68c005ff24d" alt="The /mcp diagnostic output listing connected servers, their auth type, and exposed tools -- the first thing to check when tools are missing" width="2288" height="384" data-path="images/mcp/codex-verify.png" />
</Frame>

<AccordionGroup>
  <Accordion title="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`.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="MCP server not responding">
    Confirm the URL is exactly `https://slashy.ctrlcenter.ai/mcp` - no trailing slash, no typos. Check [status.slashy.com](https://status.slashy.com) for incidents. Try `curl -I https://slashy.ctrlcenter.ai/mcp` to confirm DNS and TLS reach the server.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## Still stuck?

<CardGroup cols={2}>
  <Card title="Overview" icon="book" href="/how-to-guides/slashy-mcp-overview">
    Re-check prerequisites and requirements.
  </Card>

  <Card title="Contact support" icon="envelope" href="mailto:support@slashy.com">
    Email [support@slashy.com](mailto:support@slashy.com) with your client and error message.
  </Card>
</CardGroup>