-
Fill the connector form with these two values:
Name
MCP server URL
You can leave the advanced settings alone — the defaults work.
-
Click Add, then Connect on the connector card, and sign in here when prompted.
Requires a Pro, Max, Team, or Enterprise plan.
-
Open Settings → Connectors → Add custom connector and paste your connection URL.
If it shows advanced or optional settings, leave them as they are.
Or edit the config file directly:
macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json{ "mcpServers": { "remarkdown": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.remarkdown.org/mcp" ] } } } -
Restart Claude Desktop. A browser window opens the first time to sign you in.
-
Run one command:
claude mcp add --transport http --scope user remarkdown https://mcp.remarkdown.org/mcp -
Inside Claude Code, run
/mcpand pickremarkdownto authenticate.
Drop --scope user if you only want it in the current project.
Full guide: How to connect your reMarkable to Claude →
-
In ChatGPT, open Settings → Plugins, scroll to Developer mode, and turn it on.
Settings → Plugins → Developer mode, then switch it on. -
Press the + button at the top right to open New Plugin. Developer mode has to be on first, or the button will not offer a custom plugin.
-
Fill the form, check the consent box, and press Create:
Name
Connection — keep Server URL selected and paste
- Description:
Search and send documents to your reMarkable device. - Authentication: OAuth.
- Check I understand and want to continue.
The + button, then the filled New Plugin form. - Description:
-
ChatGPT takes you to an authorization screen — click Authorize.
Authorize to grant access. -
That's it. In any chat, press + and pick remarkdown to bring your tablet into the conversation.
Press +, choose remarkdown, then ask.
Available in Developer mode on Plus, Pro, Business, Enterprise, and Edu plans.
-
Add remarkdown to
~/.codex/config.toml:[mcp_servers.remarkdown] url = "https://mcp.remarkdown.org/mcp" -
Sign in:
codex mcp login remarkdown
A browser window opens to authorize. Use a current Codex CLI — older builds couldn't complete OAuth sign-in (they omitted the RFC 8707 resource parameter; fixed upstream).
-
Edit
~/.cursor/mcp.json(or the project's.cursor/mcp.json):{ "mcpServers": { "remarkdown": { "url": "https://mcp.remarkdown.org/mcp" } } } -
Open Settings → MCP & Integrations, toggle
remarkdownon, and click Needs login.
-
Run one command:
gemini mcp add --transport http remarkdown https://mcp.remarkdown.org/mcpOr edit
~/.gemini/settings.json:{ "mcpServers": { "remarkdown": { "httpUrl": "https://mcp.remarkdown.org/mcp" } } } -
Inside
gemini, run/mcp auth remarkdownto complete sign-in.
-
In Notion, open Settings, then Connections. Pick the MCP tab. The first card is Custom MCP. Click it.
Settings, Connections, MCP. Custom MCP is the first card. -
Fill in the form. Leave Authentication on OAuth and Scopes on All, then click Connect.
MCP server URL
Name
The URL is the same for every client. “Notion hasn't reviewed this server” appears for every custom server; it's expected. -
Notion opens a popup on remarkdown and waits, showing “Processing authentication”.
Notion waits here while you finish in the popup. It updates on its own. -
In the popup, sign in to remarkdown if asked, then approve the consent screen. It lists exactly what Notion gets: read documents, push markdown. Click Authorize. The popup closes and the connection is live.
The consent screen. Two permissions, nothing else. Deny closes the popup and nothing is connected.
The connection is per person, not per workspace. Each teammate who wants their own tablet reachable adds it themselves.
Full guide: How to connect your reMarkable to Notion →
-
Open Raycast and type “install”. Pick Install Server from the MCP extension.
Type “install” and choose Install Server (MCP). -
Fill the form with exactly these three values. Copy each one; a stray space breaks it.
Name
Command
Arguments
Leave Icon on MCP, Environment empty, and Description blank or whatever you like. Press Cmd+Enter to install.
Name, command, arguments. Everything else stays as it is. -
A browser window opens on remarkdown. Sign in if asked, then approve the consent screen. It lists exactly what Raycast gets: read documents, push markdown. Click Authorize and go back to Raycast. The requester shows as “MCP CLI Proxy”; that's the mcp-remote bridge acting for Raycast.
Two permissions, nothing else. Deny closes the window and nothing is connected.
The Arguments line is the whole configuration. Nothing else to edit, no JSON file.
Full guide: How to connect your reMarkable to Raycast →
If your client can add a custom MCP server over streamable HTTP, point it at your connection URL:
https://mcp.remarkdown.org/mcpAuthentication is OAuth 2.1 with Dynamic Client Registration — your client redirects here to sign in once. Transport is Streamable HTTP.
Static clients
Most clients register themselves on first connect (OAuth 2.1 with Dynamic Client Registration). Some custom MCP connectors cannot, and ask you for a client ID and secret instead.
For those, create a static client after you sign up: auth.remarkdown.org/account/mcp_clients. Pick a name, add the redirect URL your connector shows you, and paste the ID and secret it gives you into the connector. The connection URL stays the same.