mapbox-docsofficial
A
licenseA
qualityC
maintenanceProvides AI assistants with instant access to Mapbox documentation and reference materials through tools and resources, with no Mapbox access token required.
3
141 npm
1
MIT
mapicgc-mcp
Officialby OpenICGC
Related Servers
Alternatives to mapicgc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with Mapbox developer APIs for style management, token management, and local processing tasks like GeoJSON preview and coordinate conversion.23959 npm61MIT
- AlicenseAqualityAmaintenanceEnables AI agents to validate, inspect, render, and compare MapLibre map styles locally, and to show interactive maps to users in supporting chat apps.1102MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI models to fetch GitHub repository information, read file contents, and search local documentation.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access Mapbox location services for geocoding, POI search, multi-modal routing, travel time analysis, isochrones, map matching, and interactive/static map rendering through natural language.5,064 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search API documentation, retrieve endpoint details, get SDK snippets, and check changelogs from an OpenAPI spec.771 npm3MIT
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation4/5
Each tool targets a distinct documentation need (changelog, onboarding, keyword search, exact API lookup, topic examples, live style config). The only mild overlaps are get_started vs get_example (both return sample code) and search_docs vs get_api (both retrieve docs), but the descriptions clearly frame when to use each (exact name vs keyword, first-step vs full example).
Naming Consistency5/5
All six tools follow a consistent snake_case verb_noun pattern (get_changelog, get_started, get_api, get_example, search_docs, list_styles). Verbs are used meaningfully: get_ for retrieval, search_ for querying, list_ for enumerating.
Tool Count5/5
Six tools is a well-scoped set for a library documentation/assistant server. Each tool covers a distinct entry point (onboarding, search, API ref, examples, styles, changelog) with no filler.
Completeness4/5
The surface covers the main lifecycle of using a mapping library: getting started, finding docs, exact API reference, runnable examples, live style/terrain config, and version history. Minor gaps exist (e.g., no way to list available example topics or API symbols without guessing), but agents can work around this via search_docs.
Maintenance
ActivityMaintained
ResponsivenessNo issues