Carrick indexes every TypeScript service in your GitHub org and hands that index to your AI coding agent over MCP.

Agents working across many repos burn most of their context grepping, guessing, and rebuilding code that already exists somewhere else in the org. Carrick replaces that with a precise lookup. Ask "where do we deduplicate users by email" and get back a function, file, and line number instead of a 50,000-token rake through source.

## What you can do with it

- **Find code by what it does.** Search for "verifies a webhook signature" and get the function back, even when its name says nothing about webhooks.
- **Call other services with real types.** Look up an endpoint's actual request and response shapes instead of guessing the JSON.
- **Catch contract drift before it ships.** Carrick flags type mismatches, changed routes, wrong HTTP verbs, and dependency-version conflicts between services.

## Connect your agent

The MCP endpoint is `https://api.carrick.tools/mcp`. Claude Code, Cursor, Windsurf, and Codex all connect over HTTP.

```bash
claude mcp add --transport http carrick https://api.carrick.tools/mcp
```

Sign in once in your browser when prompted, and your agent is connected. Carrick is read-only: every tool call is a query against the index. See [Connecting your agent](/connecting-your-agent) for other clients.

## In CI

The Carrick GitHub Action keeps your org's index current on every push, and comments contract-drift findings on your pull requests. See [PR comments](/pr-output).

## Next steps

- [Quickstart](/quickstart) sets up Carrick end to end: sign in, add the action, connect your agent, first scan.
- [What Carrick covers](/coverage) lists what a repo needs to scan cleanly and what falls outside scope.
- [MCP tools](/mcp-tools) is the reference for every tool the server exposes.