Note Post MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NAME | No | Server name override | note-post-mcp |
| NOTE_POST_MCP_TIMEOUT | No | Timeout in milliseconds for browser operations | 180000 |
| NOTE_POST_MCP_STATE_PATH | No | Path to the note.com 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_noteC | note.comに記事を公開します。Markdownファイルからタイトル、本文、タグを読み取り、自動的に投稿します。 |
| save_draftB | 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
The two tools have clearly distinct purposes: 'publish_note' is for publishing articles publicly, while 'save_draft' is for saving drafts privately. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the desired outcome.
Both tools follow a consistent verb_noun pattern ('publish_note' and 'save_draft'), using clear action verbs and the same noun. The naming is predictable and readable, with no deviations or mixed conventions.
With only 2 tools, the server feels thin for its apparent domain of note management on note.com. While publish and save draft are core operations, typical CRUD/lifecycle coverage would include tools for retrieving, updating, or deleting notes, making this set incomplete for robust agent workflows.
The tool surface is severely incomplete for note management. It lacks essential operations such as retrieving notes (e.g., list_notes, get_note), updating existing notes, deleting notes, or managing tags separately. This will cause agent failures when tasks require these missing actions.