Pub.dev MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_package_infoB | Get detailed information about a Dart/Flutter package from pub.dev |
| check_package_updatesC | Check for updates to a specific package or compare versions |
| get_package_versionsC | Get all available versions of a package with their release dates |
| get_documentation_changesC | Get documentation content and detect changes for a package |
| compare_package_versionsC | Compare two versions of a package and show differences |
| search_packagesB | Search for packages on pub.dev with filters |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: checking updates, comparing versions, getting documentation changes, retrieving package info, listing versions, and searching packages. The descriptions make it easy to differentiate between tools like 'check_package_updates' (for update status) and 'compare_package_versions' (for version differences).
All tool names follow a consistent verb_noun pattern with snake_case, such as 'check_package_updates', 'get_package_info', and 'search_packages'. This uniformity makes the tool set predictable and easy to navigate without any deviations in naming conventions.
With 6 tools, the server is well-scoped for its purpose of interacting with pub.dev packages. Each tool serves a specific function in package management, from discovery to version analysis, without feeling too sparse or overloaded. This count aligns with typical MCP server ranges for focused domains.
The tool set covers core workflows for package discovery, information retrieval, and version analysis effectively. Minor gaps exist, such as the lack of tools for publishing packages or managing dependencies, but agents can still perform essential tasks like searching, comparing, and monitoring updates without significant hindrance.