Repository-aware MCP server

Both starter kits now include a local Model Context Protocol server for compatible coding assistants. The server uses the current checkout as its source of truth, helping agents discover the application before they plan or review a change.

Repository-aware context

The server exposes 19 read-only tools for:

• inspecting the application architecture, key package versions, security guardrails and package scripts
• discovering, searching and reading existing UI and feature components
• discovering, searching and reading routes, configuration, hooks, core libraries, Zod schemas, tRPC source and shared types
• listing, searching and reading local documentation
• inspecting the current ORM schema, fields, constraints, checked-in migrations and migration metadata
• retrieving the correct database workflow for schema changes, production migrations, prototyping and data inspection

Component and implementation lists are capped at 250 entries and searches at 50 matches. Limited tools report whether the cap was reached in their machine-readable result metadata so a client can narrow the request.

Project, database and documentation resources are available alongside guided prompts for feature planning and change review. Server-level instructions also tell compatible clients to discover the project, search before reading, inspect existing components and request the ORM-specific database workflow. Tool calls include both text output for broad compatibility and a machine-readable structured result. Every tool publishes and validates the shared structured-result output schema.

ORM-specific adapters

Pro Prisma reads prisma/schema.prisma, including field and model-level attributes, and the checked-in Prisma migration directories. Pro Drizzle reads the TypeScript schema, including field database names, nullability, defaults, keys and references, then parses its enums, indexes and constraints and lists the checked-in SQL migrations.

The database workflow tool returns commands for the selected kit rather than presenting a generic migration sequence.

Local and read-only

The Achromatic server runs locally over stdio. Its MCP tools do not connect to the database, execute package scripts, change source files, access environment files or make network requests. Repository reads are constrained to known documentation, component, implementation, schema and migration paths. Implementation reads are limited to app/, config/, hooks/, lib/, schemas/, trpc/, types/ and selected root entry points such as proxy.ts. Real-path containment, symbolic-link rejection and file-size limits protect the local file boundary. The startup command only writes compiled output to the ignored dist/ directory.

Provider-hosted MCP servers for services such as Stripe, Vercel or Linear remain separate, optional integrations with their own authorization.

Set up

Install the starter kit dependencies:

npm install

The included .mcp.json runs npm run mcp:start for Claude Code. The documentation includes the equivalent project setup for Cursor, Visual Studio Code and Codex. The start command compiles the server before connecting over stdio, preventing stale generated output.

Read the setup and tool reference for Pro Prisma or Pro Drizzle.

Verification

The MCP adapters and server contracts are covered by focused tests in both repositories. Each suite also launches the documented npm run mcp:start command and connects a real stdio client to verify tool, resource, prompt and project discovery through the compiled entry point.

Existing applications can ignore this optional integration without changing their runtime. Adopting it requires the local MCP server files and SDK development dependency, but no database migration or production service.