About RFC MCP Server
RFC MCP Server is an MCP server for fetching, parsing and reading RFC documents from ietf.org. It is intended for developers and agents that need to query Internet standards programmatically, and it handles both HTML and TXT formats.
Key features
- 01Fetch RFC documents by number
- 02Search RFCs by keyword
- 03Extract specific RFC sections
- 04Parse HTML and TXT formats
- 05Cache results for faster repeat access
Use cases
- 01Look up protocol specification details from a coding agent
- 02Find RFCs related to a keyword or protocol
- 03Extract a single section of an RFC for analysis
MCP support
The server exposes get_rfc, search_rfcs and get_rfc_section as tools, plus rfc://{number} and rfc://search/{query} as resource templates, for MCP clients to read RFC content.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
3Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| number | string | Yes | RFC number (e.g. "2616") |
| format | enum | No | Output format (full, metadata, sections)full | metadata | sections |
Details
From the project READMERFC MCP Server
An MCP server for fetching, parsing, and reading RFCs from the ietf.org website. This server provides tools and resources to interact with RFC documents programmatically.
Features
- Fetch RFC documents by number
- Search for RFCs by keyword
- Extract specific sections from RFC documents
- Parse both HTML and TXT format RFCs
- Caching for better performance
Installation
Configure your MCP settings file to use the server:
{
"mcpServers": {
"rfc-server": {
"command": "npx",
"args": ["@mjpitz/mcp-rfc"],
"disabled": false,
"autoApprove": []
}
}
}
Available Tools
get_rfc
Fetch an RFC document by its number.
Parameters:
number(string, required): RFC number (e.g. "2616")format(string, optional): Output format (full, metadata, sections), default: "full"
Example:
{
"number": "2616",
"format": "metadata"
}
search_rfcs
Search for RFCs by keyword.
Parameters:
query(string, required): Search keyword or phraselimit(number, optional): Maximum number of results to return, default: 10
Example:
{
"query": "http protocol",
"limit": 5
}
get_rfc_section
Get a specific section from an RFC.
Parameters:
number(string, required): RFC number (e.g. "2616")section(string, required): Section title or number to retrieve
Example:
{
"number": "2616",
"section": "Introduction"
}
Available Resources
Resource Templates
rfc://{number}: Get an RFC document by its numberrfc://search/{query}: Search for RFCs by keyword
Development
- Run in watch mode:
npm run dev - Start the server:
npm run start
License
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
Implementation Details
The server implements two main components:
- RFC Service: Handles fetching, parsing, and extracting data from RFCs
- MCP Server: Implements the MCP protocol and exposes tools and resources
The RFC service supports both HTML and TXT format RFCs, attempting to use HTML first for better structure, then falling back to TXT format if needed.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.