Carrick
Maps your entire TypeScript codebase across services and repositories, giving AI agents full context on existing types, routes, and function behaviours before they write duplicate or breaking code.
- Category
- Developer Tools
- Primary Subcategory
- Developer Docs & Reference Search
View in the Claude registryIntegration details
Description
Coding agents in multi-service codebases routinely rebuild existing helpers, trust stale type definitions, and modify API contracts without knowing who consumes them. Carrick solves this by indexing your entire TypeScript ecosystem across service and repository boundaries. By integrating deeply with the TypeScript compiler, Carrick traces every route, type, and cross-service call while recording function behaviour so agents search by intent rather than name. Delivered via MCP for AI agents and LSP for IDEs, Carrick ensures models see existing endpoints and utilities before generating new code. The scanner is source-available and runs from your CLI or CI pipeline.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Primary Subcategory
- Developer Docs & Reference Search
- Secondary Subcategories
- None listed
- Brand
- Carrick
- Access
- Account required
- First tracked
- 2026-09-28
- Tool count
- 17
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like
Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competing in Claude Developer Docs & Reference Search
View Category17 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Carrick alternatives on Claude?
As of 2026-09-29, Carrick competes with Microsoft Learn, GraphOS MCP Tools, Exa, Context7, AWS MCP, Stripe, Vercel, Wix, Autodesk Product Help, MDN, pg-aiguide, Stack Overflow, Vuetify MCP, ADITUS Developer Portal MCP, Agentic Atlas, commercetools Knowledge, Compiler Explorer, Devart Learn, Ezoic Setup, GameAnalytics Documentation, GitHits, HtAG Documentation, Infobip Documentation, LX Connect für Lexware, Mailgun Docs MCP, MercadoLibre, Pantavisor Docs, ReactVision: ViroReact MCP, Sabre Developer Hub MCP Server, Seam, Sinch Build Docs, Soracom Knowledge, SourcePRD, Tailor, TALON Knowledge, Theneo in Claude Developer Docs & Reference Search, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.