note-draft-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTE_XSRF_TOKEN | No | The XSRF token to use. If not provided, it is automatically extracted from the `NOTE_SESSION_COOKIE` header when present. | |
| NOTE_SESSION_COOKIE | Yes | The value of the `_note_session_v5` cookie, or the full Cookie header from a logged-in note.com browser session. This acts like a password and must be kept secret. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_draftA | Markdown を note 用の HTML に変換し、自分の note アカウントに新しい下書きとして保存する。公開はしない(公開は note の画面から手動で行う)。ローカル画像は自動でアップロードして埋め込む。まず dry_run: true で内容を確認することを勧める。 |
| update_draftA | 既存の下書きのタイトルと本文を、指定した Markdown で丸ごと置き換える。公開済みの記事は更新できない(下書き一覧にある ID だけ受け付ける)。公開はしない。 |
| upload_imageA | ローカルの画像(PNG / JPEG / GIF、10MB まで)を note にアップロードし、本文に埋め込める URL を返す。通常は create_draft が自動で行うので、単体で使う必要はあまりない。 |
| set_eyecatchA | 既存の下書きに見出し画像(アイキャッチ)を設定する。下書き一覧にある ID だけ受け付ける。 |
| list_draftsB | 自分の note の下書きを新しい順に返す(ID・タイトル・編集画面の URL)。 |
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 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.