note-remote-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
note-remote-mcp
An experimental unofficial note.com remote MCP server (TypeScript + Streamable HTTP + Browserbase cloud browser). It aims to support drafts, cover and inline images, hashtags, paid preview boundaries and controlled publishing.
Experimental: The code has not been verified end-to-end with an authenticated note.com account. Browser UI changes can break these tools. This repository is not affiliated with note.com. Do not use with important content without reviewing the result.
MCP connection information (ChatGPT / Codex / Claude / Muse)
This repository contains server source code, not a publicly hosted MCP service. Before connecting a client, deploy this server to your own HTTPS hosting (Node.js 22+ or Docker) and configure its secrets.
Setting | Value | Notes |
MCP URL |
| Replace |
Transport |
| Not stdio or legacy SSE |
HTTP header |
| The token must match the server-side |
Health endpoint |
| Public lightweight status check; not the MCP endpoint |
Authentication | Static Bearer token | OAuth 2.1 is not implemented. If a client requires OAuth and cannot send a custom Bearer header, this implementation will not connect. |
Availability | Not deployed | No working public URL is provided by this repository |
Never put a real access token into Git, a shared configuration, a screenshot or a chat message. Use distinct secrets for Browserbase (BROWSERBASE_API_KEY) and MCP clients (MCP_ACCESS_TOKEN). Each connected client using the same bearer token gets the same note account access. Rotate it if exposed.
1. ChatGPT (web): integration prerequisites
Compatibility warning (current build): ChatGPT cannot use this server's static Bearer-token authentication directly. The ChatGPT custom-server connection currently offers OAuth, unauthenticated, or mixed OAuth/unauthenticated flows rather than arbitrary Authorization headers. Do not remove authentication or publish your access token to make it connect. To support ChatGPT safely, add MCP OAuth 2.1 authentication or place a properly secured OAuth-capable gateway in front of this server.
Additionally, write-enabled custom MCP support in ChatGPT is currently limited to eligible Business and Enterprise/Edu workspaces. A personal Plus plan does not provide the equivalent write-enabled custom MCP access. Consult the current plan requirements before attempting setup.
After the server supports a compatible authentication flow and the workspace allows custom MCP:
Open ChatGPT on the web → Plugins → + → Add custom MCP server.
Name it
note-remote-mcp; set the server URL tohttps://YOUR_HOST/mcp.Configure the supported OAuth authentication (not a static Bearer header).
Review the permissions and create/install the plugin. Refresh its tool list after server updates.
Invoke tools by selecting
@note-remote-mcp. Confirm any write action before execution.
These are future-compatible setup instructions; this repository does not currently include the OAuth server required for ChatGPT web access.
Official: OpenAI: Custom MCP server connection, OpenAI: Custom MCP availability.
2. Codex CLI / IDE
Codex supports HTTP MCP endpoints and environment-sourced bearer tokens. Store a real token in the environment of the process launching Codex, not in Git.
# Supply a strong token securely in your shell/secret manager first.
# The example assumes NOTE_MCP_TOKEN is already exported.
codex mcp add note-remote-mcp \
--url https://YOUR_HOST/mcp \
--bearer-token-env-var NOTE_MCP_TOKENEquivalent ~/.codex/config.toml:
[mcp_servers.note-remote-mcp]
url = "https://YOUR_HOST/mcp"
bearer_token_env_var = "NOTE_MCP_TOKEN"Run codex mcp list or /mcp to check connectivity. Codex's CLI and IDE extension share MCP configuration. No local note/browser server installation is required by the client.
Official: Codex MCP and Config reference.
3. Claude Code (CLI)
Claude Code supports remote Streamable HTTP and custom Authorization headers:
# Assumes NOTE_MCP_TOKEN is already set in the invoking shell.
claude mcp add --transport http --scope user \
note-remote-mcp https://YOUR_HOST/mcp \
--header "Authorization: Bearer ${NOTE_MCP_TOKEN}"
claude mcp listImportant: The CLI may store the expanded token in local Claude configuration. To avoid embedding the token directly, use a private/untracked MCP configuration with environment-variable expansion instead:
{
"mcpServers": {
"note-remote-mcp": {
"type": "http",
"url": "https://YOUR_HOST/mcp",
"headers": {
"Authorization": "Bearer ${NOTE_MCP_TOKEN}"
}
}
}
}Load it as a local/user MCP configuration (for example, a private .mcp.json), not a committed file with real credentials. Inspect status using /mcp in Claude Code.
Official: Claude Code MCP.
4. Claude (claude.ai / Claude Desktop remote connector)
For supported Claude plans, go to Customize → Connectors → Add → Custom/Web (labels vary by client). Enter your own https://YOUR_HOST/mcp. In Request headers, supply Authorization with value Bearer YOUR_MCP_ACCESS_TOKEN, if the UI provides this option. Finish adding the connector and enable it in your conversation.
This is different from the Claude Code CLI configuration. The Claude-hosted connector needs an internet-accessible HTTPS endpoint; it cannot reach localhost. Do not choose an OAuth sign-in flow for this bearer-only server.
Official: Claude remote MCP custom connectors.
5. Muse Code (Meta)
Muse Code declares MCP servers under mcp_servers in its settings JSON. Use the remote streamable_http transport, a URL and headers (not stdio or an executable command):
{
"mcp_servers": {
"note-remote-mcp": {
"transport": "streamable_http",
"url": "https://YOUR_HOST/mcp",
"headers": {
"Authorization": "Bearer ${NOTE_MCP_TOKEN}"
},
"enabled": true,
"mode": "optional"
}
}
}Set NOTE_MCP_TOKEN in the environment running Muse Code; Muse documents ${VAR} interpolation in server settings. Inspect available tools with /mcp. muse mcp login <server> is for OAuth servers and is not applicable to this bearer-only server.
Official: Meta Muse Code — Extending and automating.
Verify connectivity
After deployment, confirm the server answers on HTTPS:
curl --fail https://YOUR_HOST/health
# Expected: {"ok":true,"name":"note-remote-mcp"}The MCP HTTP handler accepts up to 16 MiB per request (including Base64 overhead); a batch of many large Base64 images can exceed this limit. Prefer allowlisted HTTPS image URLs for large batches.
A valid GET /health does not prove the MCP endpoint or authenticated note.com operations work. A 401 from /mcp usually means the bearer token is missing or invalid. Successful tool discovery still does not imply note's current editor UI is compatible.
Related MCP server: note.com MCP Server
Server owner setup
Create a Browserbase project, API key and dedicated persistent browser context for your own note.com account.
Configure server-side secrets using the template
.env.example:BROWSERBASE_API_KEY,BROWSERBASE_PROJECT_ID,BROWSERBASE_CONTEXT_ID,MCP_ACCESS_TOKEN, optionallyIMAGE_ALLOWED_HOSTS. Never commit actual secret values.Keep
ENABLE_PUBLISH=falseuntil draft/cover/body-image/paid-line behavior is verified manually.Deploy the Dockerfile to an HTTPS-accessible container host with a long-lived server process. Ensure
PORTmaps to the host's listening port.Use the cloud-browser Live View for manual note.com login; never supply note passwords directly to the MCP tool.
Connect the clients using the instructions above. Login and publish flows are experimental and may require selector fixes.
Tool overview
MCP tool | Intent |
| Cloud-browser interactive login |
| Validate existing session |
| Save draft with title, body blocks, optional cover |
| Upload article cover image |
| Insert body image |
| Set hashtags |
| Offline validation of free/paid blocks |
| Prepare price and paid boundary for manual review |
| Open review Live View |
| Explicitly confirmed, opt-in publishing |
| Close without publication |
The implementation and browser selectors are not E2E tested with note.com. Client config snippets describe intended integration, not confirmed live connections. Browserbase and hosting may incur usage charges.
Development
npm install
npm run check
npm run build
npm test日本語
本リポジトリは、note.com向けの非公式TypeScript製**リモートMCPサーバー(実験版)**です。ChatGPT / Codex / Claude / Meta Muse Codeの接続設定を上記に記載しました。接続先URLはホスティング完了後に確定します。noteのログイン、記事投稿、トップ画像・本文画像、有料ラインの設定は実アカウントでの動作確認が済んでいません。公開前には必ずご自身で確認してください。
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.
Medium MCP server for ChatGPT, Claude and any AI agent: create post, edit post, cross-post article and get post stats in your own Medium account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Medium yourself; Cotlet does not store your password and you need no Medium API key. About the official Medium API: Medium has an old REST API, but it is no longer supported and Medium does not allow new integrations (checked 11 Oct 2026). Accounts that still hold a token can only create posts, list publications and upload images, with no editing, stats or responses. Setup and FAQ: https://cotlet.dev/integrations/medium-api-mcp-server
Substack MCP server for ChatGPT, Claude and any AI agent: create post, schedule post, publish Note, reply to Notes, send direct message, moderate comments, list subscribers and get post stats in your own Substack account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Substack yourself; Cotlet does not store your password and you need no Substack API key. About the official Substack API: Substack has only a limited API (checked 11 Oct 2026). Its Developer API looks up public creator profiles after approval, and there is no public API to write posts or Notes, manage subscribers or send email. Setup and FAQ: https://cotlet.dev/integrations/substack-api-mcp-server
Publish and share access-controlled Markdown documents from any MCP-enabled AI tool.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables automated publishing and draft saving to note.com platform using Playwright automation. Reads Markdown files with titles, body text, and tags to publish content directly to your note.com account.223 npm58MIT
- AlicenseCqualityBmaintenanceEnables 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.3436 npm31ISC
- AlicenseAqualityCmaintenanceMCP server for automating article posting to note.com from Markdown files using Playwright.22MIT
- AlicenseAqualityDmaintenanceThe 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.2MIT