Code Intelligence MCP Server

Scaffold State #

Two phases have shipped. No tool implementations exist yet; that work starts at AUT-35.

Phase 1 — Scaffold Shipped (AUT-34) #

Delivered 2026-04-28 as AUT-34. Server structure copied from apps/github-mcp/ then stripped of GitHub-specific dependencies.

• Copied from github-mcp: tsconfig*.json, package.json scripts, Dockerfile (later flipped to repo-root build context), src/server.ts, src/index.ts, src/lib/telemetry.ts, src/lib/cache.ts.
• Dropped (no GitHub API calls): github.ts, gitignore.ts, ignore-factory.ts, read-file-fetch.ts, search-code-fetch.ts, rate-limit.ts, binary-detect.ts, platform-excludes.ts, pipeline.ts, secrets.ts, size-filter.ts.
• Added: empty src/tools/ directory, compose service code-intel-mcp on amtp_net at port 8091:8091, CI workflow .github/workflows/code-intel-mcp-ci-cd.yml, .env.example additions (CODE_INTEL_MCP_PORT=8091).

Acceptance (met): server starts, /healthz returns {"status":"ok","valkey":"up"}, tools/list returns an empty array.

Phase 1.5 — Extract @amtp/mcp-lib Shipped (2026-04-29) #

After Phase 1, logger.ts, health.ts, and otel.ts existed identically in both apps/github-mcp/src/lib/ and apps/code-intel-mcp/src/lib/. This phase deduplicated them before drift could set in.

• Repo became an npm workspace: root package.json declares workspaces: ["packages/*", "apps/code-intel-mcp", "apps/github-mcp"]. Per-app lockfiles deleted; root package-lock.json is the single source of truth.
• New package packages/mcp-lib/ (@amtp/mcp-lib) owns the three shared modules. Subpath exports: @amtp/mcp-lib/logger, @amtp/mcp-lib/health, @amtp/mcp-lib/otel.
• App-side wrappers: logger.ts is a direct re-export; otel.ts calls initOtel(serviceName) with the app-specific name (amtp-code-intel-mcp); health.ts calls createHealthzHandler(redis) closing over the app-local ioredis singleton.
• cache.ts and telemetry.ts stay app-local — both carry app-specific surface that does not belong in shared infra.
• Both Dockerfiles switch build context to repo root so they can COPY packages/mcp-lib/ alongside the app.

@amtp/mcp-lib Workspace Package #

Located at packages/mcp-lib/. Shared by both github-mcp and code-intel-mcp.

AUT-3 Task Plan #

Eight tasks with a dependency tree rooted at ast.summarize_file. Phases 1 and 1.5 are shipped. Phase 2 design questions must be answered before AUT-35 code lands.

The five tools form a dependency tree rooted at summarize_file. Everything else is either a specialization (routes/components/selectors operate on the same parsed AST) or an extension (find_symbol indexes summaries; benchmark measures them).

Phase 2 Design Questions #

1. WASM vs native tree-sitter #

web-tree-sitter (WASM) = no C compiler on self-hosted runners, identical behaviour everywhere. node-tree-sitter (native bindings, node-gyp) = faster, but adds a compile step to CI.

Default: WASM. Defer the performance decision to AUT-42. Only switch to native if the benchmark proves WASM is the bottleneck.

2. Output JSON shape for ast.summarize_file #

The downstream agents (Repo Crawler, Test Case Generator) are not built yet, but they will be coupled to this shape. Pick it now, document it in SCHEMA.md, and treat it as a contract. See the Output Schema Proposal below.

3. Cache key strategy #

github-mcp caches by (repo, resolved_sha, args_hash). AST output is a pure function of (content, language). Cache by sha256(content) + ":" + language + ":" + TOOL_VERSION. No GitHub ref involved. Validate with team before implementing.

Planned Tools #

Output Schema Proposal (ast.summarize_file) #

Proposed top-level shape from apps/code-intel-mcp/PLAN.md § Phase 2. Must be ratified before AUT-37 lands. Body-stripping rule: keep node header (function signature, class header, interface body), drop body statements. This is where the ~85% token reduction comes from.

{
  "path": "src/components/Button.tsx",
  "language": "tsx",
  "imports": [{ "source": "react", "names": ["useState"] }],
  "exports": [{ "name": "Button", "kind": "function", "default": false }],
  "declarations": [
    {
      "kind": "function",   // function | class | interface | type | const | enum
      "name": "Button",
      "signature": "function Button(props: ButtonProps): JSX.Element",
      "exported": true,
      "async": false,
      "line": 12
    }
  ],
  "jsx_root": true,         // true for TSX/JSX files
  "errors": []              // parser recovery notes
}

Design constraint: a 300-line TS file (~8,000 chars) must produce a summary of at most ~1,200 chars. If the schema grows past that, bodies are leaking in.

Config Reference #

File Map #

For the shared library, see @amtp/mcp-lib above. For the CI workflow, see Code Intel MCP Workflow.