CodeQuality MCP

Focused code-quality analysis and finding explanations

CodeQuality MCP analyzes source input for concrete quality findings and explains each result through the hosted catalog.

Included with an active usage plan

Available through the hosted catalog. Calls count against the shared allowance on the account plan.

Compare usage plans

Why it exists

Analyze supplied source for concrete quality issues, then explain individual findings and practical remediation without requiring repository access.

Generic terminals, provider APIs, and custom prompts can cover parts of the work, but the caller must supply permission limits, output requirements, failure handling, and usage accounting.

Connection and contract

Connect from an MCP-aware client with an account-scoped Monarchic key. The hosted route checks access, runs the named product contract, and records the operation on the account receipt.

The product-specific schema defines the inputs and outputs used by clients and downstream automation.

Current limits

The analysis covers only the submitted files and cannot infer repository-wide behavior from missing code.

Requires an authenticated, entitled account. The call receives inline source and does not need repository or provider access.

What you get

Analyze supplied source without cloning a repository
Separate lightweight explanations from deeper analysis
Return structured findings with practical remediation

Core use case

Analyze supplied source for concrete quality issues, then explain individual findings and practical remediation without requiring repository access.

Outcomes

Review code through a bounded source-input interface
Separate quick finding explanations from deeper analysis
Receive structured findings that downstream tools can consume

Primary workflows

Submit source Analyze quality Explain finding Review remediation

Concrete workflow / priced call

Review supplied source without cloning a repository

The request, exact tool-call payload, returned output, and usage receipt are shown below.

Request

“Find the low-effort quality problems in this parser.”

Execution

Tool call payload

{
  "tool": "analyze_inline_sources",
  "arguments": {
    "files": [
      {
        "path": "src/parser.ts",
        "content": "export function parse(raw: string) { return JSON.parse(raw); }\n"
      }
    ],
    "lowHangingFruitOnly": true,
    "maxFindings": 10
  }
}

Analyzes only the supplied source payload and returns a bounded list of structured findings.

Output

Representative contract excerpt

{
  "contract": "codequality.inline-analysis.v1",
  "filesAnalyzed": 1,
  "findingCount": 1,
  "findings": [
    {
      "path": "src/parser.ts",
      "category": "error-handling",
      "severity": "medium"
    }
  ]
}

Usage rating

At runtime

Recorded on the operation receipt

The completed analysis receives a measured receipt. Allowance quantities remain unpublished until the fully allocated rate card is frozen.