Augments

Retrieves live npm package documentation, type definitions, and code examples by intercepting Claude queries and resolving them against the npm registry and augments.dev backend. Uses MCP (Model Context Protocol) as the integration layer to transparently inject documentation into Claude's context without requiring manual context-switching. Supports 24 curated frameworks (React, Vue, Svelte, Angular, Express, Fastify, Hono, Prisma, Drizzle, Zod, tRPC, TanStack Query, SWR, Zustand, Jotai, Redux, React Hook Form, Framer Motion, Supabase, Vitest, Playwright, Next.js, React DOM, Solid) with enhanced formatting and any npm package via fallback resolution.

Detects the intent behind a user's query (categorized as: howto, reference, or balanced) and reformats retrieved documentation and type signatures accordingly. The mechanism for intent detection is unknown (could be rule-based pattern matching, lightweight ML classifier, or delegated to Claude), but the output formatting adapts to whether the user seeks procedural guidance, API reference material, or a balanced combination. This enables context-aware presentation of the same underlying documentation.

Enables documentation enhancement with minimal setup friction: a single `claude mcp add` command installs the MCP server, and subsequent Claude queries automatically benefit from live documentation retrieval. No configuration files, environment variables, or manual server management required. Setup time is approximately 2 minutes, and time to first value is immediate (next Claude query about an npm package will use Augments).

Extracts TypeScript type definitions from two sources: DefinitelyTyped (@types/* packages) and bundled .d.ts files within npm packages themselves. The extraction mechanism queries the npm registry and resolves type definitions, then formats them for display in Claude's context. This provides accurate, up-to-date type information without relying on Claude's training data, which may be outdated or incomplete for newer package versions.

Provides enhanced documentation retrieval for 24 pre-curated frameworks (React, Vue, Svelte, Angular, Express, Fastify, Hono, Prisma, Drizzle, Zod, tRPC, TanStack Query, SWR, Zustand, Jotai, Redux, React Hook Form, Framer Motion, Supabase, Vitest, Playwright, Next.js, React DOM, Solid) with specialized formatting and potentially additional context beyond standard npm registry metadata. The curation likely includes hand-selected documentation sources, common patterns, and framework-specific examples. Fallback to standard npm registry retrieval for non-curated packages.

Retrieves working code examples for npm packages, with the source of examples being unknown (could be curated database, README parsing, or extracted from package repositories). Examples are formatted and returned alongside type signatures and documentation to provide practical usage guidance. The retrieval mechanism integrates with the npm registry and augments.dev backend to surface relevant examples for the queried package.

Provides a client-side MCP server that runs locally via Node.js (installed via `npx -y @augmnt-sh/augments-mcp-server`) and integrates with Claude Desktop via the `claude mcp add` command. The server lifecycle is managed by Claude Desktop; once installed, it automatically intercepts relevant queries and routes them to augments.dev backend for documentation retrieval. Uninstallation and updates are managed through standard MCP server commands.

Resolves npm package names and versions against the public npm registry, supporting implicit package name extraction from conversational context. The resolution mechanism queries the npm registry API to identify the correct package, retrieve metadata, and determine available versions. Behavior for version specifiers (e.g., 'react@18.2.0') is unknown; system may default to latest version or support explicit version requests.

Manages documentation retrieval and formatting to fit within Claude's context window constraints, synthesizing type signatures, prose documentation, and code examples into a coherent response that doesn't exceed available context. The synthesis mechanism is unknown (could be automatic truncation, summarization, or prioritization), but the output is designed to maximize relevance within context limits. Multiple package queries in a single conversation will consume context progressively.

Intercepts Claude queries transparently (without explicit user commands) and routes relevant queries to the augments.dev backend for documentation retrieval. The interception mechanism is unknown (could be keyword-based pattern matching, intent classification, or heuristic-based routing), but the goal is to automatically enhance Claude's responses with live documentation without requiring users to invoke a special command or syntax. Non-relevant queries pass through to Claude without interception.

Reduces Claude's tendency to hallucinate about npm package APIs by providing live, accurate documentation from the npm registry instead of relying on training data. When a user queries Claude about a package API, Augments retrieves current documentation, type signatures, and examples, which Claude then synthesizes into a response. This approach eliminates hallucination risk for documented APIs and ensures responses reflect the current package state, not outdated training data.