note-draft-mcp
Related Servers
Alternatives to note-draft-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables automated publishing and draft saving to note.com platform using Playwright automation. Reads Markdown files with titles, body text, and tags to publish content directly to your note.com account.215 npm57MIT
- AlicenseNot gradedqualityDmaintenanceEnables saving articles to WeChat Official Account drafts with support for rich text, automatic image upload, and Markdown rendering including Mermaid diagrams.1MIT
- AlicenseAqualityBmaintenanceEnables writing Naver blog posts with rich formatting like images, tables, formulas, and places, converting Markdown to drafts and handling publishing via MCP tools.7MIT
- AlicenseBqualityCmaintenanceEnables interaction with note.com through API to search and read articles, manage posts and drafts, handle comments and likes, retrieve analytics, and access membership information.3330 npm30ISC
- AlicenseAqualityDmaintenanceThe Universal MCP Server exposes tools for automated posting and draft saving to note.com. It reads Markdown files containing titles, body text, and tags, then publishes them to your note.com account using Playwright automation.215 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables publishing Markdown blog posts to cnblogs.com via MCP protocol using natural language.3-
TDQS
Scored across 5 tools
Each tool targets a distinct action on a distinct concern: creating a new draft, replacing an existing draft, uploading a standalone image, setting an eyecatch, and listing drafts. The only mild overlap is upload_image being auto-invoked by create_draft, but the description explicitly clarifies when to use it, eliminating confusion.
All five tools follow a strict verb_noun snake_case pattern (create_draft, update_draft, upload_image, set_eyecatch, list_drafts). The convention is uniform and predictable throughout.
Five tools is well-scoped for a note draft management server, with each tool earning its place around a clear draft lifecycle. No bloat or redundancy beyond the intentional upload_image helper.
The surface covers create, update, list, image upload, and eyecatch setting, but lacks a delete_draft operation and a get-single-draft fetch (list only returns summary fields). Publishing being manual is a deliberate design choice, so the gap is minor and workable around.