Note Post MCP

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

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

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"}}'

{
  "mcpServers": {
    "note-post-mcp": {
      "command": "npx",
      "args": ["@gonuts555/note-post-mcp@latest"],
      "env": {
        "NOTE_POST_MCP_STATE_PATH": "/path/to/note-state.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"
      }
    }
  }
}

{
  "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

• MCP SDK Documentation
• MCP Architecture
• MCP Server Concepts
• MCP Server Specification
• Playwright Documentation

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