Vortex Iq

What the vortex-iq MCP server does

The vortex-iq MCP server exposes read-only access to data in a user's VortexIQ workspace. VortexIQ is described as an AI operating system for ecommerce, and the connector lets an MCP-compatible client retrieve operational information through conversation. It does not provide mutation tools: agents cannot create, edit, delete, publish, or send records or actions.

Available data spans store audit runs and reports, Nerve Centre alerts and activity, KPI definitions and integration metrics, dashboard information, Brand DNA profiles and ecommerce stores, Ask VIQ conversation records, Kanban health-fix work, reports and schedules, CloudHub inventory tabs, Vortex memory files and reports, and deployment history.

How it works

The connector is a remote MCP server at https://app.vortexiq.ai/mcp and uses Streamable HTTP transport. Authentication uses per-user OAuth 2.1 with the Authorization Code flow and PKCE using S256. OAuth discovery endpoints are available at:

• https://app.vortexiq.ai/.well-known/oauth-authorization-server
• https://app.vortexiq.ai/.well-known/oauth-protected-resource

After authorization, each request runs as the signed-in user against that user's organization. Returned data is also constrained by the user's role permissions. The vortex-iq MCP server therefore uses the user's existing VortexIQ access rather than a shared account.

Setup and configuration

A VortexIQ account is required. In Claude web or desktop, open Settings → Connectors → Add custom connector, enter the server URL, sign in with the existing VortexIQ Google login, and approve access. The tools then become available in Claude.

Other OAuth-capable MCP clients can use the documented registration, authorization, token, and refresh flow. The repository points to MCP_OAUTH_LIVE_USAGE.md for that process and provides machine-discoverable OAuth metadata. No server environment variables are specified for client-side setup.

Tools and capabilities

The connector provides 30 read-only tools grouped into these areas:

• Store Audit: list runs, retrieve reports, and check audit status.
• Nerve Centre and KPIs: inspect alerts, summaries, activity, KPI libraries, integration metrics, profiles, configurations, connectors, monitors, dashboard activity, and stores.
• Brand DNA: retrieve brand profiles and associated ecommerce stores.
• Ask VIQ: list and retrieve conversations.
• Kanban: inspect the health-fix board, items, and item status.
• Reports and Insights: list insight reports, report profiles, and schedules.
• Inventory and Memory: list CloudHub inventory tabs, Vortex memory files, and memory reports.
• Deployments: retrieve deployment history.

Typical requests include listing recent audits and drilling into a report, checking 30-day integration KPIs, reviewing active alerts and a 24-hour incident summary, viewing brand voice guidelines, or inspecting the health-fix backlog.

Limitations and notes

The vortex-iq MCP server is strictly read-only. It has no tools for writing, deleting, publishing, or sending data. Results are scoped to the connecting user's organization and permissions, so it cannot provide a shared or cross-organization account view.

Some list responses are capped at the first 50 items or approximately 40,000 characters. When a result is capped, requesting a specific identifier can provide a more focused drill-down. Support documentation is available at https://docs.vortexiq.ai/, with support at support@vortexiq.ai.