AI coding agents kept hallucinating package names, using API signatures that changed versions ago, or recommending packages that are basically abandoned. What finally got me: Claude Code grepping my local pub cache on disk instead of just looking things up, burning tokens crawling through cached source.
So I built dart-pubdev-explorer (pub.dev package: dart_pubdev_mcp), an MCP server that gives agents direct, structured access to pub.dev instead of digging through your filesystem or guessing from training data.
It can:
- search & compare packages (score, platform support, maintenance)
- browse a package’s real public API and pull exact source (by symbol or line range)
- check security advisories against the version you actually have resolved
- diff changelogs/APIs between versions before you upgrade
- read Dart SDK / Flutter framework source too (dart:core, package:flutter, …)
Quick note on how this differs from the official Dart MCP server (dart mcp-server): that one has a general pub_dev_search tool as part of a much bigger toolset (running apps, analysis, DTD, etc). This one only does package research, but goes deeper: symbol-level API browsing, exact source reads, version diffing, side-by-side comparisons, with an on-disk cache built for that kind of repeated digging. They’re complementary, I run both.
Install:
dart install dart_pubdev_mcp
I’ve been running it with both Claude Code and Antigravity. Works fine in either since it’s just a plain stdio MCP server.
pub.dev: dart_pubdev_mcp | Dart package
Source/issues: GitHub - PhilippHGerber/agentic_dart · GitHub
Curious what people think, especially whether some of the tools are overkill and others are missing something obvious.