
Crewhu
io.github.WYRE-AIPublished by GitHub account WYRE-AIv2.0.5Updated Oct 24, 2026
MCP server for Crewhu — customer feedback (CSAT/NPS), employee engagement, and gamification.
Overview
Connects an AI assistant to Crewhu to manage customer satisfaction surveys, prize catalogs and redemptions, and user engagement data.
- What you can do
- Create and manage customer satisfaction surveys (CSAT/NPS). Manage the prize catalog and prize redemptions. Look up users and their engagement and gamification data. Work with badges and other engagement features of the Crewhu platform.
- When to use it
- Useful for MSPs or teams already on Crewhu who want an assistant to draft and maintain feedback surveys, handle prize and redemption records, or review user engagement without switching to the Crewhu web app.
- Requirements
- Runs locally over stdio, typically via npx or the published container image. Needs a Crewhu API token in CREWHU_API_TOKEN for stdio or env auth mode. HTTP mode additionally requires CONDUIT_S2S_SECRET and, in gateway mode, an X-Crewhu-Api-Token header per request. Node.js for the npm package.
Installation
In SourceWeft
- Open Crewhu in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Crewhu MCP Server
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
Configuration
Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.
/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:
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.
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:
Running with Claude Code (CLI)
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.
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:
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses CREWHU_API_TOKEN:
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:
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
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.
Source: README.md at commit 6584251
Tools
0Version history
2- v2.0.5LatestOct 14, 2026
- v2.0.4Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts