Augments MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token for higher rate limits when fetching examples and documentation. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_api_contextA | RECOMMENDED: Get precise API signatures, parameters, return types, prose documentation, and code examples for any npm package. Handles natural language like "react useEffect cleanup" or "how to use zustand". Always try this first. |
| search_apisA | Search for APIs across multiple frameworks when you don't know the exact name. Supports concept search like 'state management' which matches useState, createStore, atom, etc. |
| get_version_infoA | Get version info, available versions, and breaking change detection for any npm package. Now includes actual breaking changes and new features from changelogs. |
| get_migration_guideA | Get a detailed migration guide between package versions. Returns breaking changes, new features, deprecations, type diffs, and official migration docs. |
| diagnose_errorA | Diagnose an error message or stack trace. Matches against known error patterns, searches GitHub issues, and finds relevant documentation. |
| compare_packagesA | Compare npm packages side-by-side: downloads, bundle size, dependencies, GitHub stars, exported APIs. Great for choosing between alternatives. |
| scan_project_depsC | Scan project dependencies for outdated packages, major updates, deprecated packages, and security advisories. Reads package.json. |
| diagnosticsA | Get server health information: version, uptime, memory usage, cache statistics, and Node.js version. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| frameworks |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: comparison, error diagnosis, server health, API details, migration guides, version info, dependency scanning, and API search. No overlapping functionality.
Most tools use a consistent verb_noun pattern (compare_packages, diagnose_error, get_api_context, get_migration_guide, get_version_info, scan_project_deps, search_apis). 'diagnostics' is a noun-only outlier, slightly breaking consistency.
Eight tools is well-scoped for the domain of npm package analysis and development assistance. Each tool covers a key area without redundancy.
The tool surface covers all major development needs: package comparison, error diagnosis, API exploration, version management, migration planning, project auditing, and concept search. No obvious gaps.