Heybeauty MCP Server

HeyBeauty Virtual TryOn

Local serverstdioTypeScript

What is the Heybeauty MCP MCP server?

If you want an AI assistant working directly with Heybeauty MCP, the heybeauty mcp mcp server is the bridge. HeyBeauty Virtual TryOn.

What Heybeauty MCP does

This is a TypeScript-based MCP server that implements virtual tryon using HeyBeauty API. It demonstrates core MCP concepts by providing:

Tools it exposes

Once connected, the assistant can call these 6 tools directly:

  • submit_tryon_task — Submit a tryon task
  • query_tryon_task — Query a tryon task
  • Resources — The Resources tool exposed by this server
  • Tools — The Tools tool exposed by this server
  • Prompts — The Prompts tool exposed by this server
  • Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Installing the heybeauty mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: HEYBEAUTY_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. Heybeauty MCP sits in that group, and the shape of its toolset — submit_tryon_task, query_tryon_task, Resources among others — tells you what it is really for. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by chatmcp, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the heybeauty mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
submit_tryon_taskSubmit a tryon task
query_tryon_taskQuery a tryon task
ResourcesThe Resources tool exposed by this server.
ToolsThe Tools tool exposed by this server.
PromptsThe Prompts tool exposed by this server.
DebuggingSince MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

How to install the Heybeauty MCP MCP server

{
  "mcpServers": {
    "heybeauty-mcp": {
      "command": "npx",
      "args": ["-y", "heybeauty-mcp"],
      "env": {
        "HEYBEAUTY_API_KEY": "your_heybeauty_api_key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
HEYBEAUTY_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Heybeauty MCP to submit tryon task.
  • Use Heybeauty MCP to query tryon task.
  • Use Heybeauty MCP to Resources.

Frequently asked questions

It connects Heybeauty MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (submit_tryon_task, query_tryon_task, Resources, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Heybeauty MCP directly.