Start a Free Trial

Common Issues - Troubleshooting

General Diagnostic Checklist

Before checking client-specific sections, run through these four steps:

  • Verify the endpoint URL — must be exactly https://ai-mcp.insyncanalytics.com/mcp (with /mcp path, with https://)
  • Confirm your InSync account is active — log in at insyncanalytics.com to verify
  • Re-authenticate — remove the server from your client, re-add it, and complete the OAuth flow again
  • Check your rate limit — if you've made many requests recently, wait 60 seconds and try again

ChatGPT

Problem: "InSync Analytics MCP" does not appear in my apps list
  • Ensure Developer Mode is enabled: Settings → Apps → Advanced Settings → Developer Mode ON.
  • The app will appear under Drafts (Settings → Apps → Drafts) after creation, not in the main apps list. Check Drafts.
Problem: App is in Drafts but the Authenticate button does nothing
  • Try a different browser. Pop-up blockers can intercept the OAuth redirect.
  • Temporarily disable browser extensions (ad blockers, privacy tools) and retry.
  • Ensure you are signed into your InSync account in the same browser before clicking Authenticate.
Problem: Authentication completes but the app stays in Drafts
  • Refresh the ChatGPT Settings page.
  • If the app still shows in Drafts after 30 seconds, delete it and create a new app from scratch using the same configuration.
Server connected but ChatGPT does not use it for financial questions
  • Developer Mode must be active in the active chat session, not just in Settings. Check the toolbar in the chat window.
  • Start a new chat after confirming Developer Mode is on.
  • Explicitly ask: "Use InSync Analytics MCP to find Apple's revenue" — this prompts the model to invoke the tool.
Problem: "This feature requires a paid plan"
  • ChatGPT's custom app/MCP support requires Plus, Pro, Business, or Enterprise. Upgrade your ChatGPT subscription or use a different client (Claude Desktop, Claude Code, etc.).

Claude Desktop

Problem: Server does not appear after adding the connector
  • Ensure you fully quit and restarted Claude Desktop — closing the window is not enough. Use Quit from the menu bar or Dock.
Problem: No OAuth prompt appears
  • Check that the url field in the config matches exactly: https://ai-mcp.insyncanalytics.com/mcp
Problem: Server shows as connected but returns authentication errors
  • The stored token may have expired or been invalidated. Remove the insync-analytics connector from settings, then add the block back and re-authenticate.

Claude Code

Problem: claude mcp add command not found
  • Ensure you have Claude Code CLI installed and updated to a recent version: claude --version
  • Update with: npm update -g @anthropic-ai/claude-code (or however you installed it)
Problem: Server added but does not appear during sessions
  • Run claude mcp list to confirm the server is registered.
  • If registered at user scope, it should be available in all sessions. If at project scope (--scope project), ensure you are running Claude Code from the correct directory that contains .mcp.json.
Problem: OAuth browser window does not open
  • Claude Code opens the browser automatically. If your environment does not have a browser (e.g., remote SSH session), the OAuth URL will be printed to the terminal. Copy and open it in a local browser, complete login, then return to the terminal.
Problem: Token stored but every session asks to authenticate again
  • Check that your home directory is writable — Claude Code stores OAuth tokens in ~/.claude/.
  • On shared servers or containers, the home directory may be ephemeral. Use --scope project and ensure the project directory persists between sessions.
Problem: "Server returned status 429"
  • You have hit the rate limit. Wait at least 60 seconds and retry. If you are scripting multiple calls, add delays between requests.

Cursor / VS Code

Problem: Cursor MCP Settings page shows the server as "disconnected" or "error"
  • Verify the config syntax. For Cursor and VS Code, the key is "type": "http" (not "streamable-http" as in Claude Desktop).
  • Restart Cursor/VS Code after editing the config file.
Problem: VS Code does not recognize the .vscode/mcp.json file
  • Requires VS Code version 1.99 or later. Check your version: Help → About. Update if needed.
  • The file must be named exactly mcp.json inside the .vscode/ directory at the workspace root.
Problem: "Cannot connect to MCP server" in the Cursor MCP panel
  • Test the endpoint is reachable from your machine: open https://ai-mcp.insyncanalytics.com/mcp in a browser — you should receive a JSON response, not a connection error.
  • Check firewall or corporate proxy settings that might block outbound HTTPS to ai-mcp.insyncanalytics.com.
Problem: Cursor uses the AI without invoking the MCP server
  • The AI needs to be explicitly asked about financial data. Try: "Using InSync Analytics, what is Apple's P/E ratio?"
  • Confirm the server shows as active (green dot) in Settings → MCP.

Gemini CLI

Problem: Gemini CLI does not recognize the serve
  • Confirm the config uses "httpUrl" (not "url"). This is a Gemini CLI–specific key name.
  • Check that ~/.gemini/settings.json is valid JSON. A syntax error in the file will cause Gemini CLI to ignore all MCP servers.
Problem: Timeout errors on financial data requests
  • The default "timeout": 30000 (30 seconds) should be sufficient for most queries. Complex document parsing may take longer. Try increasing to 60000.
Problem: OAuth flow does not complete
  • Gemini CLI opens a browser for OAuth. If you are in a headless environment, the URL will be printed to stdout. Copy and open in a browser, complete login.
  • If the token callback fails, delete ~/.gemini/ credentials and re-authenticate.
Problem: insync_assistant tool not visible to Gemini
  • After editing settings.json, restart Gemini CLI completely.
  • Confirm the "mcpServers" key is at the top level of the JSON object, not nested inside another key.
Error message Likely cause Fix
Rate limit exceeded Too many requests in 60s or 1h window Wait for window reset (60s for per-minute, up to 1h for per-hour)
Authentication required No valid token Re-authenticate via OAuth
Tool not found Tool name does not match any registered tool Check spelling against the tools list
Connection refused / 502 Bad Gateway Server temporarily unavailable Wait a few minutes and retry

Still Stuck?

Contact InSync Analytics support:

  • Email: support@insyncanalytics.com
  • Include in your message:
    • Which AI client you are using and its version
    • The exact error message or unexpected behavior
    • The endpoint URL you are connecting to
    • Whether authentication completed successfully

©Copyright 2025 InSync Analytics Corp. All Rights Reserved.