Crewhu

io.github.wyre-technology由 GitHub 帳號 wyre-technology 發布v2.0.3更新於 Oct 24, 2026

MCP server for Crewhu — customer feedback (CSAT/NPS), employee engagement, and gamification.

已驗證STDIO僅桌面效率與工作流商業與電商

概覽

AI 產生的概覽

將 AI 助理連接到 Crewhu,用來管理客戶滿意度調查、獎品以及使用者參與度資料。

可以做什麼
此 MCP 伺服器會把相容 MCP 的助理連接到 Crewhu 帳號,該平台用於客戶回饋(CSAT/NPS)、員工參與度與遊戲化。根據 README,它可讓助理建立與管理客戶滿意度調查、管理獎品目錄與兌換,並處理使用者管理與參與度資料。它透過 stdio 在本機執行,託管於閘道後方時也可透過 HTTP 執行。
適用情境
當你已在使用 Crewhu,並希望助理協助設定調查、管理獎品與兌換,或檢視使用者參與度資料而不必切換到 Crewhu 網頁介面時,值得加入。它鎖定託管服務供應商與經營客戶回饋方案的團隊。
執行需求
需要能執行該 npm 套件或容器映像的本機執行環境,以及透過 CREWHU_API_TOKEN 提供的 Crewhu API 權杖(在 Crewhu 的 Settings、Integrations、API 中取得)。選用設定包括 AUTH_MODE、MCP_TRANSPORT 與 LOG_LEVEL。需要連線到 Crewhu 的網路。
安裝前請注意
此伺服器需要 Crewhu API 權杖(CREWHU_API_TOKEN),這是可存取你 Crewhu 帳號的憑證,應存放在環境變數中而非共用設定檔。所描述的工具包括建立與管理調查以及管理獎品兌換,因此助理的動作可能會變更或刪除 Crewhu 環境中的資料。在正式帳號上啟用前,請確認允許助理執行哪些動作。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Crewhu,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Crewhu MCP Server

[License] [Node.js]

A Model Context Protocol (MCP) server for Crewhu — customer feedback, employee engagement, and gamification platform. Enables AI assistants to manage surveys, badges, prizes, and user engagement data.

This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Crewhu environment.

Part of the MSP Claude Plugins ecosystem — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs.

Installation

bash
npm install @wyre-ai/crewhu-mcp

Configuration

Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.

VariableRequiredDescription
CREWHU_API_TOKENFor stdio and AUTH_MODE=envCrewhu API token. Not read in gateway mode.
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENogateway (Docker image and Compose default) or env. Gateway mode requires X-Crewhu-Api-Token on each /mcp request and never falls back to CREWHU_API_TOKEN. env uses that variable only after S2S auth succeeds.
CONDUIT_S2S_SECRETYes for HTTPService-to-service HMAC secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, replace-with-a-real-secret, and similar). Compose will not start without it. Generate with openssl rand -hex 32. Never commit a real value. The value is never logged.
MCP_ALLOW_INSECURE_DEVNoSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning and does not enforce X-Gateway-S2S. The listener is forced to 127.0.0.1 even if MCP_HTTP_HOST is a wider address. A placeholder secret is still refused.
MCP_HTTP_HOSTNoBind address when MCP_TRANSPORT=http. Defaults to 127.0.0.1. Honored when CONDUIT_S2S_SECRET is set. The container image sets 0.0.0.0.
MCP_HTTP_PORTNoHTTP port. Defaults to 8080.

/health stays unauthenticated and does not require X-Gateway-S2S. The stdio transport does not use CONDUIT_S2S_SECRET.

HTTP authentication

With MCP_TRANSPORT=http and a real CONDUIT_S2S_SECRET, every /mcp request must include X-Gateway-S2S. A missing or invalid header returns 401 before any vendor credential is read.

The header is an HMAC proof:

text
X-Gateway-S2S: t=<unix seconds>,v1=<hex hmac-sha256>

v1 is the hex-encoded HMAC-SHA256 of the ASCII string t=<unix seconds> (the same t= prefix and value), keyed with CONDUIT_S2S_SECRET. The timestamp must be within 300 seconds of the server clock.

bash
t=$(date +%s)sig=$(printf 't=%s' "$t" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}')curl -sS "http://127.0.0.1:8080/mcp" \  -H "X-Gateway-S2S: t=${t},v1=${sig}" \  -H "X-Crewhu-Api-Token: $CREWHU_API_TOKEN" \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

In AUTH_MODE=gateway, /mcp also requires X-Crewhu-Api-Token. A missing or blank header returns 401 and does not fall back to CREWHU_API_TOKEN.

Usage

Running with Claude Desktop

Add to your Claude Desktop claude_desktop_config.json:

json
{  "mcpServers": {    "crewhu-mcp": {      "command": "npx",      "args": ["@wyre-ai/crewhu-mcp"],      "env": {        "CREWHU_API_TOKEN": "your-crewhu-api-token"      }    }  }}

Running with Claude Code (CLI)

bash
claude mcp add crewhu-mcp \  -e CREWHU_API_TOKEN=your-value \  -- npx -y @wyre-ai/crewhu-mcp

Docker

The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass a real S2S secret. In gateway mode, the Crewhu token arrives on each request as X-Crewhu-Api-Token; it is not read from the environment. Startup exits if CONDUIT_S2S_SECRET is empty or a known placeholder.

bash
docker build -t crewhu-mcp .docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  crewhu-mcp

Compose refuses to start when CONDUIT_S2S_SECRET is unset, defaults AUTH_MODE to gateway, publishes 127.0.0.1:8080:8080, and does not set CREWHU_API_TOKEN:

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses CREWHU_API_TOKEN:

bash
docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=env \  -e CREWHU_API_TOKEN=your-value \  -p 127.0.0.1:8080:8080 \  crewhu-mcp

Local HTTP without a secret is development-only. It binds 127.0.0.1 only and logs a warning. A non-loopback MCP_HTTP_HOST is ignored:

bash
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start

Available Domains

Badges

Manage and award employee badges

Prizes

Manage prize catalog and redemptions

Surveys

Create and manage customer satisfaction surveys

Users

User management and engagement data

Development

bash
# Clone the repositorygit clone https://github.com/WYRE-AI/crewhu-mcp.gitcd crewhu-mcp
# Install dependenciesnpm install
# Buildnpm run build
# Run testsnpm test

Contributing

Contributions are welcome! Please see CONTRIBUTING.md if present, or open an issue to discuss changes.

License

Licensed under the Apache License, Version 2.0. See LICENSE for details.

來源:README.md,提交 6584251

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v2.0.3最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分