Connect Your AI Client

Prerequisites

Before connecting, you need:

  • An active InSync Analytics account (required for all clients)
  • One of the supported AI clients listed below

MCP Endpoint

URL
https://ai-mcp.insyncanalytics.com/mcp

This URL goes into every client's configuration. The /mcp path suffix is required — the base URL alone will not work.

Authentication

InSync MCP uses OAuth 2.0 (Authorization Code flow) via AWS Cognito.

  • You do not need to generate or copy API keys.
  • New accounts receive temporary credentials by email from no-reply@insyncanalytics.com. These expire after 14 days use them to log in and set a permanent password before connecting an MCP client.
  • On first use, your client will redirect you to the InSync login page in your browser.
  • Complete login once; your session token is stored by the client and refreshes automatically.
  • Tokens are encrypted at rest. Your InSync password is never stored by the MCP client.

How It Works

Client Config Style Notes Plan Requirement
Claude Desktop JSON config file Most straightforward setup Free tier supported
Claude Code CLI CLI command (claude mcp add) Best for developers Free tier supported
ChatGPT Settings → Apps UI Requires Developer Mode Plus, Pro, Business, or Enterprise
Cursor Settings UI or ~/.cursor/mcp.json Built-in MCP support Free tier supported
VS Code .vscode/mcp.json Requires VS Code v1.99+ Free tier supported
Gemini CLI ~/.gemini/settings.json Uses httpUrl key (Gemini-specific) Google account required
Proprietary / M2M Client credentials (no browser login) Server-to-server, contact inquiries@insyncanalytics.com Higher rate limits (180/min, 1800/hr)

What to Expect at First Authentication

  • You make your first financial data request.
  • Your client detects that authentication is needed and opens a browser window.
  • You are redirected to the InSync login page (auth.insyncanalytics.com).
  • Log in with your InSync credentials.
  • You are redirected back. The OAuth token is stored automatically.
  • Your original request completes.

Subsequent requests do not require re-authentication. Tokens refresh silently in the background.