mcpField
I

integritymcp

ローカル
@bluecat.comクラウド・インフラ

integritymcp について

BlueCat Integrity MCP サーバー（旧 bammcp）

設定

ローカルサーバーの設定はどのクライアントでも共通です。コピーしてクライアントの MCP 設定ファイルに貼り付けてください。

mcp.json · 共通設定
{
  "mcpServers": {
    "com-bluecat-integritymcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BAM_BASE_URL",
        "-e",
        "BAM_USERNAME",
        "-e",
        "BAM_PASSWORD",
        "-e",
        "BAM_SSO_USERNAME",
        "-e",
        "BAM_SSO_PASSWORD",
        "-e",
        "MCP_AUTH_MODE",
        "-e",
        "MCP_API_KEY",
        "-e",
        "MCP_REQUEST_STATE_KEY",
        "-e",
        "MCP_REQUEST_STATE_KEY_PREVIOUS",
        "-e",
        "MCP_ED25519_PUBLIC_KEY",
        "-e",
        "MCP_SIGNED_KEY_AUDIENCE",
        "-e",
        "MCP_OAUTH_ISSUER",
        "-e",
        "MCP_OAUTH_JWKS_URI",
        "-e",
        "MCP_OAUTH_AUDIENCE",
        "-e",
        "ACCEPT_EULA",
        "quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d"
      ],
      "env": {
        "BAM_BASE_URL": "<BAM_BASE_URL>",
        "BAM_USERNAME": "<BAM_USERNAME>",
        "BAM_PASSWORD": "<BAM_PASSWORD>",
        "BAM_SSO_USERNAME": "<BAM_SSO_USERNAME>",
        "BAM_SSO_PASSWORD": "<BAM_SSO_PASSWORD>",
        "MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
        "MCP_API_KEY": "<MCP_API_KEY>",
        "MCP_REQUEST_STATE_KEY": "<MCP_REQUEST_STATE_KEY>",
        "MCP_REQUEST_STATE_KEY_PREVIOUS": "<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>"
      }
    }
  }
}
起動コマンドdocker run -i --rm -e BAM_BASE_URL -e BAM_USERNAME -e BAM_PASSWORD -e BAM_SSO_USERNAME -e BAM_SSO_PASSWORD -e MCP_AUTH_MODE -e MCP_API_KEY -e MCP_REQUEST_STATE_KEY -e MCP_REQUEST_STATE_KEY_PREVIOUS -e MCP_ED25519_PUBLIC_KEY -e MCP_SIGNED_KEY_AUDIENCE -e MCP_OAUTH_ISSUER -e MCP_OAUTH_JWKS_URI -e MCP_OAUTH_AUDIENCE -e ACCEPT_EULA quay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d
設定が必要な環境変数
BAM_BASE_URLBAM base URL (e.g., https://bam.bluecat.com).
BAM_USERNAMEBAM 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シークレットBAM service-account password. Required alongside BAM_USERNAME, unless the SSO pair is used instead.
BAM_SSO_USERNAMEBAM SSO username. Alternative to BAM_USERNAME + BAM_PASSWORD; the server needs exactly one of the two pairs.
BAM_SSO_PASSWORDシークレットBAM SSO password. Required alongside BAM_SSO_USERNAME when using the SSO pair.
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_REQUEST_STATE_KEYシークレット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シークレット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_EULASet to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it.

ローカルサーバーにはマシン上の実行環境（Node.js 18 以上など）が必要です。設定ファイルの場所はクライアントごとに異なります。

パッケージ
ociquay.io/bluecat/integritymcp@sha256:1b38c5fc9321ced181e414b82873a705a46b80c28209227e39fea4578e7a3a0d

ツール

ツール一覧はまだ取得されていません

ローカルサーバーのツールはマシン上で起動して初めて取得できます。メンテナーはまだツール一覧を提供していません。

詳細

メンテナーはまだ詳細を追加していません。リポジトリの README をご覧ください。

コメント

Markdown 対応

MCP は初めてですか？

プロトコルの概要から最初のサーバーの導入まで、よくある疑問にまとめて答えます。

AI アプリケーションが外部のツールやデータソースに統一的な方法で接続するためのオープンなプロトコルです。クライアントはモデルとの対話を担い、MCP サーバーはツール・リソース・プロンプトテンプレートを提供します。標準メッセージでやり取りするため、1 つのサーバーを複数のクライアントで再利用できます。