tsconfig-inheritance-flattener-mcp

Resolves TypeScript config inheritance chains and returns effective compiler options

Your AI agent readstsconfig.json. It has no idea what it actually means.

MCP server that resolves the full TypeScript config inheritance chain and returns theeffective compiler optionsthat actually apply — including everything inherited from extended base configs, monorepo packages, andnode_modulespresets.

Your agent readstsconfig.jsonand sees:

{ "extends": "@tsconfig/strictest", "compilerOptions": { "paths": { "@/": ["./src/"] } } }

It has no idea that@tsconfig/strictestsetsstrict: true,noUncheckedIndexedAccess: true,exactOptionalPropertyTypes: true. It doesn't know thatbaseUrlis defined two levels up in your monorepo base config. So it:

- Suggests code that would failnoUncheckedIndexedAccess
- Gets confused about what@/resolves to
- Doesn't know yourtargetisES2022, notES5
- Gives wrong answers about module resolution

The TypeScript compiler API already resolves all of this. This MCP just exposes it.

Resolves the fullextendschain and returns the merged compiler options that actually apply to a giventsconfig.json. Shows the inheritance chain, all merged options (with enums as readable strings, not magic numbers), and include/exclude patterns.

Effective TypeScript Configuration Config: /project/apps/web/tsconfig.json Inheritance chain: /project/apps/web/tsconfig.json → /project/tsconfig.base.json → node_modules/@tsconfig/strictest/tsconfig.json Compiler Options (merged): target: "ES2022" module: "NodeNext" moduleResolution: "NodeNext" strict: true noUncheckedIndexedAccess: true exactOptionalPropertyTypes: true baseUrl: "/project" paths: { "@/": ["apps/web/src/"] }

Maps a TypeScript path alias (e.g.@/hooks/useAuth) to its physical file location on disk, using the resolvedpathsandbaseUrlfrom the tsconfig. Returns all existing candidates with extension probing.

Alias Resolution: @/hooks/useAuth Config: /project/apps/web/tsconfig.json Base URL: /project Resolved physical paths: /project/apps/web/src/hooks/useAuth.ts ✓ exists

Inspects thereferencesarray in a roottsconfig.jsonand validates that each referenced package hascomposite: true. Catches broken cross-package dependencies in TypeScript monorepos before they cause silent build failures.

Project References Analysis Config: /project/tsconfig.json References found: 2 [✓] packages/shared → /project/packages/shared/tsconfig.json [✗ NOT FOUND] packages/deprecated → /project/packages/deprecated/tsconfig.json Violations: ✗ packages/shared is referenced but does not have composite: true Fix: add "composite": true to packages/shared/tsconfig.json

Agent is helping debug a TypeScript error and asks:

"What compiler options are actually active in this project?"

Without this MCP, the agent guesses based on what it sees intsconfig.json. With it:

get_effective_compiler_options("/project/apps/web/tsconfig.json") → strict: true, noUncheckedIndexedAccess: true, target: "ES2022", module: "NodeNext"

Now the agent knows exactly whyarr[0]has typestring | undefinedand not juststring. No more wrong suggestions.

{ "mcpServers": { "tsconfig-flattener": { "command": "npx", "args": ["-y", "tsconfig-inheritance-flattener-mcp"] } } }

"What compiler options actually apply to/project/apps/web/tsconfig.json? It extends a monorepo base and @tsconfig/strictest."

"Where does@/components/Buttonresolve to on disk?"

"Are the project references in my root tsconfig valid? Do all referenced packages have composite: true?"

- ast-impact-mapper-mcp— for code→test correlation
- release-readiness-triage-mcp— for CI triage

- npm:npmjs.com/package/tsconfig-inheritance-flattener-mcp
- GitHub:github.com/vola-trebla/tsconfig-inheritance-flattener-mcp

Provides AI assistants with a comprehensive, one-time analysis for complete codebase context and understanding.