home / mcp / waferlock robot mcp server

Waferlock Robot MCP Server

Provides a bridge to Waferlock's public MCP REST API enabling local or remote MCP clients to access model-powered conversations.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "jasonlcs-waferlock-robot-mcp-public": {
      "url": "https://waferlock-robot-mcp-1177c207c107.herokuapp.com",
      "headers": {
        "API_URL": "https://waferlock-robot-mcp-1177c207c107.herokuapp.com",
        "API_TOKEN": "YOUR_API_TOKEN",
        "MCP_TOKEN": "YOUR_MCP_TOKEN"
      }
    }
  }
}

This MCP server acts as a bridge between the Waferlock public MCP REST API and clients that implement the Model Context Protocol (MCP). You can run a local stdio MCP server or connect through the remote API to enable model-powered conversations in your apps or desktop clients without exposing cloud credentials.

How to use

You connect your MCP client to one or more endpoints exposed by this server. A local stdio server runs on your machine and talks to the Waferlock public MCP API, while a remote HTTP method lets you reach the same service over the internet. Start the STDIO server locally to enable MCP-capable clients to send requests through your own host.

How to install

Prerequisites: Node.js 18+ (the project uses native fetch). You will need npm and npx for installation and execution.

# 1. Clone the project
git clone https://github.com/jasonlcs/waferlock-robot-mcp-public.git
cd waferlock-robot-mcp-public

# 2. Install dependencies and build
npm install
npm run build

# 3. Start the local stdio server (example with placeholders for tokens)
node dist/cli.js \
  --api-url https://waferlock-robot-mcp-1177c207c107.herokuapp.com \
  --api-token <你的 API Token> \
  --mcp-token <選填：要求 MCP 客戶端提供的 Token>

Additional configuration and usage notes

This server supports both a remote HTTP MCP endpoint and a local stdio command. The HTTP method points to the Waferlock public API URL, while the stdio method runs a local process that exposes an MCP server via standard input/output.

{
  "mcpServers": {
    "waferlock_robot_http": {
      "type": "http",
      "name": "waferlock_robot_http",
      "url": "https://waferlock-robot-mcp-1177c207c107.herokuapp.com",
      "args": []
    },
    "waferlock_robot_stdio": {
      "type": "stdio",
      "name": "waferlock_robot_stdio",
      "command": "node",
      "args": [
        "dist/cli.js",
        "--api-url", "https://waferlock-robot-mcp-1177c207c107.herokuapp.com",
        "--api-token", "<你的 API Token>",
        "--mcp-token", "<選填>"
      ]
    }
  }
}

Environment and start behavior

You can pass values through command line arguments or rely on environment variables if you omit them on the command line. Available environment variables (if you prefer) include API_URL, API_TOKEN, and MCP_TOKEN. The stdio server will start with the provided command and arguments, and you can adjust server naming or version by supplying the relevant flags.