Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Alloy Navigator

by WYRE-AIversion 1.0.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.WYRE-AI/alloy-navigator-mcp

How to install

What it does

MCP server for Alloy Navigator's REST API - IT asset management and ITSM data for MSPs.

  • Connects Runs on your computer
  • Account or key Needs ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE · 1 setting to fill in (ALLOY_BASE_URL)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Alloy Navigator. Follow https://mcp.popnx.com/i/wyre-ai-alloy-navigator-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Alloy Navigator for Claude on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Alloy Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Alloy Navigator key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Alloy Navigator site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • 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…

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "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"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Alloy Navigator and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Alloy Navigator or shows a Alloy Navigator tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Alloy Navigator yet

Alloy Navigator runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Alloy Navigator

  • You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time)
  • You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time)
  • You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Alloy Navigator for Claude Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Alloy Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Alloy Navigator key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Alloy Navigator site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • 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…

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    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

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Alloy Navigator listed as connected

  7. Try it

    Use Alloy Navigator and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Alloy Navigator or shows a Alloy Navigator tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Alloy Navigator for Cursor on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Alloy Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Alloy Navigator key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Alloy Navigator site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • 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…

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Alloy Navigator settings, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Alloy Navigator and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Alloy Navigator or shows a Alloy Navigator tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Alloy Navigator key (create it on the maker’s site) · 1 setting(s) to fill in (ALLOY_BASE_URL) · Install Docker on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Alloy Navigator for VS Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Alloy Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Docker (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    docker --version
    • A version number such as Docker version … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed

    Open the Docker download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version

    Install once; it works for everything that needs Docker

  2. Sign up and create a Alloy Navigator key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Alloy Navigator site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • 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…

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Alloy Navigator settings, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE, ALLOY_BASE_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Alloy Navigator and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Alloy Navigator or shows a Alloy Navigator tool in the answer, you are connected

2 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdio
  • LOG_LEVEL Log verbosity: debug, info, warn, error · default info

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Alloy Navigator💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

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.1

Claude 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"
      }
    }
  }
}

Values you fill in

  • ALLOY_BASE_URL required env
    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_CLIENT_ID secret required env
    Application account client ID, registered in Alloy Navigator's Settings App under Services > API > Applications.
  • ALLOY_CLIENT_SECRET secret required env
    Application account client secret, issued alongside the client ID.
  • MCP_TRANSPORT env
    Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODE secret required env
    Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVEL env
    Log verbosity: debug, info, warn, error

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
No licence stated
Connection
Runs on your computer
Latest versioni
1.0.1
Categoryi
Other
Published to registryi
Oct 17, 2026
Code last changedi
Nov 13, 2026
Maker
WYRE-AI
Packages
oci: ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account WYRE-AI, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 6 days ago

  • ! Caution

    Has a licence

    GitHub could not identify the licence type; open the file to check

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked: only npm and PyPI packages with a version can be checked

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/wyre-ai-alloy-navigator-mcp.svg)](https://mcp.popnx.com/en/servers/wyre-ai-alloy-navigator-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20749 servers in this category
  • Published to the registry more recently than 57% of the other 20749 servers in this category
  • Basic checks equal to or better than 46% of the other 20749 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Alloy Navigator safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, AUTH_MODE

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 6 days ago, and the latest version (1.0.1) reached the registry 33 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Alloy Navigator
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks2/34/44/44/41/44/4
LicenseNOASSERTIONAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Alloy Navigator MCP Server

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.

Authentication

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.

Credential scope

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.

Verification

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.

Configuration

Env varDescription
ALLOY_BASE_URLBase URL of the Alloy Navigator server, e.g. https://alloy.example.com.
ALLOY_CLIENT_IDApplication account client ID, issued under Settings App > Services > API > Applications.
ALLOY_CLIENT_SECRETApplication account client secret, issued alongside the client ID.
MCP_TRANSPORTstdio (default) or http.
AUTH_MODEenv (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_SECRETRequired 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_DEVSet 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_HOSTBind 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_PORTHTTP port. Defaults to 8080.
LOG_LEVELdebug \info (default) \warn \error.

/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

HTTP authentication

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' }), });

Tools

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.

Objects
  • 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.
Activities
  • alloy_get_object_activities - get the activity/history log entries recorded against a single object (status changes, assignment changes, system notes).
Dictionary
  • alloy_get_dictionary - get the allowed reference/classification values (e.g. valid Status or Types values) for a field on an object class.

Scope

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.

Development

npm install

npm run build npm test npm run lint # tsc --noEmit

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 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

Only the beginning is shown; read the rest in the repo