MCP Devkit Server vs PlaceRoot
A side-by-side look at the MCP Devkit Server and PlaceRoot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Devkit Server for location services work as a local process; choose PlaceRoot for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Devkit Server when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MAPBOX_ACCESS_TOKEN. - You want tools like
Note, ListStylesTool, CreateStyleTool.
Choose PlaceRoot when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 61/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MAPBOX_ACCESS_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 61 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 40 | Not listed |
| Full listing | View MCP Devkit Server | View PlaceRoot |
Tools & capabilities
MCP Devkit Server tools 40
NoteThis tool automatically fetches the first available public token from your account for the preview URL. Requires at least one public token with `styles:read` scope.ListStylesToolRequires `styles:list` scopeCreateStyleToolRequires `styles:write` scopeRetrieveStyleToolRequires `styles:download` scopeUpdateStyleToolRequires `styles:write` scopeDeleteStyleToolRequires `styles:write` scopePreviewStyleToolRequires `tokens:read` scope (to list tokens) and at least one public token with `styles:read` scopestatisticsObject with type, feature count, geometry types, and bounding boxseverity"error", "warning", or "info"messageDescription of the issuepathJSON path to the problem (optional)suggestionHow to fix the issue (optional)- +28 more on the listing page
PlaceRoot tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Devkit Server
{
"mcpServers": {
"mcp-devkit-server": {
"command": "npx",
"args": [
"-y",
"@anthropic-ai/dxt"
],
"env": {
"MAPBOX_ACCESS_TOKEN": "YOUR_MAPBOX_ACCESS_TOKEN_HERE"
}
}
}
}
PlaceRoot
{
"mcpServers": {
"placeroot": {
"command": "uvx",
"args": [
"placeroot"
]
}
}
}
Frequently asked questions
MCP Devkit Server is categorized under Location Services and uses a local stdio subprocess. PlaceRoot belongs to Location Services and uses a local stdio subprocess. Pick MCP Devkit Server for location services work and PlaceRoot for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Devkit Server has no declared pricing — check the project's own site. PlaceRoot has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-devkit-server and placeroot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Devkit Server has a quality signal of 61/100 (Good) with 0 views, 0 installs and 61 GitHub stars. PlaceRoot has 40/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.