mcp-rfc-editor
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_rfcC | Load an RFC TXT file and parse its sections |
| download_rfcB | Download an RFC by number from rfc-editor and parse it |
| create_rfcC | Create a new empty RFC document |
| get_documentA | Get the current active RFC document from session context |
| save_rfcC | Save an RFC document to a TXT file |
| get_titleB | Get the title of an RFC document |
| get_abstractC | Get the abstract of an RFC document |
| get_copyrightA | Get the copyright notice of an RFC document |
| get_status_of_memoB | Get the status of this memo section |
| get_tocC | Get the table of contents |
| get_acknowledgementsC | Get the acknowledgements of an RFC document |
| get_contributorsC | Get the contributors of an RFC document |
| get_authors_addressB | Get the authors address section of an RFC document |
| get_section_by_titleC | Get a section by its title |
| set_titleC | Set the title of an RFC document |
| set_abstractB | Set the abstract of an RFC document |
| add_sectionC | Add a new section to an RFC document |
| update_sectionB | Update an existing section in an RFC document |
| delete_sectionB | Delete a section from an RFC document |
| list_sectionsB | List all sections in an RFC document |
| set_copyrightB | Set the copyright notice of an RFC document |
| set_authorsC | Set the authors of an RFC document |
| set_acknowledgementsC | Set the acknowledgements of an RFC document |
| set_contributorsC | Set the contributors of an RFC document |
| set_authors_addressC | Set the authors address section of an RFC document |
| set_status_of_memoC | Set the status of this memo section |
| set_tocC | Set the table of contents |
| set_section_by_titleC | Update a section by its title |
| to_dictB | Convert an RFC document to a dictionary |
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 29 tools
Most tools have clearly distinct purposes, with getters/setters for specific fields and section operations. However, 'update_section' and 'set_section_by_title' are ambiguous as both update a section, and the distinction between them is unclear from descriptions.
The naming pattern is largely verb_noun with 'get_' and 'set_' for attributes, and 'add_', 'delete_', 'update_', 'list_' for sections. Deviations include 'to_dict' and 'set_section_by_title' which is a longer form, but overall consistent.
29 tools is relatively high for a document editor, with individual getters/setters for each field. While this provides clarity, it may be excessive; a more streamlined set with fewer, more generic tools could suffice.
The tool set covers core RFC editing operations: download, load, save, create, metadata fields, and section management. Minor gaps include lack of tools for section reordering or retrieving full document text directly.