com.bluecat/micetromcp
BlueCat Micetro MCP Server
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
quay.io/bluecat/micetromcp@sha256:04d929d2f292ca8514ba26a0cfe9178068b591ae7b5f70b93fb4807e7bed70baclaude mcp add micetromcp -e 'MICETRO_BASE_URL=<MICETRO_BASE_URL>' -e 'MICETRO_USERNAME=<MICETRO_USERNAME>' -e 'MICETRO_PASSWORD=<your micetro_password>' -e 'MICETRO_API_KEY=<your micetro_api_key>' -e 'MCP_AUTH_MODE=<MCP_AUTH_MODE>' -e 'MCP_API_KEY=<your mcp_api_key>' -e 'MCP_ED25519_PUBLIC_KEY=<MCP_ED25519_PUBLIC_KEY>' -e 'MCP_SIGNED_KEY_AUDIENCE=<MCP_SIGNED_KEY_AUDIENCE>' -e 'MCP_OAUTH_ISSUER=<MCP_OAUTH_ISSUER>' -e 'MCP_OAUTH_JWKS_URI=<MCP_OAUTH_JWKS_URI>' -e 'MCP_OAUTH_AUDIENCE=<MCP_OAUTH_AUDIENCE>' -e 'ACCEPT_EULA=<ACCEPT_EULA>' -- docker run -i --rm quay.io/bluecat/micetromcp@sha256:04d929d2f292ca8514ba26a0cfe9178068b591ae7b5f70b93fb4807e7bed70ba
{
"mcpServers": {
"micetromcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/micetromcp@sha256:04d929d2f292ca8514ba26a0cfe9178068b591ae7b5f70b93fb4807e7bed70ba"
],
"env": {
"MICETRO_BASE_URL": "<MICETRO_BASE_URL>",
"MICETRO_USERNAME": "<MICETRO_USERNAME>",
"MICETRO_PASSWORD": "<your micetro_password>",
"MICETRO_API_KEY": "<your micetro_api_key>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"MCP_API_KEY": "<your mcp_api_key>",
"MCP_ED25519_PUBLIC_KEY": "<MCP_ED25519_PUBLIC_KEY>",
"MCP_SIGNED_KEY_AUDIENCE": "<MCP_SIGNED_KEY_AUDIENCE>",
"MCP_OAUTH_ISSUER": "<MCP_OAUTH_ISSUER>",
"MCP_OAUTH_JWKS_URI": "<MCP_OAUTH_JWKS_URI>",
"MCP_OAUTH_AUDIENCE": "<MCP_OAUTH_AUDIENCE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}
Variables d'environnement
MICETRO_BASE_URLobligatoire Micetro base URL (e.g., https://micetro.bluecat.com).MICETRO_USERNAMEMicetro service-account username. Required unless MICETRO_API_KEY is set — supply one of the two credential options.MICETRO_PASSWORDsecret Micetro service-account password. Required alongside MICETRO_USERNAME, unless MICETRO_API_KEY is used instead.MICETRO_API_KEYsecret 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.MCP_AUTH_MODEobligatoire 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_KEYsecret Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key.MCP_ED25519_PUBLIC_KEYEd25519 public key that MCP_AUTH_MODE=signed-key verifies license tokens against: the one BlueCat supplies with your license tokens, as the raw 32-byte public key, base64url-encoded without padding (43 characters). Required when MCP_AUTH_MODE=signed-key — the server refuses to start in that mode without it.MCP_SIGNED_KEY_AUDIENCEWhen 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_ISSUERToken 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_URIJWKS 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_AUDIENCEExpected 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_EULAobligatoire Set to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it.
Questions fréquentes
Qu'est-ce que com.bluecat/micetromcp ?
BlueCat Micetro MCP Server
Comment installer com.bluecat/micetromcp ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add micetromcp -e 'MICETRO_BASE_URL=<MICETRO_BASE_URL>' -e 'MICETRO_USERNAME=<MICETRO_USERNAME>' -e 'MICETRO_PASSWORD=<your micetro_password>' -e 'MICETRO_API_KEY=<your micetro_api_key>' -e 'MCP_AUTH_MODE=<MCP_AUTH_MODE>' -e 'MCP_API_KEY=<your mcp_api_key>' -e 'MCP_ED25519_PUBLIC_KEY=<MCP_ED25519_PUBLIC_KEY>' -e 'MCP_SIGNED_KEY_AUDIENCE=<MCP_SIGNED_KEY_AUDIENCE>' -e 'MCP_OAUTH_ISSUER=<MCP_OAUTH_ISSUER>' -e 'MCP_OAUTH_JWKS_URI=<MCP_OAUTH_JWKS_URI>' -e 'MCP_OAUTH_AUDIENCE=<MCP_OAUTH_AUDIENCE>' -e 'ACCEPT_EULA=<ACCEPT_EULA>' -- docker run -i --rm quay.io/bluecat/micetromcp@sha256:04d929d2f292ca8514ba26a0cfe9178068b591ae7b5f70b93fb4807e7bed70ba. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour com.bluecat/micetromcp ?
Oui. Il attend MICETRO_BASE_URL, MICETRO_PASSWORD, MICETRO_API_KEY, MCP_AUTH_MODE, MCP_API_KEY, ACCEPT_EULA, à renseigner dans sa configuration.
Qui maintient com.bluecat/micetromcp ?
Il est publié par com.bluecat. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.