Search Dart & Flutter Packages (pub.dev)
pubdev/search-packages
Searches pub.dev for Dart and Flutter packages and returns a page of ten package names, in relevance order or sorted by likes, pub points, last update or creation. Supports pub.dev search syntax such as sdk:flutter, topic:http and publisher:dart.dev. Names only: follow up with package info or score. Data from pub.dev, https://pub.dev, modified by Eden Engine (fields renamed and reduced); not an official pub.dev or Google product.
Price
$0.0026 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Package data from pub.dev, https://pub.dev, the package repository for Dart and Flutter, fetched through its public API. Modified by Eden Engine: fields renamed and reduced (the other versions' pubspecs and the legacy author field are dropped, and versions are summarised to one line each) and served by Eden Engine; this is not an official pub.dev or Google product.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "pubdev/search-packages" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "pubdev/search-packages" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "pubdev/search-packages", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "pubdev/search-packages", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0026 |
- Updated
- Oct 27, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"query"
],
"properties": {
"page": {
"type": "integer",
"default": 1,
"maximum": 10,
"minimum": 1,
"description": "Page of ten results, 1 to 10. Defaults to 1."
},
"sort": {
"enum": [
"like",
"points",
"updated",
"created"
],
"type": "string",
"description": "Order of results: like (most liked), points (most pub points), updated (latest release) or created (newest package). Leave out for pub.dev's default relevance order."
},
"query": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Search text, with optional pub.dev filters such as sdk:flutter, platform:web, topic:http or publisher:dart.dev. For example http client or sdk:flutter topic:http."
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"package_names",
"next_page"
],
"properties": {
"next_page": {
"type": [
"integer",
"null"
],
"description": "Number of the next page, or null on the last page."
},
"package_names": {
"type": "array",
"items": {
"type": "string",
"description": "A package name."
},
"description": "Package names on this page, in rank order."
}
},
"description": "One page of search results.",
"additionalProperties": true
}