note-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ACCESS_TOKEN | No | Password used to authenticate to the remote MCP server over OAuth. Only required for Cloudflare Workers deployment. | |
| NOTE_SESSION_COOKIE | No | Your note.com session cookie (`_note_session_v5`). Required for both local/Docker and Cloudflare Workers modes. |
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 |
|---|---|
| note_create_draftA | note.comに新しい下書き記事を作成する。公開はされない（下書きのまま保存される）。本文はプレーンテキスト、または簡易Markdown（太字、文字）を1行1段落として渡す。tags を指定した場合はタグ付けも試みるが、note.com側のAPI仕様が未確認のため失敗することがある（その場合も記事自体の作成は成功する）。 |
| note_update_draftA | 既存の下書き記事（IDで指定）のタイトル・本文を上書き保存する。公開状態は変更しない。 |
| note_get_draftA | 下書き記事の現在の内容を取得する（動作確認・デバッグ用）。note.com側のAPI仕様が未確認のため、取得自体が失敗する可能性がある実験的機能。 |
| note_publish_draftA | 下書き記事を公開する。【不可逆・対外公開を伴う操作】記事が誰でも閲覧可能な状態になる。note.com側の公開APIは未確認のため動作未保証の実験的機能。confirm:true を指定しない限り実行されない。 |
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 4 tools
Each tool performs a distinctly different action in the draft lifecycle: create, update, get, and publish. There is no meaningful overlap, and the irreversible publish operation is clearly separated by the confirm:true requirement.
All tool names follow the same note_<verb>_<object> pattern with consistent snake_case. The naming is predictable and makes the function of each tool immediately clear.
Four tools is a well-scoped size for a focused draft-management server. Each tool covers a necessary step in the core draft workflow without unnecessary bloat.
The server covers create, read, update, and publish for drafts, but there is no delete or list operation, which are notable gaps in a draft-management workflow. The experimental nature of several tools also makes some operations unreliable.