How do I install Micetromcp?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Micetromcp need an API key?

The publisher lists these environment variables: MICETRO_BASE_URL, MICETRO_USERNAME, MICETRO_PASSWORD, MICETRO_API_KEY, MCP_AUTH_MODE, MCP_API_KEY, MCP_ED25519_PUBLIC_KEY, MCP_SIGNED_KEY_AUDIENCE, MCP_OAUTH_ISSUER, MCP_OAUTH_JWKS_URI, MCP_OAUTH_AUDIENCE, ACCEPT_EULA.

What transport does Micetromcp use?

Micetromcp runs locally over stdio.

When was Micetromcp last checked?

Last checked 2026-10-16. BlueCat Micetro MCP Server

Micetromcp

by com.bluecat

BlueCat Micetro MCP Server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

docker run -i --rm quay.io/bluecat/micetromcp@sha256:6319226443364523115c31ad4e51b725ab5d9599af2be4ea7dc43be66f36be5d

Credentials from the publisher

MICETRO_BASE_URL — Micetro base URL (e.g., https://micetro.bluecat.com).
MICETRO_USERNAME — Micetro service-account username. Required in self-hosted mode (MCP_DEPLOYMENT_MODE unset or self-hosted) unless MICETRO_API_KEY is used instead — the server needs exactly one of the two credential options. Not used in horizon mode (accepted and ignored — an operator is free to leave it set).
MICETRO_PASSWORD — Micetro service-account password. Required alongside MICETRO_USERNAME, unless MICETRO_API_KEY is used instead.
MICETRO_API_KEY — Micetro API key (Micetro 26.1 and later). Alternative to MICETRO_USERNAME + MICETRO_PASSWORD; wins over the username/password pair when both are set. Every outbound request carries `authorization: Bearer <key>` and no session login is performed. Unlike MICETRO_USERNAME/MICETRO_PASSWORD, which are simply not used in horizon mode, MICETRO_API_KEY is rejected at startup there — cloud mode has no fixed backend identity for a key to authenticate.
MCP_AUTH_MODE — 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).
MCP_API_KEY — Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key.
MCP_ED25519_PUBLIC_KEY — 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.
MCP_SIGNED_KEY_AUDIENCE — 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.
MCP_OAUTH_ISSUER — 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.
MCP_OAUTH_JWKS_URI — 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.
MCP_OAUTH_AUDIENCE — 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.
ACCEPT_EULA — Set to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it.

Provider

Claude Code

MICETRO_BASE_URL=<value> MICETRO_USERNAME=<value> MICETRO_PASSWORD=<secret> MICETRO_API_KEY=<secret> MCP_AUTH_MODE=<value> MCP_API_KEY=<secret> MCP_ED25519_PUBLIC_KEY=<value> MCP_SIGNED_KEY_AUDIENCE=<value> MCP_OAUTH_ISSUER=<value> MCP_OAUTH_JWKS_URI=<value> MCP_OAUTH_AUDIENCE=<value> ACCEPT_EULA=<value> claude mcp add com.bluecat-micetromcp -- docker run -i --rm quay.io/bluecat/micetromcp@sha256:6319226443364523115c31ad4e51b725ab5d9599af2be4ea7dc43be66f36be5d

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "com.bluecat-micetromcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "quay.io/bluecat/micetromcp@sha256:6319226443364523115c31ad4e51b725ab5d9599af2be4ea7dc43be66f36be5d"
      ],
      "env": {
        "MICETRO_BASE_URL": "<value>",
        "MICETRO_USERNAME": "<value>",
        "MICETRO_PASSWORD": "<secret>",
        "MICETRO_API_KEY": "<secret>",
        "MCP_AUTH_MODE": "<value>",
        "MCP_API_KEY": "<secret>",
        "MCP_ED25519_PUBLIC_KEY": "<value>",
        "MCP_SIGNED_KEY_AUDIENCE": "<value>",
        "MCP_OAUTH_ISSUER": "<value>",
        "MCP_OAUTH_JWKS_URI": "<value>",
        "MCP_OAUTH_AUDIENCE": "<value>",
        "ACCEPT_EULA": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all