Skip to main content
The Vortex IQ MCP connector gives Claude, and any other Model Context Protocol client, read-only access to your Vortex IQ workspace. Once connected, you can ask about your store’s health scores, KPI trends, active alerts, brand voice guidelines, health-fix backlog and more, in plain English, without opening the dashboard. Every tool is read-only: the connector cannot create, edit, delete, publish or send anything. Each call runs as the signed-in user, so the data returned is always scoped to your own organisation and your role’s permissions.

​
At a glance

Connect to Claude

Add the connector in Claude web, desktop or Claude Code in under two minutes.

Tool reference

All 29 read-only tools with parameters and example prompts, grouped by area.

OAuth for developers

The full OAuth 2.1 + PKCE flow for connecting any custom MCP client or agent.

​
What you can ask

Once connected, Claude picks the right tools automatically. Some starting points:

​
How it works

The connector is a native MCP server co-located with the Vortex IQ OAuth authorization server at app.vortexiq.ai, there is no separate proxy. When you add it, Claude walks you through a standard OAuth sign-in with your existing Vortex IQ (Google) login. Your access token is forwarded on every tool call, so every result reflects exactly what your account can already see in the dashboard.
All 29 tools carry the MCP readOnlyHint. The connector has no write, delete, publish or send capability of any kind, it cannot modify your workspace, your stores or your data. The access token is read-only too: it only works through these tools and cannot be used against any other Vortex IQ API.

​
Other AI assistants

The same server works with any MCP client that supports OAuth. For Meta AI, see Vortex IQ connector for Meta AI.

​
Disconnecting

You can disconnect an AI assistant at any time from Connected apps at app.vortexiq.ai/oauth/mcp/connections. It stops working straight away. Removing the connector inside the assistant also works.

​
Known limitations

  • Read-only. The connector cannot create, edit, delete, publish or send anything.
  • Per-user scope. Each call runs as the connecting user against their own organisation’s data, there is no shared or service account.
  • Response caps. Some list results are capped (first 50 items / roughly 40k characters) to stay model-friendly. Ask for a specific id to drill into full detail.
  • Rate limit. Up to 120 requests a minute per user. Above that the server answers 429 with a Retry-After header.

​
Support