com.bluecat/integritymcp

Registre officiel Autres

BlueCat Integrity MCP Server (formerly bammcp)

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 »).

OCI package quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d
Claude Code
claude mcp add integritymcp -e 'BAM_BASE_URL=<BAM_BASE_URL>' -e 'BAM_USERNAME=<BAM_USERNAME>' -e 'BAM_PASSWORD=<your bam_password>' -e 'BAM_SSO_USERNAME=<BAM_SSO_USERNAME>' -e 'BAM_SSO_PASSWORD=<your bam_sso_password>' -e 'MCP_AUTH_MODE=<MCP_AUTH_MODE>' -e 'MCP_API_KEY=<your mcp_api_key>' -e 'MCP_REQUEST_STATE_KEY=<your mcp_request_state_key>' -e 'MCP_REQUEST_STATE_KEY_PREVIOUS=<your mcp_request_state_key_previous>' -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/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "integritymcp": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
            ],
            "env": {
                "BAM_BASE_URL": "<BAM_BASE_URL>",
                "BAM_USERNAME": "<BAM_USERNAME>",
                "BAM_PASSWORD": "<your bam_password>",
                "BAM_SSO_USERNAME": "<BAM_SSO_USERNAME>",
                "BAM_SSO_PASSWORD": "<your bam_sso_password>",
                "MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
                "MCP_API_KEY": "<your mcp_api_key>",
                "MCP_REQUEST_STATE_KEY": "<your mcp_request_state_key>",
                "MCP_REQUEST_STATE_KEY_PREVIOUS": "<your mcp_request_state_key_previous>",
                "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

  • BAM_BASE_URL obligatoire BAM base URL (e.g., https://bam.bluecat.com).
  • BAM_USERNAME BAM service-account username. Required unless the SSO pair (BAM_SSO_USERNAME + BAM_SSO_PASSWORD) is used instead — the server needs exactly one of the two pairs.
  • BAM_PASSWORD secret BAM service-account password. Required alongside BAM_USERNAME, unless the SSO pair is used instead.
  • BAM_SSO_USERNAME BAM SSO username. Alternative to BAM_USERNAME + BAM_PASSWORD; the server needs exactly one of the two pairs.
  • BAM_SSO_PASSWORD secret BAM SSO password. Required alongside BAM_SSO_USERNAME when using the SSO pair.
  • MCP_AUTH_MODE obligatoire 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 secret Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key.
  • MCP_REQUEST_STATE_KEY secret HMAC key (at least 32 bytes) sealing the approval-gated write tools' requestState on MCP 2026-07-28 connections (#1031). Optional: unset uses a random per-process key, which is fine for a single replica; set the same value on every replica of a multi-replica deployment.
  • MCP_REQUEST_STATE_KEY_PREVIOUS secret Second requestState HMAC key, accepted for opening a sealed plan but never for sealing one: two-key rotation of MCP_REQUEST_STATE_KEY (#1032). Optional, and only valid together with MCP_REQUEST_STATE_KEY. When rolling the key across replicas set this to the old key, and remove it two minutes after the last replica restarted.
  • 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 obligatoire 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/integritymcp ?

BlueCat Integrity MCP Server (formerly bammcp)

Comment installer com.bluecat/integritymcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add integritymcp -e 'BAM_BASE_URL=<BAM_BASE_URL>' -e 'BAM_USERNAME=<BAM_USERNAME>' -e 'BAM_PASSWORD=<your bam_password>' -e 'BAM_SSO_USERNAME=<BAM_SSO_USERNAME>' -e 'BAM_SSO_PASSWORD=<your bam_sso_password>' -e 'MCP_AUTH_MODE=<MCP_AUTH_MODE>' -e 'MCP_API_KEY=<your mcp_api_key>' -e 'MCP_REQUEST_STATE_KEY=<your mcp_request_state_key>' -e 'MCP_REQUEST_STATE_KEY_PREVIOUS=<your mcp_request_state_key_previous>' -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/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour com.bluecat/integritymcp ?

Oui. Il attend BAM_BASE_URL, BAM_PASSWORD, BAM_SSO_PASSWORD, MCP_AUTH_MODE, MCP_API_KEY, MCP_REQUEST_STATE_KEY, MCP_REQUEST_STATE_KEY_PREVIOUS, ACCEPT_EULA, à renseigner dans sa configuration.

Qui maintient com.bluecat/integritymcp ?

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.