Alloy Navigator MCP Server

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

Packages and local setup

The published oci package is ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.0. Its declared MCP transport is stdio.

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

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.