Mcp Rfc Editor
Draft and revise RFC-style specification documents with your agent using dedicated MCP editing capabilities instead of plain markdown chat.
Overview
io.github.daedalus/mcp-rfc-editor is a MCP server for the Build phase that provides RFC editing capabilities to AI models over stdio.
What is this MCP server?
- MCP RFC editor server (mcp-rfc-editor v0.1.2 on PyPI) with stdio transport for agent hosts
- Provides RFC-oriented editing capabilities exposed as MCP tools to the model
- Supports solo builders writing internal API specs, ADRs, or standards-track style documents
- Hosted at github.com/daedalus/mcp-rfc-editor with MCP registry schema metadata
- Documentation workflow integration—not automatic publication to IETF or RFC Editor services
- Server version 0.1.2 registered with Model Context Protocol schema 2025-12-11
- PyPI identifier mcp-rfc-editor using stdio transport
- Repository github.com/daedalus/mcp-rfc-editor
What problem does it solve?
Writing rigorous RFCs and API specs in chat produces unstructured text that is hard to iterate on with proper section discipline.
Who is it for?
Indie platform authors and API maintainers who want agent help structuring Internet-draft-style or internal RFC documents.
Skip if: Builders who only need README tweaks, or teams expecting automated IETF submission and official RFC numbering.
What do I get? / Deliverables
After you add the server, your agent can use RFC-oriented MCP editing tools while you keep specs versioned with your codebase.
- Agent-accessible RFC editing MCP toolset
- Iterated specification drafts with structure suited to RFC-style sections
- Specs kept adjacent to code in your documentation workflow
Recommended MCP Servers
Journey fit
Protocol and design RFCs are written while you are building and documenting how systems behave—canonical placement is Build docs. Docs subphase fits tools that help produce structured specifications, ADRs, and Internet-draft-style text your team will implement against.
How it compares
RFC/spec editing MCP server, not a generic markdown linter skill or OpenAPI generator alone.
Common Questions / FAQ
Who is mcp-rfc-editor for?
Solo developers and small teams who write formal or semi-formal RFC-style specifications and want MCP-backed editing in their AI coding workflow.
When should I use mcp-rfc-editor?
Use it during Build docs when you are drafting or revising protocol specs, ADRs, or standards-oriented documents aligned with implementation.
How do I add mcp-rfc-editor to my agent?
Install mcp-rfc-editor from PyPI, configure the stdio MCP server block in Claude Code or Cursor, point it at your spec repo, and reload tools so RFC editing endpoints appear.