three.ws Concierge MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add concierge-mcp -- npx -y @three-ws/concierge-mcp

{
  "mcpServers": {
    "concierge-mcp": {
      "args": [
        "-y",
        "@three-ws/concierge-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.concierge-mcp]
command = "npx"
args = ["-y", "@three-ws/concierge-mcp"]

{
  "mcpServers": {
    "concierge-mcp": {
      "args": [
        "-y",
        "@three-ws/concierge-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "concierge-mcp": {
      "args": [
        "-y",
        "@three-ws/concierge-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: THREE_WS_BASE (Base URL of the three.ws API that serves POST /api/concierge, and the origin the generated embed snippets point at. Override only when self-hosting or targeting a preview deployment.), THREE_WS_TIMEOUT_MS (Per-request timeout in milliseconds for the concierge answer call. The answer streams over a free-first LLM chain that can fail over across providers, so the default leaves room for one slow rung.), CONCIERGE_PAGE_TIMEOUT_MS (Timeout in milliseconds for fetching a page that concierge_ask grounds its answer in. Separate from the answer timeout so a slow site cannot consume the whole call.). The author declared them in the registry entry; get the values from the project itself.