Explore likely radio services, channels, and emissions from 108 MHz to 1 GHz.
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
docker run -i --rm ghcr.io/guycole/mellow-tapir-mcp:1.0.2
MCP client config
{
"mcpServers": {
"mellow-tapir-radio-spectrum-guide": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/guycole/mellow-tapir-mcp:1.0.2"
]
}
}
}Mellow-Tapir is an experimental MCP server that helps radio hobbyists explore likely services, channels, and signal types across the radio spectrum from 108 MHz to 1 GHz; it is not a frequency-coordination or regulatory-authority tool.
For server setup, local Ollama testing, sample MCP client sessions, and Docker usage, see src/tapir_mcp_server/README.md.
The Tapir MCP server exposes the following tools:
classify_frequency: classify a single frequency into matching channels and likely services.query_channels: list known channels inside a frequency range.search_services: search service and use-name text across the catalog.execute_readonly_sql: run read-only SQL (SELECT or WITH) against the SQLite catalog.ask_reference_model: query a local reference LLM through Ollama, defaulting to gpt-oss:20b.For detailed parameters, outputs, and examples, use the tool reference in src/tapir_mcp_server/README.md.
The dox/allocation directory is a versioned archive of authoritative United States radio-frequency allocation and service references. The collection prioritizes spectrum at 30 MHz and above and is intended to support source-preserving extraction into a normalized database rather than replace the original publications.
The archive currently includes:
The manifest.json file is the index to the archive. Each entry records the publishing agency, title and version, effective or publication date when available, original URL, retrieval date, local filename, media type, file size, SHA-256 checksum, and intended use.
Source files are preserved in their original formats. New revisions should be added under a new version directory and appended to the manifest; existing versions should not be overwritten. Derived records should retain links to their source artifact and, where possible, the relevant page, section, table, or rule citation so database results remain traceable to the authoritative material.
The MCP server uses a read-only SQLite file built from the editable catalog under src/tapir_schema.
Data sources:
src/tapir_schema/seed.json: authoritative editable band, emission, and channel catalog.src/tapir_schema/schema.sql: reference SQL schema used for provenance and alignment with the source data model.Build location:
Build command:
cd /Users/gsc/github/mellow-tapir/src/tapir_mcp_server
./venv/bin/python -m mcp_server.build_db \
--db-path data/tapir.sqlite \
--seed-path ../tapir_schema/seed.json \
--schema-path ../tapir_schema/schema.sql
When source catalog data changes, rebuild the SQLite file with the command above and restart the MCP server.