Skip to main content
Glama
mapbox-docs

mapbox-docs

Official
by mapbox

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_document_toolA

Fetch the full content of a specific Mapbox documentation page by URL. Use this after search_mapbox_docs_tool to follow a link from the search results and retrieve the complete page content. For fetching multiple pages at once, use batch_get_documents_tool instead.

batch_get_documents_toolA

Fetch the full content of multiple Mapbox documentation pages in a single call (max 20). More efficient than calling get_document_tool multiple times. Returns an array of results — failed pages include an error message rather than failing the whole batch.

search_mapbox_docs_toolA

Search Mapbox documentation by keyword or natural language query. Searches across API reference, GL JS, Help Center, Style Spec, Studio, Search JS, iOS/Android Maps and Navigation SDKs, and Tilesets. Returns ranked results with titles, URLs, and descriptions. Use get_document_tool to fetch the full content of a result page.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Mapbox Style Specification GuideMapbox GL JS style specification reference for layer types, paint/layout properties, and Streets v8 source layers
Mapbox Streets v8 Fields ReferenceComplete field definitions for all Mapbox Streets v8 source layers including available values for each field. Use this to understand what fields and values are available when filtering or styling map features.
Mapbox Token Scopes ReferenceReference guide for Mapbox access token scopes and their permissions. Use this to understand what each scope allows and which scopes are needed for different operations.
Mapbox Layer Type MappingMapping of Mapbox Streets v8 source layers to compatible Mapbox GL JS layer types. Use this to understand which layer types (fill, line, symbol, etc.) work with which source layers.
Mapbox Documentation[DEPRECATED: Use granular resources like resource://mapbox-api-reference instead] Latest official Mapbox documentation, APIs, SDKs, and developer resources. Always up-to-date comprehensive coverage of all current Mapbox services.
Mapbox API ReferenceMapbox REST API reference index organized by service (Maps, Navigation, Search, Accounts). Lists all API endpoints with links to detailed reference pages covering parameters, rate limits, authentication, and response formats (Geocoding, Directions, Static Images, Tilequery, Matrix, Isochrone, Optimization, Styles, Uploads, Datasets, and more).
Mapbox SDK DocumentationMapbox GL JS documentation index: guides for getting started, adding data, globe/projections, indoor mapping, gestures, styling layers, and migration. Also includes links to API reference and code examples. For mobile/native SDKs (iOS, Android, Flutter), use resource://mapbox-reference to discover their documentation URLs.
Mapbox GuidesMapbox Help Center documentation: troubleshooting guides, how-to tutorials, glossary, account and billing setup, and walkthroughs for common developer tasks. Use this for conceptual guidance and step-by-step instructions.
Mapbox ExamplesMapbox interactive API playgrounds, demo applications, and code examples. Includes playground URLs for Directions, Search Box, Static Images, Isochrone, Matrix APIs, and demo apps for real estate, store locator, etc.
Mapbox ReferenceComplete catalog of all Mapbox products and documentation. Lists every product section (Maps SDKs, Navigation APIs, Search APIs, Studio, Style Spec, Tilesets, Data products, Help Center, Atlas, Unity, etc.) with links to each product's own llms.txt index. Use this to discover what documentation exists and find the right URLs to fetch full docs.

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: search to find pages, get_document_tool to fetch one page, batch_get_documents_tool to fetch many. The descriptions explicitly cross-reference each other and state when to prefer one over the other, leaving no real ambiguity.

Naming Consistency4/5

All names are snake_case and end in the same _tool suffix, following a verb_object pattern (get_document, search_mapbox_docs). The only deviation is the 'batch_' prefix on batch_get_documents_tool, which is a minor and readable variation.

Tool Count4/5

Three tools is on the thin side, but it maps cleanly to the narrow purpose of a documentation search-and-retrieve server. Batch fetching earns its place alongside the single-fetch tool, so nothing feels redundant.

Completeness4/5

Search plus single and batch retrieval covers the core documentation workflow end to end, including partial-failure handling in the batch call. Minor gaps exist (no explicit pagination or listing/index tool for browsing all docs), but agents can work around these via search.

Maintenance

ActivityActive
ResponsivenessLimited data