Build

MCP setup

Expose Coldvio's customer-safe tools to Claude, Codex, Copilot, and other stdio-compatible agents.

How the connection works

Your agent starts npx -y @coldvio/[email protected] mcp as a local stdio server. The server calls the dedicated Coldvio agent API over HTTPS and returns only data owned by the signed-in customer. The MCP client never needs your Coldvio password.

Local stdio is the supported first release. A remote Streamable HTTP MCP endpoint is future work for browser-only and hosted agent products.

Claude Code

User scope keeps the command in your own configuration. If a team shares a project-level MCP command, the credential must still remain outside the repository.

bash

claude mcp add --transport stdio --scope user coldvio -- npx -y @coldvio/[email protected] mcp
claude mcp list

Codex CLI and IDE extension

Codex shares MCP configuration between its CLI and IDE extension. A project config may contain the command, but never COLDVIO_API_TOKEN.

bash

codex mcp add coldvio -- npx -y @coldvio/[email protected] mcp
codex mcp list

VS Code and GitHub Copilot agent mode

Add this as a user setting or .vscode/mcp.json. VS Code asks you to trust a local server the first time.

json

{
  "servers": {
    "coldvio": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@coldvio/[email protected]", "mcp"]
    }
  }
}

GitHub Copilot CLI

This writes the user configuration at ~/.copilot/mcp-config.json. Copilot's hosted coding agent is not supported in v0.1 because Coldvio has not yet shipped an audited credential-provisioning flow; never scrape or upload credentials.json.

bash

copilot mcp add coldvio -- npx -y @coldvio/[email protected] mcp
copilot mcp list

Cursor, Windsurf, Gemini CLI, and other clients

Field names vary by client. The stable contract is a stdio process started with npx -y @coldvio/[email protected] mcp, with stdin and stdout kept open.

json

{
  "mcpServers": {
    "coldvio": {
      "command": "npx",
      "args": ["-y", "@coldvio/[email protected]", "mcp"]
    }
  }
}

Safe agent behavior

Read-only tools may be called without additional confirmation.
CRM updates, generation, approval, and rejection require trusted confirmation shown by the MCP host; model-supplied booleans are not accepted.
If the host lacks elicitation support, the operation fails closed and points the customer to the CLI.
Draft-generation tools do not send or publish content.
Prefer narrow searches and low result limits when customer or lead data is involved.