Mapbox Studio (BYOK)

Mapbox Studio (BYOK) — connector documentation

• MCP endpoint: https://byok-mapbox-studio.connectorbay.com/mcp
• REST API: POST https://byok-mapbox-studio.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-mapbox-studio.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Mapbox Studio Mapbox access token (secret token with the read and list scopes of the resources you want), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-mapbox-studio.connectorbay.com/health · Tool schemas: https://byok-mapbox-studio.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-mapbox-studio · agent@connectorbay.com

What Mapbox Studio (BYOK) is for

Mapbox Studio (BYOK) lets an AI assistant read your own Mapbox Studio data through the Mapbox Studio API with a key you supply (Mapbox access token (secret token with the read and list scopes of the resources you want)). Read-only: 11 tools (list_styles, get_style, list_datasets, get_dataset, list_dataset_features, get_dataset_feature, list_tilesets, list_tileset_jobs, get_tileset_recipe, list_tileset_sources, list_tileset_activity). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.mapbox.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mapbox Studio. Mapbox Studio and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Mapbox styles does my account have?"
• "Show details of Mapbox style cjikt35x83t1z2rnxpdmjs7y7"
• "Which Mapbox datasets do I have?"
• "How many features are in Mapbox dataset ckd1abc2d0001xyz?"
• "Show the features in Mapbox dataset ckd1abc2d0001xyz"
• "Show feature park-001 of Mapbox dataset ckd1abc2d0001xyz"

What it does

• list_styles: List the map styles of an account with name, id, owner, created and modified time (metadata only). Needs the styles:list scope.
• get_style: Get one style's header information: name, owner, visibility, protection and draft flags, center, zoom, sources and sprite. Layers are left out. Needs the styles:read scope.
• list_datasets: List the datasets (editable GeoJSON collections) of an account with name, description, feature count, size and bounds. Needs the datasets:list scope.
• get_dataset: Get one dataset's information: name, description, owner, dates, feature count, size and bounds. Needs the datasets:read scope.
• list_dataset_features: List the GeoJSON features of a dataset (up to 1000 per call) with ids, properties and geometry. Needs the datasets:read scope.
• get_dataset_feature: Get one feature of a dataset by id: its geometry and properties. Needs the datasets:read scope.
• list_tilesets: List the tilesets of an account with type, name, visibility, status, size and dates. Needs the tilesets:list scope.
• list_tileset_jobs: List the processing jobs of one tileset (publish runs) with stage, dates, errors, warnings and file size; can filter by stage. Needs the tilesets:list scope.
• get_tileset_recipe: Get the recipe (layer definitions, zoom range and source) used to build a tileset. Needs the tilesets:list scope.
• list_tileset_sources: List the tileset sources (uploaded GeoJSON inputs for tilesets) of an account with file count and size. Needs the tilesets:list scope.
• list_tileset_activity: List 30-day request activity for the account's tilesets (request count, last modified), busiest first by default. Needs the tilesets:list scope.

BYOK key

You bring your own Mapbox Studio Mapbox access token (secret token with the read and list scopes of the resources you want) (https://account.mapbox.com/access-tokens/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.mapbox.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.mapbox.com/api/maps/styles/ (the API this connector calls, with a BYOK key)

Live from the Mapbox Studio API (api.mapbox.com) with a BYOK key; documentation: https://docs.mapbox.com/api/maps/styles/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mapbox Studio. Mapbox Studio and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Mapbox Studio account.

Built for: Worldwide. Languages: English.

Mapbox Studio (BYOK) — Privacy Policy

Effective 16 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Mapbox Studio (BYOK) is. Mapbox Studio (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Mapbox Studio data: Read your Mapbox styles, datasets and features, tilesets, tileset jobs, recipes, sources and tileset request activity with your own access token. You bring your own Mapbox Studio Mapbox access token (secret token with the read and list scopes of the resources you want); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Mapbox Studio call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.mapbox.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Mapbox Studio rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Mapbox Studio receives. The request we make on your behalf, including the key and the arguments, under Mapbox Studio's own terms and privacy policy (https://www.mapbox.com/legal/tos). Mapbox Studio acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Mapbox Studio gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Mapbox Studio data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Mapbox Studio (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Mapbox Studio at any time to end all access.

Children. Mapbox Studio (BYOK) is a general-audience service operated by the adult using the assistant, under Mapbox Studio's own age rules.

Changes. We will post changes here with a new effective date.

Mapbox Studio (BYOK) — Terms of Service

Effective 16 October 2026. These terms govern use of the Mapbox Studio (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Mapbox Studio (BYOK) provides: Read your Mapbox styles, datasets and features, tilesets, tileset jobs, recipes, sources and tileset request activity with your own access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Mapbox Studio credentials and only access data you are allowed to access. Mapbox Studio's terms (https://www.mapbox.com/legal/tos) apply to your use of Mapbox Studio; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mapbox Studio. Mapbox Studio and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Mapbox Studio returns, lightly trimmed; it may be incomplete, delayed or changed by Mapbox Studio. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Mapbox Studio account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Mapbox Studio's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Mapbox Studio may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Mapbox Studio key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Mapbox Studio takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-mapbox-studio

Mapbox Studio (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-mapbox-studio.connectorbay.com/mcp
• REST API: https://byok-mapbox-studio.connectorbay.com/openapi.json
• Live status: https://byok-mapbox-studio.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Mapbox Studio (BYOK) never asks for them.