mqtt-spec-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Evidence from the OASIS MQTT 3.1.1 and 5.0 specifications; each call reads one version.
Pass version "3.1.1" or "5.0" on every call; if the user named none, ask. Never carry section numbers, labels or codes between versions (3.1.1 has Clean Session and return codes; 5.0 has Clean Start, Session Expiry, properties and reason codes). To compare, query each version and cite the version with each claim.
Consult the tools before answering: search once with the question's key terms, one ';'-separated group per part of the question, and answer from the results, citing their sections; use lookup for one exact packet, property, code, label or term. Results marked (excerpt: ...) show part of a section; unmarked results are complete. If your answer would say MQTT does not require, define or mention something, leaves it open or optional, or that a rule has no exception, and the section that would decide it is excerpted or not listed, first get that section: at most one section per version. Never invent identifiers.
Keep MUST/SHOULD/MAY and every condition and exception.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mqtt_spec_outlineB | Section ids and titles of one MQTT version, for browsing. |
| mqtt_spec_searchB | Evidence from one MQTT version: excerpts of the sections that best match the question. |
| mqtt_spec_getA | One section of one MQTT version as Markdown pages; continue a page with its Next cursor. |
| mqtt_spec_lookupB | Exact entry for one packet, property or reason_code (5.0), return_code (3.1.1), requirement label or glossary term. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a recognizable retrieval role: outline for browsing, search for ranked excerpts, get for full section text with pagination, lookup for exact named entries. Search, get, and lookup all retrieve spec content and could occasionally be confused, but the descriptions clearly delineate excerpt vs. full section vs. exact entry.
All four tools share a consistent mqtt_spec_ prefix and snake_case form, which makes the set easy to scan. The suffix mix is minor ('outline' and 'lookup' read as nouns while 'search' and 'get' are verbs), but the pattern is still predictable.
Four tools is lean but sensible for a read-only spec retrieval server, with each tool covering a distinct access pattern (browse, search, read, exact lookup). It borders on thin since there is no separate tool to enumerate the available MQTT versions.
The surface covers the core documentation workflows: navigation, discovery, full-text retrieval with cursor pagination, and precise term/identifier lookup across versions. Minor gaps remain, such as no way to list supported versions or compare sections between versions, but agents can work around these via outline.