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 分