mapbox / mapbox/mcp-devkit-server

feat: add Mapbox Tiling Service (MTS) tools

Open
#115 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
60
Forks
12
Avg merge
2d 9h
Merged PRs (30d)
5

Description

## Summary

Add MTS tools so agents can take raw data (GeoJSON, CSV, etc.) all the way through to a published tileset that can be referenced in a style layer — entirely within the devkit.

## Why DevKit

MTS is a data-pipeline / developer workflow operation, not a runtime geospatial computation. It belongs alongside the existing style and token management tools rather than in the mainline geo-computation MCP server.

## Proposed Tools

| Tool | MTS / Uploads API endpoint | Description |
|---|---|---|
| `upload_tileset_source_tool` | `POST /tilesets/v1/sources/{username}/{id}` | Upload a GeoJSON or CSV file as a tileset source |
| `create_tileset_tool` | `POST /tilesets/v1/{tileset_id}` | Create a tileset with a recipe |
| `publish_tileset_tool` | `POST /tilesets/v1/{tileset_id}/publish` | Kick off the tiling job |
| `get_tileset_status_tool` | `GET /tilesets/v1/{tileset_id}/jobs/{job_id}` | Poll job status (queued / processing / success / failed) |
| `list_tilesets_tool` | `GET /tilesets/v1/{username}` | List tilesets for the authenticated user |

## Agent Workflow This Enables

```
1. upload_tileset_source_tool — POST GeoJSON/CSV → get source_id
2. create_tileset_tool — define tileset + recipe referencing source_id
3. publish_tileset_tool — kick off tiling job → get job_id
4. get_tileset_status_tool — poll until status === "success"
5. update_style_tool (exists) — add a layer referencing the new tileset
```

This gives an agent a complete "I have data, build me a map" loop without leaving the devkit.

## Token Scopes Required

- `tilesets:write` — create, update, publish tilesets
- `tilesets:read` — list, status
- `tilesets:list` — list tilesets

## References

- [Mapbox Tiling Service API docs](https://docs.mapbox.com/api/maps/mapbox-tiling-service/)
- [Uploads API docs](https://docs.mapbox.com/api/maps/uploads/)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Mapbox Tiling Service and Uploads API references linked in the issue, then trace how existing style and token management tools are structured in the devkit. Implement and verify the five proposed tools across upload, creation, publishing, status polling, and listing, with the required token scopes and the documented agent workflow working end to end.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.