Warm

Warm runs locally from a Node.js package published to the npm registry: @warmio/mcp version 7.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @warmio/mcp@7.0.1. It reads these environment variables: WARM_CONTEXT_API_KEY (secret), WARM_CONTEXT_API_KEY_FILE, WARM_AUTOMATION_API_KEY (secret), WARM_AUTOMATION_API_KEY_FILE, WARM_CONFIG_DIR, WARM_API_URL and WARM_API_TIMEOUT_MS; set them in the client's configuration for this server. Required arguments: mode.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "warmio": {
      "command": "npx",
      "args": [
        "-y",
        "@warmio/mcp@7.0.1"
      ],
      "env": {
        "WARM_CONTEXT_API_KEY": "<secret>",
        "WARM_CONTEXT_API_KEY_FILE": "<value>",
        "WARM_AUTOMATION_API_KEY": "<secret>",
        "WARM_AUTOMATION_API_KEY_FILE": "<value>",
        "WARM_CONFIG_DIR": "<value>",
        "WARM_API_URL": "<value>",
        "WARM_API_TIMEOUT_MS": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect