Pick your client below. You'll sign in here once to authorize. If your client isn't listed, use Custom provider at the bottom.
Open Claude connector settings →
Paste this URL as the MCP server URL:
https://mcp.remarkdown.org/mcp
remarkdown.Requires a Pro, Max, Team, or Enterprise plan.
Open ChatGPT connector settings →
Paste this URL as the MCP server URL:
https://mcp.remarkdown.org/mcp
Open Settings → Connectors in ChatGPT, then click Advanced settings.
Toggle Developer mode on, then click Create app at the top.
Fill the form, check the consent box, and press Create:
remarkdownSearch and send documents to your reMarkable device.
ChatGPT takes you to an authorization screen — click Authorize.
Wait for the success screen — usually under a minute.
Available in Developer mode on Plus, Pro, Business, Enterprise, and Edu plans.
Open Settings → Connectors → Add custom connector and paste this URL:
https://mcp.remarkdown.org/mcp
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.
claude mcp add --transport http --scope user remarkdown https://mcp.remarkdown.org/mcp
Then run /mcp inside Claude Code and pick remarkdown to authenticate. Drop --scope user if you only want it in this project.
Edit ~/.cursor/mcp.json (or the project's .cursor/mcp.json):
{
"mcpServers": {
"remarkdown": {
"url": "https://mcp.remarkdown.org/mcp"
}
}
}
Open Settings → MCP & Integrations, toggle remarkdown on, and click Needs login.
gemini mcp add --transport http remarkdown https://mcp.remarkdown.org/mcp
Or edit ~/.gemini/settings.json:
{
"mcpServers": {
"remarkdown": {
"httpUrl": "https://mcp.remarkdown.org/mcp"
}
}
}
Inside gemini, run /mcp auth remarkdown to complete sign-in.
codex mcp login fails against remarkdown. The blocker is on Codex's side, and we can't work around it without breaking the MCP spec.
MCP's OAuth 2.1 profile requires clients to send an RFC 8707 resource parameter on the authorize request so the provider knows which MCP server is being authorized. Every other client on this page sends it. Codex doesn't, so our provider rejects the request:
invalid_request: Missing or invalid resource
Tracked upstream:
When Codex ships the fix, point it at this URL:
https://mcp.remarkdown.org/mcp
In the meantime: any other client on this page works, or use the open-source remarkable_rust CLI as an alternative.
If your client supports an OAuth-protected HTTP MCP server, point it at this URL:
https://mcp.remarkdown.org/mcp
Authentication is OAuth 2.1 with Dynamic Client Registration; your client will be redirected here to sign in once. Transport is Streamable HTTP.
First time here?