note-post-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTE_POST_MCP_TIMEOUT | No | Timeout in milliseconds | 180000 |
| NOTE_POST_MCP_STATE_PATH | No | Path to the authentication state file | ~/.note-state.json |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_noteB | note.comに記事を公開します。Markdownファイルからタイトル、本文、タグ、価格設定を読み取り、自動的に投稿します。有料記事はFront Matterのpriceで価格指定、または本文中ので有料ラインを設定できます。 |
| save_draftA | note.comに下書きを保存します。Markdownファイルからタイトル、本文、タグを読み取り、下書きとして保存します。 |
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 2 tools
publish_note and save_draft have clearly distinct purposes: one publishes immediately, the other saves a draft. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern: publish_note and save_draft. The naming is predictable and uniform.
With only 2 tools, the server is minimal but for a narrow purpose like posting notes, this is reasonable. It is slightly below the typical 3-15 range but each tool serves a distinct and necessary function.
The server covers the core publishing workflow (draft and publish) but lacks update, delete, or list operations. This is a notable gap for managing existing notes, though for a simple posting tool it may be acceptable.