Skip to main content
Glama
devqxi

Pub.dev MCP Server

by devqxi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Pub.dev MCP Server

No user-submitted related servers found.

    Related Servers

    • Flutter Package MCP Server

      OrtakProje-1
      A
      license
      A
      quality
      D
      maintenance
      Integrates the Pub.dev API with AI assistants to provide real-time Flutter package information, documentation, and trend analysis. It enables users to search for packages, compare versions, and evaluate quality scores through natural language commands.
      6
      MIT

    • package-registry-mcp

      mikeysrecipes
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and retrieve detailed package information from multiple package registries (NPM, crates.io, NuGet, PyPI, Go).
      2,520 npm
      MIT

    • mcp-pub-dev

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching pub.dev for Dart and Flutter packages by keyword, returning matching package names and pagination URLs.
      17 npm
      MIT

    • flutter-docs-mcp

      KEEPEE
      A
      license
      A
      quality
      B
      maintenance
      Gives AI coding agents live, cached access to current Flutter, Dart SDK and pub.dev documentation returned as clean markdown, resolving class names, identifiers and packages on demand instead of relying on a model's memory. Also provides ranked name search over thousands of classes and a politeness layer with robots.txt compliance, throttling, conditional GETs and request budgets.
      6
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    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).

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources