MCP and automation

How to connect Vexday to Claude, ChatGPT and other AI assistants (MCP)

Ask your AI assistant whether a CVE has a public exploit or affects a client and get the answer with Vexday's data and the source of each item. The steps work for Claude, ChatGPT, Cursor, VS Code, n8n and other apps.

  • Who it's forFor SOCs, MSSPs and anyone who uses AI in day-to-day security work.
  • PlanSOC and MSSP plans
  • Timeabout 5 min

What you need

  • A Vexday account on the SOC or MSSP plan.
  • An MCP-compatible assistant or editor, such as Claude, ChatGPT, Cursor or VS Code.

Calls per day on the plans with the MCP: SOC, 5,000 · MSSP, 20,000.

Step by step

  1. Choose how to sign in

    Through the connector, no key: the app opens the Vexday screen, you sign in with email or Google and click Allow. Or with the API key, in apps that accept a header. In the list below, each app says which of the two it supports.

  2. Create the key, if you use one

    In the dashboard, open Integrations and click New key. Copy the key right away: it starts with vx_live_ and is shown only once. If you use the connector, skip this step.

  3. Add the server to the app

    The server address is https://api.vexday.io/mcp. Open your app in the list below and follow its steps, with the config file where there is one.

  4. Ask the first question

    Ask, for example: "Does CVE-2024-3400 have a public exploit? Does it affect any technology I monitor?". The assistant queries Vexday and answers with the source of each item.

  5. Track usage and disconnect any time

    Each tool call counts as one request against the account limit, the same as the API's. The connector shows up under Integrations as the key "Conector: app name": to disconnect, revoke the key.

Each app, step by step

Chat assistants

Claude.ai e Claude DesktopConnector, no key

The Free plan allows one custom connector. On Team and Enterprise, the organization owner adds it (Organization settings → Connectors) and each member clicks Connect. Claude Desktop uses the same account connectors.

  1. In Customize → Connectors, click + Add → Add custom connector.
  2. Name it Vexday and paste the address https://api.vexday.io/mcp.
  3. For authentication, choose to sign in now and leave the OAuth client on automatic registration (no advanced settings).
  4. Sign in with your Vexday account and authorize.
  5. In a chat, turn Vexday on under + → Connectors.

Official docs ↗

ChatGPTConnector, no key

ChatGPT only connects by signing in: it doesn't send API keys. Custom MCP servers are on the Business and Enterprise plans (on Business, admins create them) and, on Pro, in developer mode. In older versions, the path is Settings → Apps & Connectors → Advanced settings → Developer mode → Create.

  1. Open chatgpt.com/plugins and click + → Add custom MCP server.
  2. Name it Vexday and paste https://api.vexday.io/mcp in Server URL.
  3. Under Authentication, choose OAuth and leave the client fields empty.
  4. Accept the warning, click Create as a plugin, review the tools and sign in with your Vexday account.
  5. In a chat, type @ and pick Vexday.

Official docs ↗

Microsoft Copilot StudioConnector or key

The agent needs generative orchestration on. After connecting, check the tool list.

  1. In the agent, open Tools → Add a tool → New tool → Model Context Protocol.
  2. Fill in the name, the description (the agent uses it to decide when to call Vexday) and the Server URL https://api.vexday.io/mcp.
  3. To sign in: OAuth 2.0, type Dynamic discovery. For the key: API key, type Header, named Authorization.
  4. Under Add tool, create the connection: to sign in, log in with your Vexday account; with the key, paste Bearer vx_live_SUA_CHAVE (with Bearer in front).
  5. Click Add to agent.

Official docs ↗

Le Chat (Mistral Vibe)Connector, no key

Le Chat is now called Vibe; the chat.mistral.ai address is the same. Only the account admin adds connectors.

  1. Open Connectors (under Context in the menu) and click + Add Connector → Custom MCP Connector.
  2. Name: vexday (no spaces); Server URL: https://api.vexday.io/mcp.
  3. Click Connect and sign in with your Vexday account.
  4. In My Connectors, open Vexday and set its functions to Always allow so you don't confirm each lookup.

Official docs ↗

5ireAPI key

5ire has no sign-in (OAuth): it connects with the API key.

  1. Create an API key in the Vexday dashboard, under Integrations.
  2. In Tools, open the arrow on the + Local button and choose Remote.
  3. Name Vexday, URL https://api.vexday.io/mcp and, under Http Headers, Name Authorization and Value Bearer vx_live_SUA_CHAVE.
  4. Save and turn Vexday on.

Official docs ↗

Code editors and terminals

Claude CodeConnector or key
  1. Create an API key in the Vexday dashboard, under Integrations.
  2. In the terminal, run the command below (with --scope user, it applies to all your projects).
  3. Check with claude mcp list: vexday shows as Connected. Without --header, Claude Code offers the Vexday sign-in under /mcp.
claude mcp add --transport http --scope user vexday https://api.vexday.io/mcp \
  --header "Authorization: Bearer vx_live_SUA_CHAVE"

Official docs ↗

CursorConnector or key
  1. Create an API key in the Vexday dashboard, under Integrations.
  2. Put the key in the VEXDAY_API_KEY environment variable (in the terminal: export VEXDAY_API_KEY=vx_live_…) and start the app from that terminal.
  3. Paste the block below into the file and check in Cursor's MCP settings that vexday is on. Without headers, Cursor opens the Vexday sign-in.

File: ~/.cursor/mcp.json (or .cursor/mcp.json in the project)

{
  "mcpServers": {
    "vexday": {
      "url": "https://api.vexday.io/mcp",
      "headers": { "Authorization": "Bearer ${env:VEXDAY_API_KEY}" }
    }
  }
}

Official docs ↗

VS Code com GitHub CopilotConnector or key

This is the new format, shared with the GitHub Copilot CLI. The old format (.vscode/mcp.json, with "servers" instead of "mcpServers" and ${env:VEXDAY_API_KEY}) still works.

  1. Create an API key in the Vexday dashboard, under Integrations.
  2. Put the key in the VEXDAY_API_KEY environment variable (in the terminal: export VEXDAY_API_KEY=vx_live_…) and start the app from that terminal.
  3. Paste the block below into the file. In MCP: List Servers, pick vexday to see its status and output. Without headers, VS Code opens the Vexday sign-in.

File: ~/.copilot/mcp-config.json (or .mcp.json at the project root)

{
  "mcpServers": {
    "vexday": {
      "type": "http",
      "url": "https://api.vexday.io/mcp",
      "headers": { "Authorization": "Bearer ${VEXDAY_API_KEY}" },
      "tools": ["*"]
    }
  }
}

Official docs ↗

Windsurf (Devin Desktop)Connector or key

Windsurf was renamed Devin Desktop in June 2026. In versions with the old name, the file is ~/.codeium/windsurf/mcp_config.json and the address goes in "serverUrl".

  1. Create an API key in the Vexday dashboard, under Integrations.
  2. Paste the block below into the file. In the project's .local.json, the key stays out of git.
  3. In Customize → MCPs, refresh and check that vexday is on. Without headers, it asks for the Vexday sign-in (Authenticate).

File: .devin/mcp_config.local.json in the project (or ~/.config/devin/mcp_config.json)

{
  "mcpServers": {
    "vexday": {
      "url": "https://api.vexday.io/mcp",
      "headers": { "Authorization": "Bearer vx_live_SUA_CHAVE" }
    }
  }
}

Official docs ↗

ZedConnector or key

In Zed, prefer signing in: it doesn't read environment variables in headers. If you use the key, add "headers": { "Authorization": "Bearer vx_live_SUA_CHAVE" } only in your user settings, never in the project's .zed/settings.json.

  1. Paste the block below into your user settings (or use Settings → AI → MCP Servers → Add Server → Add Remote Server).
  2. Click Authenticate and sign in with your Vexday account.
  3. In Settings → AI → MCP Servers, the vexday dot turns green.

File: ~/.config/zed/settings.json (on Windows, %APPDATA%\Zed\settings.json)

{
  "context_servers": {
    "vexday": {
      "url": "https://api.vexday.io/mcp"
    }
  }
}

Official docs ↗

OpenCodeConnector or key
  1. Create an API key in the Vexday dashboard, under Integrations.
  2. Put the key in the VEXDAY_API_KEY environment variable (in the terminal: export VEXDAY_API_KEY=vx_live_…) and start the app from that terminal.
  3. Paste the block below into the file and check with opencode mcp list (or opencode mcp debug vexday). To sign in instead, remove "oauth" and "headers" and run opencode mcp auth vexday.

File: ~/.config/opencode/opencode.json (or opencode.json in the project)

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vexday": {
      "type": "remote",
      "url": "https://api.vexday.io/mcp",
      "oauth": false,
      "headers": { "Authorization": "Bearer {env:VEXDAY_API_KEY}" }
    }
  }
}

Official docs ↗

Other CLIs and automation

Gemini CLIConnector or key

In older Gemini CLI versions, replace "url" and "type" with "httpUrl": "https://api.vexday.io/mcp".

  1. Create an API key in the Vexday dashboard, under Integrations.
  2. Put the key in the VEXDAY_API_KEY environment variable (in the terminal: export VEXDAY_API_KEY=vx_live_…) and start the app from that terminal.
  3. Paste the block below into the file and check with gemini mcp list (Connected) or /mcp in a chat. To sign in with your Vexday account instead of the key, remove "headers" and run /mcp auth vexday in a chat.

File: ~/.gemini/settings.json (or .gemini/settings.json in the project)

{
  "mcpServers": {
    "vexday": {
      "url": "https://api.vexday.io/mcp",
      "type": "http",
      "headers": { "Authorization": "Bearer ${VEXDAY_API_KEY}" }
    }
  }
}

Official docs ↗

Codex CLI (OpenAI)Connector or key

The same config applies to the Codex extension in your editor.

  1. Create an API key in the Vexday dashboard, under Integrations.
  2. Put the key in the VEXDAY_API_KEY environment variable (in the terminal: export VEXDAY_API_KEY=vx_live_…) and start the app from that terminal.
  3. Paste the block below into the file and check with codex mcp list or /mcp. Without the key line, codex mcp login vexday opens the Vexday sign-in.

File: ~/.codex/config.toml

[mcp_servers.vexday]
url = "https://api.vexday.io/mcp"
bearer_token_env_var = "VEXDAY_API_KEY"

Official docs ↗

n8nConnector or key

Needs n8n 1.104 or newer (HTTP Streamable). To sign in instead, use Authentication: MCP OAuth2.

  1. Create an API key in the Vexday dashboard, under Integrations.
  2. In the AI Agent node, under Tool, add the MCP Client Tool.
  3. Endpoint: https://api.vexday.io/mcp; Server Transport: HTTP Streamable.
  4. Authentication: Bearer Auth, with a new credential. In Bearer Token, paste just the key (vx_live_…), without Bearer: n8n adds it.
  5. In Tools to Include, choose Selected: if the Vexday tools show up in the list, the connection works.

Official docs ↗

Something went wrong?

The app says the key is invalid (401)The key was revoked or pasted with a space. Create another one under Integrations and paste it again. In n8n, paste just the key: it adds the Bearer itself.
It says the plan does not include the MCP (403)The MCP is part of the SOC and MSSP plans. Check the account's plan under Account and plan.
Too many requests per minuteThe assistant called many tools in a row. Wait a minute: the per-minute limit resets on its own.
The connector does not open the sign-in screenCheck that the address ends in /mcp and that the app is set to sign-in (OAuth) mode, not key mode.

Frequently asked questions

Do I need to install anything?

No. The server runs at Vexday: you only add the address to the app.

Does it work with an app that is not on the list?

Yes, with any MCP client that uses HTTP: add the address and send the key in the Authorization header.

What can the assistant see in my account?

The monitored stack, the alerts and the exposure of the connected account, read-only. No tool changes the account.

Keep going