CommoVision

See the future in real time

Connect your tools

The REST API and the MCP server answer with the same key. Create the key in the portal under Account & settings, then pick the way in that fits your stack.

AI tools over MCP

The MCP server at api.commovision.com/mcp answers AI tools with the same data the API serves. A tool that accepts a key takes the server as one configuration entry. The tools below are listed alphabetically. Where we have connected one ourselves, its entry says so. Every other entry states what its publisher documents.

ChatGPT

Not yet. ChatGPT's custom connectors accept signing in or no authentication, and refuse a key sent in a header or a URL, so our key cannot be used there. Signing in is on our roadmap.

Claude Code

claude mcp add --transport http commovision \
  https://api.commovision.com/mcp \
  --header "Authorization: Bearer cvk_your_key_here"

claude mcp list then shows the server and whether it connected.

Tested by us: 2026-10-13, CommoVision, connected over the public edge and called the freshness tool.

Claude Desktop and claude.ai

Customize > Connectors > Add > Add custom connector. Give it a name, enter https://api.commovision.com/mcp as the server URL, and put Authorization: Bearer cvk_your_key_here in the Request headers field, which is where a fixed credential goes for a server that does not ask you to sign in. Claude connects from its own cloud rather than from your machine.

Shape from the publisher's documentation; not tested by us yet.

Codex CLI

Config file: ~/.codex/config.toml

[mcp_servers.commovision]
url = "https://api.commovision.com/mcp"
bearer_token_env_var = "COMMOVISION_API_KEY"

Set COMMOVISION_API_KEY in the environment Codex runs in. The config file holds the variable's name, never the key itself. Then codex mcp list shows the server.

Shape from the publisher's documentation; not tested by us yet.

Cursor

Config file: ~/.cursor/mcp.json (or .cursor/mcp.json in one project)

{
  "mcpServers": {
    "commovision": {
      "url": "https://api.commovision.com/mcp",
      "headers": {
        "Authorization": "Bearer cvk_your_key_here"
      }
    }
  }
}

To keep the key out of the file, set it in your environment and write "Bearer ${env:COMMOVISION_API_KEY}" as the header value.

Shape from the publisher's documentation; not tested by us yet.

Gemini CLI

Config file: ~/.gemini/settings.json (user scope)

gemini mcp add --transport http commovision \
  https://api.commovision.com/mcp \
  --header "Authorization: Bearer cvk_your_key_here" -s user
{
  "mcpServers": {
    "commovision": {
      "httpUrl": "https://api.commovision.com/mcp",
      "headers": {
        "Authorization": "Bearer cvk_your_key_here"
      }
    }
  }
}

httpUrl is the streamable-HTTP key. url there means an SSE endpoint, which this server does not serve.

Shape from the publisher's documentation; not tested by us yet.

VS Code

VS Code's own MCP documentation does not document a header field for a remote server, and advises against putting a key in the file, so we publish no VS Code config until one is sourced from its documentation and tested.

From code

The REST API is plain HTTPS with your key in an Authorization header, and requests answer JSON or CSV. The Python package installs with pip: pip install commovision. The developer reference at api.commovision.com/docs covers both.

Spreadsheets, BI and the warehouse

Routes that take a format parameter answer CSV as well as JSON. For a warehouse, bulk extracts download whole tables as Parquet or CSV by signed URL, and the change feed keeps a mirror current from a cursor; both come with the paid API plans.

A free trial includes the whole portal, and API and MCP access on request.

Start a free trial