Operate1 min read

Operating MCP

Architecture, certification evidence and parity planning for the OpsKnight MCP server.

  • Architecture and threat model: authentication, authorization, workload isolation and outstanding work.
  • Monitoring and capacity: every MCP metric, the shipped alerts, the per-request log line, sizing per replica and the MCP_FORCE_DISABLED emergency stop.
  • Threat model, data flow and control matrix: what the MCP server protects, the threats considered, the controls that answer them with their evidence, and the residual risks. Not an independent assessment.
  • Service-account design (proposal): a non-human identity for headless agents, for sign-off before any code.
  • Release status and certification: what is verified for 2.2.0, what is not, and how release evidence is collected.
  • Exclusion review packet: open operations with proposed dispositions.
  • Full-parity delivery: the parity plan and acceptance criteria.
  • Contributing to MCP: local checks, manual OAuth and protocol calls, and the reviewed workflows, for people working on OpsKnight itself.

To set MCP up, see the self-hosted setup guide.

Last updated for v2.2.0

Edit this page on GitHub