Ext Ops Panel
Open dashboard
Comparison

Mapbox Developer vs 1acre Land Intelligence

Mapbox Developer is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). 1acre Land Intelligence is an MCP server published by 1acre.in. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceMapbox Developer1acre Land Intelligence
Docker MCP Catalog Listed
Version: sha256:4dd53e90855e
Forks (GitHub): 11
Pulls (Docker Hub): 14 257
Stars (Docker Hub): 1
Stars (GitHub): 61
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Mapbox Developer vs 1acre Land Intelligence
FactMapbox Developer1acre Land Intelligence
Marketplaces that list it11
Stars (GitHub) (differs)61 (better)0 (worse)
Pulls (Docker Hub) (differs)14 257No figure on Docker Hub
Forks (GitHub) (differs)11 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mapbox-devkit)Remote server (mcp.1acre.in/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)23Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/mapbox/mcp-devkit-servergithub.com/1acre-in/1acre-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (30 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Mapbox Developer

In its own words, on Docker MCP Catalog:

Direct access to Mapbox developer APIs for AI assistants. Enables style management, token management, GeoJSON preview, and other developer tools for building Mapbox applications.

1acre Land Intelligence

In its own words, on Official MCP Registry:

Look up Indian land parcels by survey number or lat/lon. Returns parcel boundaries.

How to run each

Mapbox Developer As a local MCP server: Docker image

Claude Code
claude mcp add --env "MAPBOX_ACCESS_TOKEN=<YOUR_MAPBOX_ACCESS_TOKEN>" --transport stdio mapbox-devkit -- docker run -i --rm -e MAPBOX_ACCESS_TOKEN mcp/mapbox-devkit

Requires: MAPBOX_ACCESS_TOKEN (secret)

1acre Land Intelligence As a remote MCP server

Claude Code
claude mcp add --transport http land-intelligence https://mcp.1acre.in/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only 1acre Land Intelligence has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of 1acre Land Intelligence publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of 1acre Land Intelligence publish no settings it asks for, so we do not compare settings.

What it can do: Mapbox Developer · What it can do: 1acre Land Intelligence · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built