CodeIntel MCP

Live code navigation and language-server intelligence

CodeIntel MCP keeps a tenant-scoped repository index and warm language-server sessions for symbol lookup, references, diagnostics, and code navigation 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

Keep a durable repository index and warm language-server sessions available for symbol lookup, references, diagnostics, and code navigation.

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 map reflects the retained revision and the capabilities of its language servers. It does not claim runtime coverage or semantic certainty beyond indexed source files.

Requires an authenticated, entitled account and a tenant-scoped retained repository. Repository identity and storage paths are resolved by hosted orchestration.

What you get

Navigate symbols and references across large repositories
Reuse warm language-server sessions between related calls
Keep repository indexing separate for each tenant

Core use case

Keep a durable repository index and warm language-server sessions available for symbol lookup, references, diagnostics, and code navigation.

Outcomes

Answer code-navigation questions without rebuilding the index on every call
Use language-server results alongside repository structure
Keep each tenant's repositories and sessions isolated

Primary workflows

Index repository Find symbols Trace references Inspect diagnostics

Concrete workflow / priced call

Map a retained codebase from its indexed structure

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

Request

“Show me the components, entry points, and relationships in this repository.”

Execution

Tool call payload

{
  "tool": "codeintel_hosted_map_v1",
  "arguments": {
    "freshness": "require-current",
    "scope": [
      "repository"
    ]
  }
}

Reads the tenant-scoped durable index and returns a bounded component and relationship map without rebuilding or uploading state on the read path.

Output

Representative contract excerpt

{
  "schema": "codeintel.hosted-map.v1",
  "status": "ready",
  "summary": {
    "files": 42,
    "objects": 318,
    "relationships": 704,
    "languages": [
      "typescript"
    ]
  },
  "freshness": {
    "status": "current"
  }
}

Usage rating

At runtime

Recorded on the operation receipt

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