CodeProfiler MCP

Codebase profiling plans and bounded analysis jobs

CodeProfiler MCP detects a repository's languages and project markers, builds a profiling plan, and runs bounded read-only probes through the hosted catalog.

Included with an active usage plan

Available through the hosted catalog for authenticated, entitled accounts. Calls count against the shared allowance on the account plan.

Compare usage plans

Why it exists

Detect a repository's stack, choose an appropriate profiling toolbox, and run bounded read-only probes in an isolated job.

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

Assessment recommends measurements; it does not prove a bottleneck. Approved profiling jobs remain bounded and read-only, and their tool output remains untrusted.

Requires an authenticated, entitled account and a bounded tenant-scoped source snapshot. The assessment operation is read-only and does not start an external profiler.

What you get

Choose profiling tools from the repository's actual stack
Separate quick inventory from deeper analysis jobs
Return tool output and failures in one structured result

Core use case

Detect a repository's stack, choose an appropriate profiling toolbox, and run bounded read-only probes in an isolated job.

Outcomes

Choose profiling tools from the detected project stack
Keep expensive analysis out of lightweight discovery calls
Return results and tool failures in one structured report

Primary workflows

Detect stack Build plan Run probes Review report

Concrete workflow / priced call

Build a bounded profiling plan before running probes

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

Request

“Assess this retained codebase and identify the measurements that fit the stated performance concern.”

Execution

Tool call payload

{
  "tool": "codeprofiler_hosted_assess_v1",
  "arguments": {
    "symptoms": [
      "Build latency increased after dependency changes"
    ],
    "scenario": "Representative build and startup path",
    "constraints": [
      "Do not access production data"
    ],
    "mode": "standard"
  }
}

Inspects a bounded retained source snapshot, detects the stack, and returns a measurement plan before any profiler job is dispatched.

Output

Representative contract excerpt

{
  "status": "ready",
  "inventory": {
    "languages": [
      "typescript"
    ]
  },
  "recommendedProfilers": [
    {
      "profiler": "scc",
      "availableForBoundedRun": true
    },
    {
      "profiler": "tokei",
      "availableForBoundedRun": true
    }
  ],
  "confidence": 0.9
}

Usage rating

At runtime

Recorded on the operation receipt

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