Troubleshoot and manage Vani MCP
Claude says it cannot reach the MCP server
- Check that you entered the correct Vani MCP server URL and that it ends with /mcp. Example: https://app.vanihq.com/mcp.
- Do not use a private, local, staging, or VPN-only URL unless Vani support has asked you to test one. Claude custom connectors connect from Claude's cloud infrastructure, so the MCP server must be reachable over the public internet.
The sign-in window does not open
- Disconnect and reconnect the Vani connector from Claude settings.
- If your browser blocks pop-ups or redirects, allow them for Claude and Vani, then try again.
I signed in, but Claude still cannot use Vani tools
- Make sure the Vani connector is enabled in the current Claude conversation. Adding a connector and enabling it in a chat can be separate steps.
- Check that your Vani account has access to the team, Space, Zone, or action you're asking about.
Claude says "permission denied" or "access denied"
Your Vani role may not allow that action. Ask a Vani admin or a Space organizer for the required access, or ask the assistant to perform a read-only task instead.
Claude keeps asking you to reconnect
Remove the Vani connector from Claude and add it again using the correct Vani MCP server URL. This starts a fresh secure sign-in flow.
You connected to the wrong Vani data center
Remove the connector and add it again using the correct regional URL. Your Vani account and data must be in the same data center as the MCP server URL.
Information to send Vani support
If the problem continues, contact Vani support (support@vanihq.com) with:
- Your Vani data center or app domain.
- The approximate time of the failed connection.
- The exact error shown in Claude.
- Whether you are using Claude Free, Pro, Max, Team, or Enterprise.
- Whether you are setting up a personal connector or an organization connector.
Do not send passwords, access tokens, refresh tokens, authorization codes, or browser cookies.