# 3GPP Scout API and hosted MCP server

> 3GPP Scout is a hosted 3GPP MCP server and REST API for semantic search over the full 3GPP TS/TR corpus (Release 15 through Release 20, 8,700+ document versions, 1.3M+ sections). You do not need to run a local index. For the agent skill guide, see [skill.md](https://api.3gppscout.com/skill.md). Homepage: [https://3gppscout.com](https://3gppscout.com).

## Hosted 3GPP MCP server

3GPP Scout is a **hosted 3GPP MCP server**. Agents connect over Streamable HTTP. Authentication is **OAuth 2.1** (browser sign-in on first use). Do not put a Scout API key in MCP config. REST uses an API key; MCP does not.

- Homepage: [https://3gppscout.com](https://3gppscout.com)
- Product page: [https://3gppscout.com/mcp](https://3gppscout.com/mcp)
- Chat app: [https://app.3gppscout.com](https://app.3gppscout.com)
- MCP endpoint (Streamable HTTP): `https://api.3gppscout.com/mcp/`
- Catalog (JSON): [https://api.3gppscout.com/.well-known/mcp.json](https://api.3gppscout.com/.well-known/mcp.json)
- REST docs: [https://api.3gppscout.com/docs](https://api.3gppscout.com/docs)
- Agent skill: [https://api.3gppscout.com/skill.md](https://api.3gppscout.com/skill.md)
- Setup prompt: [https://api.3gppscout.com/agent-setup/prompt.md](https://api.3gppscout.com/agent-setup/prompt.md)

Explorer includes 150 direct API/MCP requests per UTC calendar month. Founding Engineer is $8/month for 1,000.

## Corpus

The production index covers **all currently published TS/TR versions for Rel-15 through Rel-20** (8,700+ document versions, 1.3M+ sections). It is kept current as 3GPP publishes new and revised specifications.

## MCP tools

The server has 17 tools named for what an agent wants to do. Typical flow: `search_specs` to find the clause that defines a behavior, `read_clause` to quote it, `clause_history` to check later releases, then the meeting tools to see what is still being discussed.

- Specifications: `search_specs` (normative specs first, with a role on every result), `read_clause` (one clause with its citation), `clause_history` (which releases have a clause and which changed it), `lookup_reference` (a cause code, timer, information element or message by name or number, or a term or abbreviation a spec defines), and `find_conformance_tests` (the test cases for one requirement clause).
- Meetings, TDocs and companies: `search_meeting_documents` (TDocs by topic, with group, meeting, spec, company and date filters), `find_meetings` (meeting IDs by group and date), `get_meeting_decisions` (what a meeting agreed), `get_tdoc` (one TDoc with its quoted proposals), and `company_positions` (who proposed, supported or opposed something, quoted from their TDocs).
- Simulation results: `find_simulation_results` (which companies reported what gain for a RAN1 agenda item or topic, against which baseline, grouped by company, each value with its TDoc, link, location and verbatim quote).
- Followed topics: `find_topics_to_follow`, `follow_topic`, `list_followed_topics`, `update_followed_topic`, `unfollow_topic`, and `get_followed_topic_updates`.

The same list is in the [catalog](https://api.3gppscout.com/.well-known/mcp.json).

## TDocs

A separate TDoc catalog covers the full registers of recent meetings of RAN1 to RAN4, SA1 to SA4, CT1, CT3, CT4 and the RAN, SA and CT plenaries (currently 60+ meetings, 55,000+ registered TDocs, 50,000+ parsed and searchable), plus on-demand fetch of any named TDoc usually within seconds (REST). Meeting decisions from chair notes and reports are extracted for a pilot subset so far. Company positions are quoted verbatim from the TDocs that state them; cross-meeting stories are not built yet. Each TDoc call is one ordinary metered API/MCP request.

## REST only

These are available over the REST API with a Bearer API key, not as MCP tools: `POST /tdocs/{tdoc_id}/fetch` (download and parse any TDoc on demand), `POST /tdocs/batch` (up to 10 TDocs in one call, each counted as one request), `GET /organizations` and `GET /organizations/{org_id}` (company names and TDoc activity), and `GET /news/search` (FCC and SEC filings and news metadata, with short verified quotes; context, not 3GPP evidence).

## IETF RFCs

The IETF RFCs that 3GPP depends on: every RFC a current 3GPP spec cites (obsoleted ones included) and the current RFCs of the transport and signalling working groups, about 2,270 RFCs and no Internet-Drafts. Available over REST: `POST /rfcs/search` (RFC passages by meaning and by exact term, each with its section link, status, attribution line and the 3GPP clauses that cite the RFC) and `GET /rfcs/{rfc_number}` (one RFC section verbatim, or an RFC's outline with the clauses that cite it). Quote at most 100 words per excerpt and 300 words from one RFC per answer, verbatim, with the attribution line.

## FAQ

- **Is there a hosted 3GPP MCP server?** Yes. 3GPP Scout at `https://api.3gppscout.com/mcp/`. Product page: [3gppscout.com/mcp](https://3gppscout.com/mcp).
- **Do I need to self-host or clone a GitHub MCP project?** No. Scout is a hosted remote MCP server.
- **Does MCP need an API key?** No. MCP uses OAuth 2.1. REST uses a Bearer API key from the dashboard.
- **Which releases?** Rel-15 through Rel-20, the full published TS/TR set.
- **Does the index stay up to date?** Yes. New and bumped 3GPP specs are ingested into the live index.
- **Do you cover TDocs?** Yes. Recent meetings of RAN1 to RAN4, SA1 to SA4, CT1, CT3, CT4 and the plenaries, plus on-demand fetch over REST. See the MCP tools and TDocs sections above.