Which integrations are available for this server?

Processes Markdown files containing titles, body text, and tags for automated posting and draft saving to note.com

How do I use Note Post MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Note Post MCP publish my blog post from /home/user/blog.md with a thumbnail" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Note Post MCP

by Go-555

Overview Schema Related Servers Score Discussions

JavaScript

Local

Note Post MCP

GitHub

The 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.

Installation

Prerequisites

Node.js 18+
A note.com account
note-state.json authentication state file (obtained via npm run login)
Set NOTE_POST_MCP_STATE_PATH in your environment (optional, defaults to ~/.note-state.json)

Install from GitHub

git clone https://github.com/Go-555/note-post-mcp.git
cd note-post-mcp
npm install
npm run build

Install Playwright Browser

npm run install-browser

This installs the Chromium browser required for automation.

Get an authentication state file

Run the login script to authenticate with note.com:

npm run login

A browser window will open. Log in to note.com, then press Enter in the terminal. This creates a ~/.note-state.json file containing your authentication state. Store this file securely and reference it via NOTE_POST_MCP_STATE_PATH or pass it as a parameter.

Or install from npm (if published)

npm install -g note-post-mcp

Related MCP server: xhs-mcp

Setup: Claude Code (CLI)

Use this one-liner (replace with your real values):

claude mcp add Note Post MCP -s user -e NOTE_POST_MCP_STATE_PATH="/path/to/note-state.json" -- npx @gonuts555/note-post-mcp@latest

To remove:

claude mcp remove Note Post MCP

Setup: Cursor

Create .cursor/mcp.json in your client (do not commit it here):

{
  "mcpServers": {
    "note-post-mcp": {
      "command": "npx",
      "args": ["@gonuts555/note-post-mcp@latest"],
      "env": {
        "NOTE_POST_MCP_STATE_PATH": "/path/to/note-state.json"
      },
      "autoStart": true
    }
  }
}

Other Clients and Agents

Install via URI or CLI:

code --add-mcp '{"name":"note-post-mcp","command":"npx","args":["@gonuts555/note-post-mcp@latest"],"env":{"NOTE_POST_MCP_STATE_PATH":"/path/to/note-state.json"}}'

Add to your Claude Desktop configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "note-post-mcp": {
      "command": "npx",
      "args": ["@gonuts555/note-post-mcp@latest"],
      "env": {
        "NOTE_POST_MCP_STATE_PATH": "/path/to/note-state.json"
      }
    }
  }
}

Command: npx
Args: ["@gonuts555/note-post-mcp@latest"]
Env: NOTE_POST_MCP_STATE_PATH=/path/to/note-state.json

Type: STDIO
Command: npx
Args: @gonuts555/note-post-mcp@latest
Enabled: true

Example ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "note-post-mcp": {
      "type": "local",
      "command": ["npx", "@gonuts555/note-post-mcp@latest"],
      "enabled": true,
      "env": {
        "NOTE_POST_MCP_STATE_PATH": "/path/to/note-state.json"
      }
    }
  }
}

Add a new MCP and paste the standard JSON config from above.

Add the following to your Windsurf MCP configuration:

{
  "note-post-mcp": {
    "command": "npx",
    "args": ["@gonuts555/note-post-mcp@latest"],
    "env": {
      "NOTE_POST_MCP_STATE_PATH": "/path/to/note-state.json"
    }
  }
}

Setup: Codex (TOML)

Add the following to your Codex TOML configuration.

Example (Serena):

[mcp_servers.serena]
command = "uvx"
args = ["--from", "git+https://github.com/oraios/serena", "serena", "start-mcp-server", "--context", "codex"]

This server (minimal):

[mcp_servers.note-post-mcp]
command = "npx"
args = ["@gonuts555/note-post-mcp@latest"]
# Optional environment variables:
# NOTE_POST_MCP_STATE_PATH = "/path/to/note-state.json"
# NOTE_POST_MCP_TIMEOUT = "180000"
# MCP_NAME = "note-post-mcp"

Configuration (Env)

NOTE_POST_MCP_STATE_PATH: Path to the note.com authentication state file (default: ~/.note-state.json)
NOTE_POST_MCP_TIMEOUT: Timeout in milliseconds for browser operations (default: 180000)
MCP_NAME: Server name override (default: note-post-mcp)

Available Tools

publish_note

Publishes an article to note.com from a Markdown file.

Inputs:
- markdown_path (string, required): Path to the Markdown file containing title, body, and tags
- thumbnail_path (string, optional): Path to the thumbnail image file
- state_path (string, optional): Path to the note.com authentication state file
- screenshot_dir (string, optional): Directory to save screenshots
- timeout (number, optional): Timeout in milliseconds
Outputs: JSON object with:
- success (boolean): Whether the operation succeeded
- url (string): URL of the published article
- screenshot (string): Path to the screenshot
- message (string): Success message

save_draft

Saves a draft article to note.com from a Markdown file.

Inputs:
- markdown_path (string, required): Path to the Markdown file containing title, body, and tags
- thumbnail_path (string, optional): Path to the thumbnail image file
- state_path (string, optional): Path to the note.com authentication state file
- screenshot_dir (string, optional): Directory to save screenshots
- timeout (number, optional): Timeout in milliseconds
Outputs: JSON object with:
- success (boolean): Whether the operation succeeded
- url (string): URL of the draft editor page
- screenshot (string): Path to the screenshot
- message (string): Success message

Markdown File Format

Your Markdown file should follow this format:

---
title: Your Article Title
tags:
  - tag1
  - tag2
---

Your article body content goes here.

You can include URLs and they will be automatically expanded by note.com.

Alternatively, you can use array notation for tags:

---
title: Your Article Title
tags: [tag1, tag2]
---

Your article body content goes here.

Or use a simple # heading for the title if no front matter is present:

# Your Article Title

Your article body content goes here.

Body Content Details

The body content supports the following Markdown elements:

Front Matter Format:

All lines after the closing --- of the front matter are treated as body content
Trailing blank lines are automatically trimmed

Heading Format:

The first line starting with # is treated as the title (not included in the body)
Headings with ## or ### are treated as part of the body content

Code Blocks:

Must have a closing fence (```)
Language specification is preserved
Entire code blocks are pasted as a unit

Image Insertion:

Use relative paths from the Markdown file: ![description](./images/sample.png)
Supports PNG, JPEG, and GIF formats
Local image files are automatically uploaded

Lists and Quotes:

Bullet lists (-) and numbered lists (1.) are automatically continued by note.com
Block quotes (>) are also automatically continued
Markdown symbols are processed automatically after the first line

Horizontal Rules:

--- in the body content is correctly processed as a horizontal rule
Blank lines immediately following horizontal rules are automatically skipped

URL Single Lines:

URLs on their own line are automatically expanded into link cards by note.com
YouTube and other embeds are also automatically processed

Example invocation (MCP tool call)

{
  "name": "publish_note",
  "arguments": {
    "markdown_path": "/path/to/article.md",
    "thumbnail_path": "/path/to/thumbnail.png",
    "state_path": "/path/to/note-state.json"
  }
}

For saving a draft:

{
  "name": "save_draft",
  "arguments": {
    "markdown_path": "/path/to/draft.md"
  }
}

Troubleshooting

Authentication errors: Ensure your note-state.json file is valid and up-to-date. You may need to regenerate it if your session has expired.
Ensure Node 18+: Run node -v to verify your Node.js version.
Build errors: Run npm install and npm run build to ensure all dependencies are installed and TypeScript is compiled.
Local runs: After building, test locally with npx note-post-mcp (it will wait for MCP messages on stdin).
Inspect publish artifacts: Run npm pack --dry-run to see what files will be included in the published package.
Timeout issues: If operations are timing out, increase NOTE_POST_MCP_TIMEOUT or pass a larger timeout parameter.
Playwright browser not installed: Run npm run install-browser or npx playwright install chromium to install the required browser.

References

Name Consistency & Troubleshooting

Always use CANONICAL_ID (note-post-mcp) for identifiers and keys.
Use CANONICAL_DISPLAY (Note Post MCP) only for UI labels.
Do not mix different names across clients.

Consistency Matrix

npm package name → note-post-mcp
Binary name → note-post-mcp
MCP server name (SDK metadata) → note-post-mcp
Env default MCP_NAME → note-post-mcp
Client registry key → note-post-mcp
UI label → Note Post MCP

Conflict Cleanup

Remove any old entries with different names and re-add with note-post-mcp.
Ensure global .mcp.json or client registries only use note-post-mcp for keys.
Cursor: Configure in the UI only. This project does not include .cursor/mcp.json.

Example

Correct: "mcpServers": { "note-post-mcp": { "command": "npx", "args": ["@gonuts555/note-post-mcp@latest"] } }
Incorrect: Using different keys like "NotePost" or "note_post" (will conflict with note-post-mcp)

License

MIT

Available Tools

2 tools

publish_noteC

note.comに記事を公開します。Markdownファイルからタイトル、本文、タグを読み取り、自動的に投稿します。

ParametersJSON Schema

Name	Required	Description
`markdown_path`	Yes	Markdownファイルのパス（タイトル、本文、タグを含む）
`thumbnail_path`	No	サムネイル画像のパス（オプション）
`state_path`	No	note.comの認証状態ファイルのパス（デフォルト: /app/.note-state.json）
`screenshot_dir`	No	スクリーンショット保存ディレクトリ（オプション）
`timeout`	No	タイムアウト（ミリ秒、デフォルト: 120000）

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool reads from a Markdown file and automatically posts, but lacks details on critical behaviors: authentication requirements (implied by 'state_path' but not explained), error handling, rate limits, or what happens on failure (e.g., if the file is invalid). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Japanese that front-loads the core action ('記事を公開します') and explains the mechanism. It avoids redundancy and wastes no words, though it could be slightly more structured (e.g., separating key points). Every part of the sentence contributes to understanding the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a mutation tool with 5 parameters, no annotations, and no output schema), the description is incomplete. It lacks information on authentication, error handling, return values, or how it differs from 'save_draft'. While the schema covers parameters well, the description doesn't compensate for missing behavioral and contextual details needed for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema: it implies that 'markdown_path' contains title, body, and tags, but this is already stated in the schema's description for that parameter. No additional semantics or usage context are provided for other parameters, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: '記事を公開します' (publishes an article) on note.com using a Markdown file. It specifies the action (publish), resource (article), and mechanism (reading from Markdown file). However, it doesn't explicitly differentiate from the sibling tool 'save_draft' (which likely saves rather than publishes), though the distinction is implied through the verb '公開' (publish).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool 'save_draft' or any other options, nor does it specify prerequisites (e.g., authentication state) or scenarios where this tool is preferred. Usage is implied only by the action of publishing, with no explicit context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

save_draftB

note.comに下書きを保存します。Markdownファイルからタイトル、本文、タグを読み取り、下書きとして保存します。

ParametersJSON Schema

Name	Required	Description
`markdown_path`	Yes	Markdownファイルのパス（タイトル、本文、タグを含む）
`thumbnail_path`	No	サムネイル画像のパス（オプション）
`state_path`	No	note.comの認証状態ファイルのパス（デフォルト: /app/.note-state.json）
`screenshot_dir`	No	スクリーンショット保存ディレクトリ（オプション）
`timeout`	No	タイムアウト（ミリ秒、デフォルト: 120000）

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states basic functionality. It doesn't disclose behavioral traits like authentication needs (implied by 'state_path'), potential side effects, error handling, or rate limits, leaving significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Japanese that front-loads the core purpose. It could be slightly more structured but avoids redundancy and is appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens on success/failure, return values, or important constraints like authentication requirements, leaving the agent with insufficient context for reliable use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds minimal value by mentioning Markdown file content (title, body, tags) and optional thumbnail, but doesn't elaborate beyond what the schema provides, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('保存します' - saves) and resource ('下書き' - draft) on 'note.com', specifying it reads from a Markdown file containing title, body, and tags. It distinguishes from sibling 'publish_note' by focusing on draft saving rather than publishing, though not explicitly contrasting them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a Markdown file to save as a draft, but lacks explicit guidance on when to use this versus 'publish_note' or other alternatives. It mentions optional parameters but doesn't clarify prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Notipo A
io.github.kfuras
Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.
Workplace & Productivity
12
yuna0x0-hackmd-mcp
ai.smithery
Interact with your HackMD notes and teams seamlessly. Manage your notes, view reading history, and…
Note Taking Developer Tools Content Management Systems
267
GRTwo Docs
io.github.grtwo-jcansler
Publish and share Markdown/HTML docs from AI assistants. Requires grtwo.app Pro. OAuth or API key.
Content Management Systems Documentation Access
2
dochost-mcp A
io.github.zyli5313
Publish Markdown or HTML to a shareable link from your AI assistant. OAuth, no API keys.
Content Management Systems Documentation Access
621

Related MCP Servers

note.com MCP Server
Social Media Content Management Systems Developer Tools
shimayuz
A
license
B
quality
B
maintenance
Enables 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.
Updated 11 days ago (2026-08-24 01:03 UTC)
33
201
29
ISC
xhs-mcp
FrancoSbaffi
A
license
Not graded
quality
D
maintenance
Enables AI agents to automatically publish photo notes to Xiaohongshu (RedNote) using Playwright browser automation. It supports title, body, and image uploads while maintaining persistent login sessions for seamless automated posting.
Updated 6 months ago (2026-03-07 01:44 UTC)
1
MIT
note-post-mcp
Content Management Systems Browser Automation Marketing
nullponull
A
license
A
quality
D
maintenance
MCP server for automating article posting to note.com from Markdown files using Playwright.
Updated 6 months ago (2026-03-17 09:07 UTC)
2
217
1
MIT
note-post-mcp
Content Management Systems App Automation Developer Tools
Go-555
A
license
A
quality
D
maintenance
The 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.
Updated a year ago (2025-10-13 13:51 UTC)
2
217
MIT

Appeared in Searches

Information about playwrights or the Playwright testing framework

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Go-555/note-post-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Note Post MCP

Installation

Prerequisites

Install from GitHub

Install Playwright Browser

Get an authentication state file

Or install from npm (if published)

Setup: Claude Code (CLI)

Setup: Cursor

Other Clients and Agents

Setup: Codex (TOML)

Configuration (Env)

Available Tools

publish_note

save_draft

Markdown File Format

Body Content Details

Example invocation (MCP tool call)

Troubleshooting

References

Name Consistency & Troubleshooting

Consistency Matrix

Conflict Cleanup

Example

License

Available Tools

TDQS

TDQS

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

note.com MCP Server

xhs-mcp

note-post-mcp

note-post-mcp

Appeared in Searches

Latest Blog Posts

MCP directory API