Quotient MCP

quotient-mcp is an maintainence bridge for Quotient. It exposes Quotient operational data and admin actions through MCP so operators can inspect service health, verify scoring activity, review PCR state, and make controlled maintenance changes from an MCP client.

This repository is intended for internal infrastructure use. The focus is Quotient server maintenance, service validation, and operator workflows rather than end-user access.

Maintenance Workflows

The server exposes MCP tools for common Quotient maintenance tasks:

• Check public service, score, and uptime graphs
• Review announcements, team metadata, and team service summaries
• Inspect historical service check results for a specific team and service
• Audit engine state, runner tasks, score exports, and red overview data
• Review enabled service matrices across teams
• Inspect PCR credential state and PCR history
• Pause or resume the engine during maintenance windows
• Mark the event started state when coordinating lab operations
• Enable or disable services for individual teams
• Update team identifiers and active flags
• Submit or reset PCR credentials during recovery work

Authentication

Set the Quotient base URL:

export QUOTIENT_BASE_URL="https://quotient.example.com"

Authenticate with either a Quotient session cookie or a local Quotient username/password pair.

Session cookie:

export QUOTIENT_SESSION_COOKIE="PASTE_THE_COOKIE_VALUE_HERE"

Username/password:

export QUOTIENT_USERNAME="admin"
export QUOTIENT_PASSWORD="secret"

If the Quotient deployment uses self-signed TLS, also set:

export QUOTIENT_ALLOW_INSECURE_TLS=true

Exposure Profile

The default startup profile exposes inspection and audit workflows for Quotient maintenance.

To enable maintenance actions that change Quotient state, start the server with:

export QUOTIENT_MCP_MODE=config

With config enabled, the MCP server can perform operational changes such as pausing the engine, resetting scores, updating team service checks, and managing PCR credentials. These actions still require an authenticated Quotient session with the necessary server-side permissions.

Run It

source /home/user/.cargo/env
cargo run --quiet

To launch with maintenance write actions enabled:

source /home/user/.cargo/env
QUOTIENT_MCP_MODE=config cargo run --quiet

Recommended Checks

Typical internal lab checks through an MCP client:

• Confirm the server can authenticate and report its current auth summary
• Pull service graphs to verify scoring data is moving
• Inspect a team summary and service check history when a service is flapping
• Review the admin team-check matrix before enabling or disabling a service
• Check engine state and active runner tasks before planned maintenance
• Export scores or inspect PCR history during incident response

Example MCP Client Config

{
  "mcpServers": {
    "quotient": {
      "command": "bash",
      "args": [
        "-lc",
        "source /home/user/.cargo/env && cd /home/user/quotient/quotient-mcp && cargo run --quiet"
      ],
      "env": {
        "QUOTIENT_BASE_URL": "https://quotient.example.com",
        "QUOTIENT_SESSION_COOKIE": "PASTE_COOKIE_HERE"
      }
    }
  }
}

For maintenance sessions that need write access, add:

{
  "QUOTIENT_MCP_MODE": "config"
}