MCP Server for OSCAL

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

этот файл ставится пользователю, но в репозитории его нет

        commit = subprocess.run(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-server-for-oscal -- uvx mcp-server-for-oscal

{
  "mcpServers": {
    "mcp-server-for-oscal": {
      "args": [
        "mcp-server-for-oscal"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.mcp-server-for-oscal]
command = "uvx"
args = ["mcp-server-for-oscal"]

{
  "mcpServers": {
    "mcp-server-for-oscal": {
      "args": [
        "mcp-server-for-oscal"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "mcp-server-for-oscal": {
      "args": [
        "mcp-server-for-oscal"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: BEDROCK_MODEL_ID (AWS Bedrock model ID for OSCAL documentation queries), OSCAL_KB_ID (AWS Bedrock Knowledge Base ID for OSCAL documentation), AWS_PROFILE (AWS CLI profile name for credential resolution), AWS_REGION (AWS region for Bedrock API calls), LOG_LEVEL (Logging verbosity level (DEBUG, INFO, WARNING, ERROR)). The author declared them in the registry entry; get the values from the project itself.