Asynthetic
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP mode port (Streamable HTTP at /mcp, legacy SSE at /sse + /messages, health at /) | |
| SUPABASE_URL | No | PostgreSQL URL for Supabase backend | |
| SUPABASE_ANON_KEY | No | Anon key for Supabase backend | |
| MIGRATION_DATA_DIR | No | Overrides the local maps directory | |
| SUPABASE_SERVICE_ROLE_KEY | No | Service role key needed by npm run seed only |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_migrationA | Returns the verified migration map for upgrading a package between two versions: ordered breaking changes with before/after code, deprecations, source-citation URLs, and a last_verified date. Accepts concrete versions or SemVer ranges (e.g. "^14.2.0", "~14.1.0", "15.x"); non-exact lookups resolve to the covering map and disclose how via match_type/resolved_via/match_note. If found=false, no verified data exists — do not guess. |
| get_breaking_changesA | Returns the breaking changes introduced when upgrading TO the given version of a package (matched by major version against curated migration maps), with source citations and last_verified dates. Accepts concrete versions or SemVer ranges ("15", "^15.0.0", "15.x"); resolution is disclosed via match_type/resolved_via. If found=false, no verified data exists — do not guess. |
| list_available_mapsA | Lists every migration map in the store: package, ecosystem, from_version, to_version, status (draft/verified/stale), last_verified. Optional filters: ecosystem, package. Use this to discover coverage before calling get_migration. |
| check_peer_compatibilityA | Static SemVer check of two known package versions against curated compatible_with peer data from migration maps. Purely declarative — no filesystem access or project inspection (that is the scope of the separate, unimplemented check_compatibility). Returns compatible: true | false | "unknown". Treat "unknown" as absence of curated data, never as evidence of incompatibility. |
| check_compatibilityA | PLANNED: project-aware compatibility analysis. Currently returns implemented=false and no data. Do not infer compatibility (or incompatibility) from this response. For a static SemVer check between two known package versions, use check_peer_compatibility instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing maps, retrieving migration maps, getting breaking changes, static peer compatibility check, and a planned project-aware check. Descriptions provide clear boundaries and guidance to avoid confusion.
All tools follow a consistent verb_noun pattern with snake_case (check_, get_, list_). The naming is predictable and descriptive, with no mixed conventions.
With 5 tools covering migration map queries, static compatibility, and breaking changes, the count is well-scoped for the domain. Each tool earns its place without being excessive or insufficient.
The set covers core operations for package migration analysis: listing, retrieving maps, and checking static compatibility. The unimplemented check_compatibility indicates a planned feature for project-aware analysis, which is a minor gap, but the current surface is functional for its stated scope.