Log inSubmit server
Opencellid logo

Opencellid

Queries OpenCellID for cell-tower details and nearby towers through MCP tools or HTTP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Opencellid

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "opencellid": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-opencellid"
      ],
      "env": {
        "PLATFORM_OPENCELLID_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 2 tools correctly (7d ago).

Overview

The Opencellid MCP server connects AI clients to OpenCellID's cell-tower geolocation database through tools for tower lookup and area searches. It can run locally as a stdio package or remotely through the Pipeworx gateway, which also exposes shared routing and discovery tools. Use it when an agent needs to identify a cell from network identifiers or list towers within a geographic bounding box. Authentication uses an OpenCellID API key, supplied through the gateway configuration or a BYO key.

Use cases

  • Look up a cell tower from MCC, MNC, LAC, and cell ID values
  • Search for cell towers inside a geographic bounding box
  • Filter area results by mobile country or network code
  • Route natural-language OpenCellID questions through the Pipeworx gateway

Key features

  • Cell lookup by network identifiers
  • Bounding-box searches for nearby cells
  • Optional MCC, MNC, radio, and result-limit parameters
  • Local stdio MCP operation
  • Remote MCP and HTTP gateway access
  • Natural-language routing through ask_pipeworx

Tools2

What Opencellid lets your agent do. Expand a tool for its parameters.

Verified live~302 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

What it can do

From the 2 tools this server returned when we ran it.

Read-only tools · 2
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age157 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-opencellid (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads453Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed2Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Opencellid works

What the Opencellid MCP server does

The Opencellid MCP server gives MCP-compatible agents access to OpenCellID cell-tower data. Its pack-specific interface supports looking up a tower from mobile-network identifiers and finding towers inside a geographic bounding box. The underlying data source is OpenCellID at opencellid.org.

This is useful for workflows that have cellular network information such as MCC, MNC, LAC, and cell ID and need corresponding tower data. Area searches can accept optional network filters and a result limit, allowing an agent to narrow results by operator identifiers or control response size.

How it works

The package is available in two deployment modes. A remote MCP endpoint is hosted at the Pipeworx gateway, while the npm package can run locally and communicate over standard input and output. The local mode exposes only the OpenCellID pack tools. The gateway endpoint exposes those tools plus shared Pipeworx capabilities, including tool discovery, cross-catalog routing through ask_pipeworx, and memory-related tools.

The gateway also provides an HTTP interface for direct tool calls. For example, a client can send a JSON POST request to the get_cell tool endpoint instead of maintaining an MCP connection. The full Pipeworx gateway is another option when an agent needs all catalog packs listed directly; both gateway URLs use the same underlying gateway and data sources.

Setup and configuration

For a remote connection, add the gateway URL https://gateway.pipeworx.io/opencellid/mcp to an MCP client's server configuration. The README names Claude Desktop, Cursor, and Windsurf as compatible clients. A full-gateway connection uses https://gateway.pipeworx.io/mcp instead.

For local execution, configure the client to run npx -y @pipeworx/mcp-opencellid. This starts the standalone stdio server without a Pipeworx account or gateway round trip. The package can also be launched directly with the same command to verify that it starts.

Gateway authentication uses the PLATFORM_OPENCELLID_KEY environment setting. Alternatively, callers can register with OpenCellID and provide a key using the ?_apiKey=<key> form described by the project. The remote gateway and direct HTTP examples use the OpenCellID source's key-based access.

Tools and capabilities

The pack defines two primary tools:

  • get_cell(mcc, mnc, lac, cell_id, radio?) looks up a cell using mobile-country, network, location-area, and cell identifiers, with an optional radio value.
  • cells_in_area(bbox, mcc?, mnc?, limit?) searches for cells within a bounding box, with optional MCC, MNC, and result-limit filters.

The Opencellid MCP server can also be used through ask_pipeworx on gateway connections. An agent submits a natural-language question, and the gateway selects a tool and fills its arguments. Gateway connections list additional shared tools, so their tool count is larger than the two pack-specific operations.

Limitations and notes

The local server does not include Pipeworx shared meta-tools or cross-catalog routing. Gateway connections do include those tools, and the exact scope is reported by the MCP initialize response. The standalone package and gateway therefore differ in their listed tool sets even though they use the same pack tools and source.

An API key is part of the documented access setup. Clients should inspect the tool definitions and OpenCellID documentation before depending on those details. OpenCellID access is described as free with a key, but no specific quota is provided.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Opencellid

Opencellid is an MCP server that connects AI clients to the OpenCellID cell-tower geolocation database. Its main tools are get_cell for identifier-based tower lookups and cells_in_area for bounding-box searches, with optional network filters and limits. It runs locally over stdio or remotely through the Pipeworx gateway.

Run it with `npx -y @pipeworx/mcp-opencellid` and configure that command as a stdio MCP server. This local mode does not require a Pipeworx account. You can also add the remote gateway URL `https://gateway.pipeworx.io/opencellid/mcp` to an MCP client.

It provides `get_cell` and `cells_in_area`. `get_cell` accepts MCC, MNC, LAC, cell ID, and an optional radio value; `cells_in_area` accepts a bounding box plus optional MCC, MNC, and result-limit parameters.

Use an OpenCellID API key. Gateway deployments can use the `PLATFORM_OPENCELLID_KEY` environment setting, while BYO access uses the `?_apiKey=<key>` form after registering with OpenCellID.

Yes, Cursor is named as a supported MCP client in the setup instructions. Add the remote gateway URL to its MCP configuration, or configure Cursor to launch the local package with `npx -y @pipeworx/mcp-opencellid`.

Related MCP servers

All in Location Services All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpencellid AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/opencellid?style=directory)](https://allmcps.com/mcp/opencellid)
HTML Embed
<a href="https://allmcps.com/mcp/opencellid"><img src="https://allmcps.com/api/badge/opencellid?style=directory" alt="Opencellid on AllMCPs" /></a>