Augments MCP Server

A next-generation framework documentation provider for Claude Code via Model Context Protocol (MCP). Returns types + prose + examples with context-aware formatting for any npm package — not just curated ones.

mcp-name: dev.augments/mcp

What's New in v7

Version 7.0 is the biggest upgrade yet — documentation-first search, 4 new tools, BM25 indexing, and production-grade reliability.

Quick Start

Claude Code

# Add the MCP server (runs locally via npx)

claude mcp add -s user augments -- npx -y @augmnt-sh/augments-mcp-server

Verify configuration

claude mcp list

Cursor

Add to your MCP config:

{

"mcpServers": { "augments": { "command": "npx", "args": ["-y", "@augmnt-sh/augments-mcp-server"] } } }

Environment Variables

Set GITHUB_TOKEN for higher GitHub API rate limits when fetching examples and documentation:

{

"mcpServers": { "augments": { "command": "npx", "args": ["-y", "@augmnt-sh/augments-mcp-server"], "env": { "GITHUB_TOKEN": "ghp_your_token_here" } } } }

Usage

# Get API context with prose + examples (recommended first tool)

@augments get_api_context query="useEffect cleanup" framework="react"

Natural language queries work great

@augments get_api_context query="how to use zustand middleware"

Search for APIs by concept (synonym-aware)

@augments search_apis query="state management"

Get version info with real breaking changes

@augments get_version_info framework="react" fromVersion="18" toVersion="19"

Migration guide between versions

@augments get_migration_guide package="next" fromVersion="14" toVersion="15"

Diagnose an error

@augments diagnose_error error="Objects are not valid as a React child" package="react"

Compare packages side-by-side

@augments compare_packages packages=["zod", "yup", "joi"]

Scan project dependencies

@augments scan_project_deps

Tools

Architecture

flowchart TD

A["Query: 'how to use useEffect cleanup'"] --> B

B["Intent Detection → howto Query Parser → react / useEffect"]

B --> C["Type Fetcher CDN racing · npm metadata · @types"] B --> D["Doc Fetcher GitHub API · BM25 search · 25 synonym clusters"] B --> E["Example Extractor GitHub docs · README fallback · Auto-discovery"]

C --> F["Type Parser Signatures · Parameters · Related types"] D --> G["Doc Search Engine BM25 indexing · Heading-based chunks · API boost"]

F --> H["Intent-Driven Formatter (howto) → Examples first, prose, brief signature → ~500-2000 tokens, 10KB max"] G --> H E --> H

Source Structure

src/

├── cli.ts # stdio entry point ├── server.ts # MCP server (8 tools + diagnostics) ├── core/ # Core modules │ ├── query-parser.ts # Parse natural language → framework + concept │ ├── type-fetcher.ts # Fetch .d.ts + README from npm/unpkg/jsdelivr │ ├── type-parser.ts # Parse TypeScript, extract signatures, synonym search │ ├── example-extractor.ts # Fetch examples from GitHub docs + auto-discovery │ ├── version-registry.ts # npm registry integration + changelog-backed diffs │ ├── doc-fetcher.ts # GitHub documentation fetcher │ ├── doc-search.ts # BM25 inverted index search engine │ ├── changelog-fetcher.ts # CHANGELOG.md + GitHub Releases parser │ ├── type-differ.ts # .d.ts diff between versions │ └── error-patterns.ts # Curated error pattern database ├── tools/v4/ # MCP tools │ ├── get-api-context.ts # Primary tool (types + docs + examples) │ ├── search-apis.ts # Cross-framework API search │ ├── get-version-info.ts # Version comparison │ ├── get-migration-guide.ts # Cross-version migration guides │ ├── diagnose-error.ts # Error diagnosis │ ├── compare-packages.ts # Package comparison │ └── scan-project-deps.ts # Dependency scanner └── utils/ ├── logger.ts # stderr logger └── lru-cache.ts # Generic LRU cache with stats

Key Features

Documentation-First Search (New in v7)

Queries like "prisma findMany with pagination" and "zustand create store with middleware" now return real documentation content. The BM25 search engine indexes docs fetched from GitHub by heading-based chunks, with API name boosting and synonym expansion.

Concept Synonyms

25 synonym clusters cover state, form, fetch, animation, routing, auth, cache, effect, middleware, pagination, validation, testing, streaming, error handling, database, layout, modal, table, upload, realtime, deployment, i18n, SSR, component, and context patterns. Bidirectional lookup means "usestate" expands to the "state" cluster.

Intent-Aware Formatting

Production Reliability (New in v7)

• Exponential backoff with jitter for npm registry retries, with 429 Retry-After support
• CDN circuit breaker — skips repeatedly failing CDN endpoints (3 failures / 5 min)
• GitHub rate limiting — tracks remaining quota, skips fetches when exhausted
• LRU caches with hit/miss statistics across all cache-using modules

Coverage

Any npm Package

Every npm package is supported out of the box — no curation or configuration needed. Augments resolves documentation automatically through four layers:

1. Documentation search — fetches real docs from GitHub repos, indexes with BM25
2. TypeScript types — bundled ("types" in package.json) or DefinitelyTyped (@types/*)
3. Auto-discovered docs — parses the npm repository field, finds the GitHub repo, probes docs/ directories
4. README fallback — extracts concept-relevant code blocks and prose from README.md

This means augments works with the entire npm ecosystem (~2.5M packages), not just a curated subset.

Enhanced Results for Popular Frameworks

22 frameworks have curated doc sources for richer examples: React, Next.js, Vue, Prisma, Zod, Supabase, TanStack Query, tRPC, React Hook Form, Framer Motion, Express, Zustand, Jotai, Drizzle, SWR, Vitest, Playwright, Fastify, Hono, Solid, Svelte, Angular, Redux

Barrel Export Handling

Special sub-module resolution for: React Hook Form, TanStack Query, Zustand, Jotai, tRPC, Drizzle ORM, Next.js

Local Development

# Clone and install

git clone https://github.com/augmentscode/augments-mcp-server.git cd augments-mcp-server npm install

Build with tsup

npm run build

Run locally

npm start

Watch mode

npm run dev

Run tests

npm test

Run e2e tests (real network calls)

npm run test:e2e

Type check

npm run type-check

How Augments Compares to Context7

Contributing

1. Fork the repository
2. Create a feature branch: git checkout -b feature/amazing-feature
3. Make your changes
4. Run tests: npm test
5. Submit a pull request

License

MIT License - see LICENSE for details.

Support

• GitHub Issues
• GitHub Discussions

---

Built for the Claude Code ecosystem | Version 7.0.0