01/ 06

This circle is your TypeScript compiler. It understands your system.

One index, three surfaces

Read indexed contracts in your editor, find existing code through your agent, and check changes on your pull request.

checkout/src/order.ts
const res = await fetch("/orders/summary")const total: number = body.total
orders-api returns total: string · 4 callers
VS Code Cursor Windsurf

In your editor

See an indexed counterpart, its contract, and the local file on the other side without leaving the editor.

What it resolves
search_by_intent 12 matches
get_endpoint_types req + res
check_compatibility 1 disagreement
get_service_graph 9 services
get_callers 4 consumers

In your agent

Code that already exists, found by what it does, the real shape of any endpoint, the service graph, and who breaks if it changes.

The MCP tools
carrick / scan 2 findings
carrick-cloud Bot
contract dispatchedAt is Date in orders-api and string in billing-service.
duplicate formatCarrierName() already exists in shared-utils.
34 endpoints and 19 cross-service calls indexed.

In your pull request

Contract risks, duplicated work and version drift across the indexed repos.

What the check reports
4.0FAQ

Common questions

Carrick reads your TypeScript source and builds one index of every service: its routes, the real request and response types, and a one-line description of what each function does. The index is built in CI on every merge, and the CLI builds a local index in your workspace. Your coding agent queries the hosted index over MCP, while the editor reads the local index for diagnostics, code lenses and go to definition.

Grep finds the name you guessed, while Carrick matches on what a function does. The agent can find an existing implementation even when it is named something else in another repo.

Yes. Carrick derives services from workspace manifests and shows the proposal during init. An existing carrick.json can specify service folders and shared source. Each service is indexed separately so Carrick can check the contracts between them.

Agents that support MCP can connect to Carrick, including Claude Code, Cursor, Windsurf and Codex. The editor extension is available from Visual Studio Marketplace and Open VSX, and other LSP clients can start the same server directly.

TypeScript source and an existing package or Deno manifest. Carrick prepares dependencies without running lifecycle scripts. Deno projects also need Deno on PATH; Carrick reads their configuration without a separate TypeScript config. The coverage guide lists supported runtime scopes and any dependency preparation your project needs.

Carrick reads source to build an index of route signatures, resolved types, dependencies and function descriptions. Access to that index is scoped to your workspace, and stored index data is encrypted at rest.

TypeScript today. Other languages will follow once the TypeScript tooling is where we want it.

Free for up to 10 repositories, no card needed. Above that it is €299 a month for up to 25 repositories, and a custom price beyond. Every plan is the whole product with unlimited queries. A limited number of teams can apply for three months free, then 50% off for the following twelve.

Direct support, usually the same day. Bug reports and feature requests go to the engineers who build Carrick, with no queue in between.

One index of your whole system. Every service, type and contract, served to agents over MCP and checked in CI.

Get started now Apply to get 3 months free Free for up to 10 repositories