World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
MCP server for Alloy Navigator's REST API - IT asset management and ITSM data for MSPs.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Alloy Navigator。按照 https://mcp.popnx.com/i/wyre-ai-alloy-navigator-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 2/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要 Alloy Navigator 的密钥(在开发者网站创建) · 需要填写 1 项设置(ALLOY_BASE_URL) · 需要先在电脑上安装 Docker(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Alloy Navigator,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "alloy-navigator": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "ALLOY_BASE_URL", "-e", "ALLOY_CLIENT_ID", "-e", "ALLOY_CLIENT_SECRET", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1" ], "env": { "ALLOY_BASE_URL": "your-value", "ALLOY_CLIENT_ID": "your-value", "ALLOY_CLIENT_SECRET": "your-value", "AUTH_MODE": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Alloy Navigator 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
ALLOY_BASE_URL Base URL of the Alloy Navigator server this connector talks to, e.g. https://alloy.example.com. Every Alloy Navigator instance is self-hosted (on-prem or self-hosted-cloud); there is no shared hosted…说明仍为英文原文。
SettingsDeveloperEdit Config
{
"mcpServers": {
"alloy-navigator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ALLOY_BASE_URL",
"-e",
"ALLOY_CLIENT_ID",
"-e",
"ALLOY_CLIENT_SECRET",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
],
"env": {
"ALLOY_BASE_URL": "your-value",
"ALLOY_CLIENT_ID": "your-value",
"ALLOY_CLIENT_SECRET": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Alloy Navigator 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Alloy Navigator,或回答中出现 Alloy Navigator 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_TRANSPORT 服务器的传输模式。本地 CLI 使用时设为 'stdio';镜像默认为 'http',用于网关托管。 LOG_LEVEL 日志详细程度:debug、info、warn、error 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Alloy Navigator
Alloy Navigator 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Alloy Navigator 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要 Alloy Navigator 的密钥(在开发者网站创建) · 需要填写 1 项设置(ALLOY_BASE_URL) · 需要先在电脑上安装 Docker(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Alloy Navigator,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user alloy-navigator --env ALLOY_BASE_URL=your-value --env ALLOY_CLIENT_ID=your-value --env ALLOY_CLIENT_SECRET=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e ALLOY_BASE_URL -e ALLOY_CLIENT_ID -e ALLOY_CLIENT_SECRET -e AUTH_MODE ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Alloy Navigator 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
ALLOY_BASE_URL Base URL of the Alloy Navigator server this connector talks to, e.g. https://alloy.example.com. Every Alloy Navigator instance is self-hosted (on-prem or self-hosted-cloud); there is no shared hosted…说明仍为英文原文。
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user alloy-navigator --env ALLOY_BASE_URL=your-value --env ALLOY_CLIENT_ID=your-value --env ALLOY_CLIENT_SECRET=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e ALLOY_BASE_URL -e ALLOY_CLIENT_ID -e ALLOY_CLIENT_SECRET -e AUTH_MODE ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Alloy Navigator 在列表中并显示已连接
用 Alloy Navigator 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Alloy Navigator,或回答中出现 Alloy Navigator 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_TRANSPORT 服务器的传输模式。本地 CLI 使用时设为 'stdio';镜像默认为 'http',用于网关托管。 LOG_LEVEL 日志详细程度:debug、info、warn、error 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Alloy Navigator 的密钥(在开发者网站创建) · 需要填写 1 项设置(ALLOY_BASE_URL) · 需要先在电脑上安装 Docker(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Alloy Navigator,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "alloy-navigator": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "ALLOY_BASE_URL", "-e", "ALLOY_CLIENT_ID", "-e", "ALLOY_CLIENT_SECRET", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1" ], "env": { "ALLOY_BASE_URL": "your-value", "ALLOY_CLIENT_ID": "your-value", "ALLOY_CLIENT_SECRET": "your-value", "AUTH_MODE": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Alloy Navigator 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
ALLOY_BASE_URL Base URL of the Alloy Navigator server this connector talks to, e.g. https://alloy.example.com. Every Alloy Navigator instance is self-hosted (on-prem or self-hosted-cloud); there is no shared hosted…说明仍为英文原文。
在 Alloy Navigator 的设置中,ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Alloy Navigator 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Alloy Navigator,或回答中出现 Alloy Navigator 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_TRANSPORT 服务器的传输模式。本地 CLI 使用时设为 'stdio';镜像默认为 'http',用于网关托管。 LOG_LEVEL 日志详细程度:debug、info、warn、error 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Alloy Navigator 的密钥(在开发者网站创建) · 需要填写 1 项设置(ALLOY_BASE_URL) · 需要先在电脑上安装 Docker(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Alloy Navigator,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "alloy-navigator": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "ALLOY_BASE_URL", "-e", "ALLOY_CLIENT_ID", "-e", "ALLOY_CLIENT_SECRET", "-e", "AUTH_MODE", "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1" ], "env": { "ALLOY_BASE_URL": "your-value", "ALLOY_CLIENT_ID": "your-value", "ALLOY_CLIENT_SECRET": "your-value", "AUTH_MODE": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Alloy Navigator 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
这些是程序设置,不是密钥,无需注册。按开发者的说明填写。
ALLOY_BASE_URL Base URL of the Alloy Navigator server this connector talks to, e.g. https://alloy.example.com. Every Alloy Navigator instance is self-hosted (on-prem or self-hosted-cloud); there is no shared hosted…说明仍为英文原文。
在 Alloy Navigator 的设置中,ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Alloy Navigator 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Alloy Navigator,或回答中出现 Alloy Navigator 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_TRANSPORT 服务器的传输模式。本地 CLI 使用时设为 'stdio';镜像默认为 'http',用于网关托管。 LOG_LEVEL 日志详细程度:debug、info、warn、error 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user alloy-navigator --env ALLOY_BASE_URL=your-value --env ALLOY_CLIENT_ID=your-value --env ALLOY_CLIENT_SECRET=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e ALLOY_BASE_URL -e ALLOY_CLIENT_ID -e ALLOY_CLIENT_SECRET -e AUTH_MODE ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"alloy-navigator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ALLOY_BASE_URL",
"-e",
"ALLOY_CLIENT_ID",
"-e",
"ALLOY_CLIENT_SECRET",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
],
"env": {
"ALLOY_BASE_URL": "your-value",
"ALLOY_CLIENT_ID": "your-value",
"ALLOY_CLIENT_SECRET": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"alloy-navigator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ALLOY_BASE_URL",
"-e",
"ALLOY_CLIENT_ID",
"-e",
"ALLOY_CLIENT_SECRET",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
],
"env": {
"ALLOY_BASE_URL": "your-value",
"ALLOY_CLIENT_ID": "your-value",
"ALLOY_CLIENT_SECRET": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"alloy-navigator": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ALLOY_BASE_URL",
"-e",
"ALLOY_CLIENT_ID",
"-e",
"ALLOY_CLIENT_SECRET",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
],
"env": {
"ALLOY_BASE_URL": "your-value",
"ALLOY_CLIENT_ID": "your-value",
"ALLOY_CLIENT_SECRET": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}ALLOY_BASE_URL 必填 envALLOY_CLIENT_ID 机密 必填 envALLOY_CLIENT_SECRET 机密 必填 envMCP_TRANSPORT envAUTH_MODE 机密 必填 envLOG_LEVEL env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 WYRE-AI 验证,该账户拥有此仓库
代码最后更新于6天前
GitHub 无法识别许可证类型;请打开文件自行查看
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/wyre-ai-alloy-navigator-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于6天前,最新版本(1.0.1)于33天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Alloy Navigator | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 2/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | NOASSERTION | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for Alloy Navigator's REST API - IT asset management, ITSM, and network inventory data (incidents, work orders, assets, software catalog, consumables, and more) for AI assistants and the WYRE Conduit gateway.
Alloy Navigator authenticates third-party applications with the OAuth2 client_credentials grant. An application account is registered in the Alloy Navigator Settings App under Services > API > Applications, which issues a client ID and client secret. This connector exchanges those for a bearer access token by POSTing to /api/token, then sends Authorization: Bearer on every subsequent request. Access tokens are valid for 8 hours per Alloy Navigator's own documentation; this connector caches a token per credential set and transparently re-authenticates once it's near expiry (see src/auth.ts).
Alloy Navigator has no fixed hosted API endpoint - every instance (on-premises, or a customer's own self-hosted-cloud tenant) is deployed at its own base URL, so this connector requires all three of a base URL, a client ID, and a client secret. In gateway mode all three arrive per-request via the X-Alloy-Base-Url, X-Alloy-Client-Id, and X-Alloy-Client-Secret headers; in local/stdio mode they're read once from ALLOY_BASE_URL, ALLOY_CLIENT_ID, and ALLOY_CLIENT_SECRET.
Alloy Navigator's API module (and this connector's application-account grant type specifically) requires the API Module to be installed and enabled on the target instance - see Alloy Navigator's own Installation Guide ("Installing and Configuring the API Module") if a client_credentials request returns a connection or 404 error rather than an auth error.
Vendor-documented, not independently verified against a live account (see Verification below for why): Alloy Navigator's API User's Guide describes application accounts as accounts used by "third-party applications that run without a signed-in user present," distinct from a regular technician (username/password) account, but does not document a way to scope an application account's *read* access below whatever object classes and fields the account otherwise has permission to see in Alloy Navigator's own security/role configuration. In practice this means the actual read-only guarantee is enforced by this connector's tool surface (GET-only, no workflow-action execution), not by the credential itself - Alloy Navigator's own workflow-action model means even a technically "read" API call executes through the same account whose role could, in principle, also be granted write/workflow-action permissions elsewhere. Customers should create a dedicated, minimally-privileged application account for this connector, matching the same practice recommended by other vendors in this fleet (e.g. PRTG) whose API keys inherit the creating account's full permission set.
This connector was built directly against Alloy Navigator's official API User's Guide (docs.alloysoftware.com/alloynavigator/docs/api-userguide/), not against secondary documentation or a naming convention - every tool below maps to one real, documented GET operation, with its exact query parameters and response shape verified against the guide's own worked examples (see each tool's JSDoc in src/client.ts for the source example it was checked against). What it is not is independently verified against a live Alloy Navigator instance: Alloy Navigator does not publish a public self-serve trial or sandbox instance, and provisioning one requires a live sales/licensing engagement this build environment could not complete. This is a build-environment limitation, not a vendor-side approval gate for a customer with an existing license.
| Env var | Description | |||
|---|---|---|---|---|
ALLOY_BASE_URL | Base URL of the Alloy Navigator server, e.g. https://alloy.example.com. | |||
ALLOY_CLIENT_ID | Application account client ID, issued under Settings App > Services > API > Applications. | |||
ALLOY_CLIENT_SECRET | Application account client secret, issued alongside the client ID. | |||
MCP_TRANSPORT | stdio (default) or http. | |||
AUTH_MODE | env (default, reads the vars above) or gateway (credentials arrive per-request via the X-Alloy-Base-Url / X-Alloy-Client-Id / X-Alloy-Client-Secret headers, injected by the Conduit gateway). The Docker image and Compose file default to gateway. In gateway mode, /mcp returns 401 when any of those headers is missing and never falls back to ALLOY_*. | |||
CONDUIT_S2S_SECRET | Required for HTTP. Service-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, secret, placeholder, your-s2s-secret, replace-with-a-real-secret, and the same list in src/http.ts). Compose will not start when it is unset. Never commit a real value. The process never logs it. | |||
MCP_ALLOW_INSECURE_DEV | Set to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, skips X-Gateway-S2S, and listens on 127.0.0.1 only. A wider MCP_HTTP_HOST is overridden. A known placeholder secret is still refused. | |||
MCP_HTTP_HOST | Bind address when MCP_TRANSPORT=http. Defaults to 127.0.0.1. A configured CONDUIT_S2S_SECRET honors this value, including 0.0.0.0. The container image sets 0.0.0.0. Without a secret, the listener is 127.0.0.1 only. | |||
MCP_HTTP_PORT | HTTP port. Defaults to 8080. | |||
LOG_LEVEL | debug \ | info (default) \ | warn \ | error. |
/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, 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, not a copy of the secret:
t=<unix seconds>,v1=<hex hmac-sha256>
is HMAC-SHA256 of the ASCII string t= (the same t= prefix and the same decimal timestamp), keyed with CONDUIT_S2S_SECRET, encoded as lowercase hex. The timestamp must be within 300 seconds of the server clock.
import { createHmac } from 'node:crypto';
const secret = process.env.CONDUIT_S2S_SECRET; const t = Math.floor(Date.now() / 1000); const v1 = createHmac('sha256', secret).update(t=${t}).digest('hex'); const xGatewayS2s = t=${t},v1=${v1};
In AUTH_MODE=gateway, /mcp also requires X-Alloy-Base-Url, X-Alloy-Client-Id, and X-Alloy-Client-Secret. Those headers are the only credential source for that request.
await fetch('http://127.0.0.1:8080/mcp', {
method: 'POST', headers: { 'content-type': 'application/json', accept: 'application/json, text/event-stream', 'x-gateway-s2s': xGatewayS2s, 'x-alloy-base-url': 'https://alloy.example.com', 'x-alloy-client-id': 'application-client-id', 'x-alloy-client-secret': 'application-client-secret', }, body: JSON.stringify({ jsonrpc: '2.0', id: 1, method: 'tools/list' }), });
Alloy Navigator's API is class-generic rather than one fixed REST path per object type (unlike, say, PRTG's /devices, /sensors, etc.) - a single object class parameter (Incidents, Computers, Work Orders, Consumables, SoftwareCatalog, Purchase Order Items, and so on) selects what you're querying. This connector's 4 tools mirror that shape faithfully rather than inventing per-class tools Alloy Navigator's own API doesn't have.
alloy_list_objects - list/search objects of a given object class, with field selection, sorting, paging, free-text search, and per-field filters.alloy_get_object - get every field of a single object by its OID (ticket number) or database record GUID.alloy_get_object_activities - get the activity/history log entries recorded against a single object (status changes, assignment changes, system notes).alloy_get_dictionary - get the allowed reference/classification values (e.g. valid Status or Types values) for a field on an object class.This is a deliberately narrow, read-only v1 surface: 4 `GET` operations covering exactly Alloy Navigator's generic object query, single-object read, activity/history read, and reference-value lookup - nothing else. Alloy Navigator's API User's Guide documents a significantly larger surface built around workflow actions (Alloy Navigator does not create or update objects directly; every mutation runs as a named workflow action against an object). This connector excludes every one of those by design, not by oversight:
Hard-excluded (object creation and mutation - all mutation in Alloy Navigator's API model runs through workflow actions) - never implemented: POST /object/ /action/ - executing a workflow action (the mechanism Alloy Navigator's own "Creating objects" documentation describes for creating new incidents, work orders, assets, and any other object) is a write by definition and is excluded outright, including any workflow action a customer's instance might label as innocuous-sounding (e.g. an "Acknowledge" or "Close" action) - this connector has no way to distinguish a read-flavored action from a real state-changing one, so none are exposed.
Hard-excluded (redundant POST-based retrieval) - never implemented: Alloy Navigator's guide documents POST variants of both the object-list and object-activities GET endpoints (POST / , POST /Activities/ ), intended to work around URL query-length limits when a caller constructs a raw URL by hand. This connector builds every request server-side from structured tool arguments rather than a hand-typed URL, so the length limit the POST variant exists to work around doesn't apply here - implementing it would add a second code path with identical behavior and no read/write distinction of its own, so it's excluded as redundant rather than as a scope boundary.
Hard-excluded (user/session/application administration - identity and credential management, not ITSM/asset data) - never implemented: the technician (username/password) authentication grant (POST /api/token with grant_type=password) - this connector only uses the application-account client_credentials grant, the shape intended for unattended service integrations - and any endpoint for managing application accounts, technician accounts, or sessions themselves.
Hard-excluded (out of ITSM/asset-data scope) - never implemented: GET /api/v2/GetAppConfig - configuration for a registered mobile scanner application (Settings App > Services > Mobile Applications), unrelated to IT asset/ITSM record data and dependent on a customer having registered a mobile app in the first place.
They can be added as a follow-up if there's demand, after a deliberate scope decision - not by default.
npm install
npm run build npm test npm run lint # tsc --noEmit
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 the S2S secret. In gateway mode, Alloy Navigator credentials arrive on each request as X-Alloy-* headers; the image does not read them from the environment.
docker build -t alloy-navigator-mcp .
docker run \ -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -p 127.0.0.1:8080:8080 \ alloy-navigator-mcp
Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and passes no ALLOY_* variables:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secr