integrity MCP配置与使用教程
com.bluecat/integritymcp · v26.1.0
BlueCat Integrity MCP Server (formerly bammcp)
产品介绍
BlueCat Integrity MCP Server (formerly bammcp) integritymcp 是一个MCP Server,收录自 官方 MCP Registry。支持 streamable-http 传输。本页提供产品介绍、配置教程、安装命令与适用场景,支持 Trae、通义灵码、Cursor、Claude Code、VS Code 等。
AgentHub Verified 可用性验证技术测试通过
自动化测试流水线已校验安装命令、传输协议与客户端兼容性
按平台快速复制
选择你的平台查看安装方式
- 打开项目根目录下的 .cursor/mcp.json(没有就新建)
- 点击「复制配置」粘贴进去;若已有其他 MCP,只合并 mcpServers 里的本条目
- 将 env 中的 <占位符> 替换为真实密钥(见下方「环境变量」)
- 保存后按 Cmd+Shift+P(Windows:Ctrl+Shift+P)→ 输入 Reload Window 并执行
预填环境变量与密钥(可选)
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}配置教程
- 打开 integritymcp 详情页,确认这是你需要的 MCP Server(来源 官方 MCP Registry)。
- 按客户端选择 Trae、通义灵码、Cursor、Claude Code 或 VS Code,复制 JSON 配置或 CLI 命令。
- 将配置合并进 mcpServers,并把环境变量占位符替换为真实密钥。
- 重载窗口后,在 Agent 对话中调用该 MCP 提供的工具。
安装命令
以下安装命令与配置步骤已写入页面 HTML,搜索引擎与未启用 JavaScript 的浏览器均可直接读取。
Claude Code(本地)
- 确保已安装 Claude Code CLI
- 复制下方命令,将 <占位符> 替换为真实环境变量值后,在终端执行
- 若下方列出了环境变量,请对照填写
claude mcp add integritymcp --env BAM_BASE_URL=<BAM_BASE_URL> --env MCP_AUTH_MODE=<MCP_AUTH_MODE> --env ACCEPT_EULA=<ACCEPT_EULA> -- docker run -i --rm quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0dCursor — .cursor/mcp.json(本地)
- 打开项目根目录下的 .cursor/mcp.json(没有就新建)
- 点击「复制配置」粘贴进去;若已有其他 MCP,只合并 mcpServers 里的本条目
- 将 env 中的 <占位符> 替换为真实密钥(见下方「环境变量」)
- 保存后按 Cmd+Shift+P(Windows:Ctrl+Shift+P)→ 输入 Reload Window 并执行
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}VS Code — .vscode/mcp.json(本地)
- 确保 VS Code 已安装 GitHub Copilot 扩展并支持 MCP
- 打开项目根目录下的 .vscode/mcp.json(没有就新建)
- 点击「复制配置」粘贴;若已有其他 MCP,只合并 mcpServers 里的本条目
- 将 env 中的 <占位符> 替换为真实密钥(见下方「环境变量」)
- 保存后重新加载 VS Code 窗口
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}Claude Desktop — claude_desktop_config.json(本地)
- 打开 Claude Desktop 的 claude_desktop_config.json(路径见远程指引)
- 点击「复制配置」合并到 mcpServers
- 将 env 中的 <占位符> 替换为真实密钥
- 完全退出并重启 Claude Desktop
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}Trae — .trae/mcp.json(本地)
- 打开 Trae → 设置 → MCP,或编辑 .trae/mcp.json / 全局 mcp.json
- 点击「复制配置」粘贴并合并 mcpServers
- 将 env 中的 <占位符> 替换为真实密钥
- 保存后重载 Trae 窗口
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}Cherry Studio — MCP 设置(本地)
- 打开 Cherry Studio → 设置 → MCP 服务器 → 添加(STDIO)
- 也可直接导入下方 JSON:点击「复制配置」合并到 mcpServers
- 将 env 中的 <占位符> 替换为真实密钥,并确保本机已安装 Node.js / uv(npx、uvx)
- 启用服务并查看工具列表是否加载成功
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}通义灵码 — MCP 配置(本地)
- 通义灵码:个人设置 → MCP 服务 → 「+」→ 手工添加(STDIO)或配置文件添加
- 点击「复制配置」合并 mcpServers;命令/参数/环境变量与 JSON 一致
- 将 env 中的 <占位符> 替换为真实密钥;本机需 Node.js 18+(npx)或已安装 uv(uvx)
- 确认服务状态为已连接后再在智能体对话中调用
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}Windsurf — mcp_config.json(本地)
- 编辑 ~/.codeium/windsurf/mcp_config.json
- 点击「复制配置」合并 mcpServers(本地 stdio 与 Cursor 格式相同)
- 将 env 中的 <占位符> 替换为真实密钥后保存并刷新 Cascade
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}Cline — MCP Servers(本地)
- Cline 面板 → 设置 → MCP Servers
- 点击「复制配置」粘贴并合并
- 将 env 中的 <占位符> 替换为真实密钥后保存
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}WorkBuddy — .workbuddy/mcp.json(本地)
- 编辑 ~/.workbuddy/mcp.json(用户级)或项目目录 .workbuddy/mcp.json
- 也可在界面:插件 → MCP 服务器 → 配置 MCP,粘贴下方 JSON
- 将 env 中的 <占位符> 替换为真实密钥;Windows 下 command/脚本路径建议用绝对路径
- 保存并重启 WorkBuddy,确认连接器状态为绿色
{
"mcpServers": {
"integritymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
],
"env": {
"BAM_BASE_URL": "<BAM_BASE_URL>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}常见报错排查与运行避坑 (Troubleshooting)FAQ
针对 integritymcp 在 Cursor、Claude Code 中的常见连接错误与解决办法
在 Cursor / Claude Code 中配置 integritymcp 提示 connection closed 或 exit code 1?
通常由本地运行时环境缺失或命令路径未被 IDE 继承引起。排查步骤: 1. 确认已安装 Node.js 18+(支持 npx)或 Python 3.10+(支持 uvx); 2. 尝试在终端运行 which npx 或 which uvx,把配置文件中的 "command" 字段改为完整绝对路径; 3. 修改 mcp.json 后,必须完全重载或重启客户端窗口。
# 终端测试命令是否存在: which npx node -v
提示 spawn npx ENOENT 或 command not found?
这是因为编辑器后台进程未加载完整的终端环境变量(PATH)。解决方案:在全局安装该包(如 npm install -g 包名),或在配置文件中将 command 设置为系统的实际路径(如 Windows 下的 C:\Program Files\nodejs\npx.cmd,Mac 下的 /usr/local/bin/npx)。
提示 Missing required environment variable 或 API 认证失败?
integritymcp 依赖环境变量(如 BAM_BASE_URL、MCP_AUTH_MODE、ACCEPT_EULA)。请在客户端配置文件的 "env" 对象中填入有效密钥,注意不要包含多余空格或未闭合的双引号。
// .cursor/mcp.json 或 claude_desktop_config.json
{
"env": {
"BAM_BASE_URL": "your_actual_key_here"
}
}免安装模拟调用 (Playground)
仿真环境integritymcp 核心接口调用仿真 · 无需配置本地环境,直接预览调用参数与返回格式
{
"target": "integritymcp",
"action": "execute",
"options": {
"mode": "standard",
"timeoutMs": 5000
}
}点击上方「模拟运行」按钮
查看该工具在 Agent 内部的返回数据格式
选型与决策建议(为什么选它?)
帮助你快速判断该资源是否契合当前项目,避免盲目折腾
- 需要让 AI 在此领域调用自主工具能力时
- 替代繁琐的手工重复操作,提升自动化闭环
- 配合支持 MCP / Skill 的现代 AI 编程客户端
- 没有对应环境运行权限或缺少必要 API Key 时
- 单纯需要简单对话、无需外部系统连接的场景
integritymcp + 对应场景 Prompt → 组成标准 Agent 自动化任务
MCP 实战教程:从安装到看见效果
按完整实例走一遍(含期望效果与对比验收)。装完本页资源后,用教程里的提示词核对是否真正生效。
相关资源
飞书文档
io.mcp-cn.feishu-mcp
飞书的MCP服务器,支持文档管理等功能
Figma
io.mcp-cn.figma-developer-mcp
连接Figma的MCP服务器,支持设计文件管理和操作
Puppeteer
io.mcp-cn.modelcontextprotocol/server-puppeteer
基于Puppeteer的网页自动化和数据抓取MCP工具
顺序思考
io.mcp-cn.modelcontextprotocol/server-sequential-thinking
帮助AI进行结构化思考和推理的MCP工具
Context7
io.mcp-cn.upstash/context7-mcp
基于Upstash的向量搜索和上下文管理MCP服务
MarkItDown MCP Server
io.mcp-cn.markitdown-mcp-npx
MarkItDown MCP服务器,提供无Docker依赖的NPX包装器,支持直接运行Microsoft的markitdown-mcp服务器,包括自动Python环境设置和依赖管理
常搭配使用
基于文件的规划
v3.23.0
io.clawhub.othmanadi/planning-with-files
面向多步 AI Agent 工作的持久化文件规划。将 task_plan.md、findings.md 与 progress.md 保存在磁盘上,生命周期钩子注入所选的项目规划上下文;自动恢复仅读取项目规划文件,显式运行 session-catchup.py --input-file 时读取同项目的本地 Agent……(原文截断)
OpenClaw 指挥中心
v1.5.0
io.clawhub.jontsai/command-center
OpenClaw 任务控制台仪表盘——实时会话监控、LLM 用量跟踪、成本情报与系统生命体征。在一处查看你所有的 AI Age……(原文截断)
ClawCall 语音电话
v2.0.1
io.clawhub.clawcall-dev/clawcall-dev
当用户需要 AI Agent 拨打美国电话、呼叫商家、处理通话等待或语音菜单、完成确认/改期/取消/预订/跟进/查询……时使用本技能(原文截断)。
中文公文写作
v2.0.25
io.clawhub.gongyu0918-debug/chinese-official-writing
用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理,适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论,以及采购、整改、反馈和 AI 算力等场景。
继续逛 AgentHub
大多数人安装前还会对比同类工具或看场景方案——下面这些能帮你少走弯路。
收录徽章:把 AgentHub 挂到你的官网
复制下面任意一段代码到项目主页、官网或 GitHub README。徽章是 SVG 热链,无需上传文件,链接指向本页,访客可由此直接找到安装方式。
<a href="https://myagenthub.cn/p/com.bluecat/integritymcp" title="AgentHub 已收录:integritymcp" target="_blank" rel="noopener">
<img src="https://myagenthub.cn/badge/com.bluecat/integritymcp" alt="AgentHub 已收录:integritymcp" height="20" style="border:0"/>
</a>[](https://myagenthub.cn/p/com.bluecat/integritymcp)徽章由 /badge/<资源ID> 动态生成,名称与收录状态变化后自动更新;请保留链接指向,它是收录来源的判定依据。
统一 Manifest
{
"id": "com.bluecat/integritymcp",
"type": "mcp-server",
"version": "26.1.0",
"displayName": "integritymcp",
"description": "BlueCat Integrity MCP Server (formerly bammcp)",
"distribution": {
"packages": [
{
"registryType": "oci",
"identifier": "quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d",
"runtimeHint": "docker",
"transport": "streamable-http",
"environmentVariables": [
{
"name": "BAM_BASE_URL",
"description": "BAM base URL (e.g., https://bam.bluecat.com).",
"isRequired": true
},
{
"name": "BAM_USERNAME",
"description": "BAM service-account username. Required unless the SSO pair (BAM_SSO_USERNAME + BAM_SSO_PASSWORD) is used instead — the server needs exactly one of the two pairs."
},
{
"name": "BAM_PASSWORD",
"description": "BAM service-account password. Required alongside BAM_USERNAME, unless the SSO pair is used instead.",
"isSecret": true
},
{
"name": "BAM_SSO_USERNAME",
"description": "BAM SSO username. Alternative to BAM_USERNAME + BAM_PASSWORD; the server needs exactly one of the two pairs."
},
{
"name": "BAM_SSO_PASSWORD",
"description": "BAM SSO password. Required alongside BAM_SSO_USERNAME when using the SSO pair.",
"isSecret": true
},
{
"name": "MCP_AUTH_MODE",
"description": "Client authentication mode for the /mcp endpoint. One of: none | static-key | signed-key | resource-server. Required at runtime — the server refuses to start without it (no default).",
"isRequired": true
},
{
"name": "MCP_API_KEY",
"description": "Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key.",
"isSecret": true
},
{
"name": "MCP_REQUEST_STATE_KEY",
"description": "HMAC key (at least 32 bytes) sealing the approval-gated write tools' requestState on MCP 2026-07-28 connections (#1031). Optional: unset uses a random per-process key, which is fine for a single replica; set the same value on every replica of a multi-replica deployment.",
"isSecret": true
},
{
"name": "MCP_REQUEST_STATE_KEY_PREVIOUS",
"description": "Second requestState HMAC key, accepted for opening a sealed plan but never for sealing one: two-key rotation of MCP_REQUEST_STATE_KEY (#1032). Optional, and only valid together with MCP_REQUEST_STATE_KEY. When rolling the key across replicas set this to the old key, and remove it two minutes after the last replica restarted.",
"isSecret": true
},
{
"name": "MCP_ED25519_PUBLIC_KEY",
"description": "Ed25519 public key (base64url) that MCP_AUTH_MODE=signed-key verifies license tokens against. DEFAULTS TO A SHARED DEMO KEY, which authenticates a token holder rather than a customer — every BlueCat-issued token for this server verifies against it. For anything beyond a trial, generate a per-deployment key pair (license-keygen --gen-key) and set this to its public half."
},
{
"name": "MCP_SIGNED_KEY_AUDIENCE",
"description": "When set, a license token must carry exactly this audience or it is rejected — a declarative scope check on top of the key, so a token minted for another deployment fails even if it verifies. Unset means the aud claim is not checked. Only meaningful with MCP_AUTH_MODE=signed-key."
},
{
"name": "MCP_OAUTH_ISSUER",
"description": "Token issuer URL, matched against the iss claim of incoming JWTs. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it."
},
{
"name": "MCP_OAUTH_JWKS_URI",
"description": "JWKS endpoint whose public keys verify the signature on every incoming Bearer JWT. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it."
},
{
"name": "MCP_OAUTH_AUDIENCE",
"description": "Expected JWT aud claim for MCP_AUTH_MODE=resource-server. A token carrying a different audience, or no aud claim at all, is rejected. Unset skips audience validation entirely."
},
{
"name": "ACCEPT_EULA",
"description": "Set to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it.",
"isRequired": true
}
]
}
],
"remotes": []
},
"dependencies": [],
"installTargets": [
"claude-code",
"claude-desktop",
"cursor",
"vscode",
"trae",
"cherry-studio",
"lingma",
"windsurf",
"cline",
"workbuddy"
],
"keywords": [],
"provenance": {
"origin": "official-mcp-registry",
"originalId": "com.bluecat/integritymcp",
"originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/com.bluecat%2Fintegritymcp/versions/latest",
"isOfficial": true,
"status": "active"
}
}