3GPP Scout MCP server

Hosted 3GPP MCP Server

3GPP Scout is a hosted 3GPP MCP server. It makes 3GPP technical specifications (TS and TR) searchable from Cursor, Claude, Codex, and other MCP clients: 5G NR, LTE, RAN, and 5G core, Rel-15 through Rel-20.

You do not download the 3GPP FTP archive, parse Word files, or run a local SQLite index. Connect to the remote Model Context Protocol endpoint and search.

MCP endpoint: https://api.3gppscout.com/mcp/ (Streamable HTTP, OAuth 2.1)

This repository is the public listing and integration page for the 3GPP Scout MCP Server. The hosted service is proprietary. There is nothing here to go run or npx. If you want a 3GPP MCP server without self-hosting, this is that product.

Why a hosted 3GPP MCP

3GPP specifications are hard for LLMs to use from training data alone. There are thousands of TS/TR documents. A single spec such as TS 38.331 (NR RRC) or TS 23.501 (5G system architecture) can run hundreds of pages. Releases diverge. Tables and figures carry the protocol.

A self-hosted 3GPP MCP typically means: scrape the 3GPP archive, convert .docx, build a local database, and keep it current yourself. Scout runs that index as a service. New and revised 3GPP specs are ingested into the live search index as 3GPP publishes them.

The production corpus is Rel-15 through Rel-20 (8,700+ document versions, 1.3M+ sections). It is not a Rel-15 + Rel-19 subset.

What you can search

Semantic search over the published TS/TR set, including:

• 5G NR / RAN: 38-series (RRC, NG-RAN, NR overall description)
• 5G system and core: 23-series architecture, 24-series NAS, 29-series HTTP/2 service-based interfaces, 33-series security
• LTE / EPS: 36-series and related SAE specs
• Charging, OAM, and the rest of the TS/TR catalog in those releases, not only radio

Filter by release (Rel-18, Rel-19, …), document number (38.331, 23.501, 36.300), series, TS vs TR, or section. Image search covers figures, diagrams, and tables extracted from the specs.

Citations from the hosted chat app link to the specification's folder on the 3GPP FTP archive, not to a sentence-level PDF deep-link.

Connect an agent (Cursor, Claude, Codex)

Official registry name: com.3gppscout/scout

Cursor

Merge into .cursor/mcp.json:

{
  "mcpServers": {
    "3gpp-scout": {
      "url": "https://api.3gppscout.com/mcp/"
    }
  }
}

Enable 3gpp-scout under Cursor Settings > Tools & MCP. The first tool call opens a browser for OAuth. Do not put a Scout API key in the MCP config.

Claude Code

claude mcp add --transport http --scope user 3gpp-scout https://api.3gppscout.com/mcp/

Then /mcp and connect 3gpp-scout.

OpenAI Codex

codex mcp add 3gpp-scout --url https://api.3gppscout.com/mcp/
codex mcp login 3gpp-scout

Verify

Call listdocuments with docnumber=38.331 and release=Rel-19. You should see indexed versions of TS 38.331. Do not list the entire corpus as a health check.

Setup prompt for agents: api.3gppscout.com/agent-setup/prompt.md

MCP tools

Full agent skill (parameters, filters, workflows): api.3gppscout.com/skill.md. ClawHub listing: chriscarrotlabs/3gpp-scout.

REST with an API key (same corpus): api.3gppscout.com/docs

Shortened. The full README is on GitHub.