MCP server for accessing reMarkable tablet data - sync files, extract text from highlights, and browse your reMarkable cloud
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 17%
Response Time: <1h
First Timer Success: -
SamMorrowDrums/remarkable-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in SamMorrowDrums/remarkable-mcp respond to incoming external pull requests in approximately 0.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 48.8 places SamMorrowDrums/remarkable-mcp in the B tier.
The external contributor pull request merge rate for SamMorrowDrums/remarkable-mcp is 16.7%, based on public PR activity from non-core contributors.
SamMorrowDrums/remarkable-mcp currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in SamMorrowDrums/remarkable-mcp welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/SamMorrowDrums/remarkable-mcp?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (21% approval). Large PRs (>500 lines) take ~0 hours (15% approval). Keep your diff compact for rapid review.
Problem Users want reMarkable notes to flow into an Obsidian vault without manually exporting, naming, and placing each document. Scope Design an opt-in synchronization workflow that can: export selected notebooks or folders into an Obsidian vault preserve stable document identity so repeated runs update rather than duplicate notes map reMarkable folders and useful metadata into predictable Markdown paths/frontmatter detect conflicts and avoid silently overwriting user-edited Obsidian content support a dry-run/report mode before writes Non-goals Page-level “processed” markers on the tablet are tracked separately in #24. Generic PDF/Markdown export is tracked in #27 and should provide reusable primitives. This should not introduce a second independent rendering/OCR pipeline. Acceptance criteria documented sync direction and conflict policy deterministic mapping between reMarkable IDs and vault files incremental sync tests using local fixtures hardware/cloud validation against t
Background remarkable_author (method=draw/add_page/create_document) is currently SSH-only. As of #117 the tool is hidden in cloud and USB-web modes (rather than erroring at call time), because native .rm write-back has only been implemented and device-validated over SSH. This issue tracks extending authoring to cloud mode so cloud users get parity with the other write tools (cloud already supports upload/mkdir/rename/move/delete). Feasibility (from prior research) create_document — Feasible now. It can be built on the existing cloud sync v3/v4 upload primitives (the same path remarkable_upload/mkdir already use) plus the pure-logic notebook builders in notebooks.py / strokes.py. No download-modify-reupload needed because the document is brand new. add_page / draw — Harder. These mutate an existing document, which over cloud means download → modify → re-upload a new generation of the document blob. This is riskier (must preserve the original bytes, append-only stroke compositio
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to SamMorrowDrums/remarkable-mcp, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of SamMorrowDrums/remarkable-mcp acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.7% were successfully merged into the primary branch.
SamMorrowDrums/remarkable-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 48.8 places SamMorrowDrums/remarkable-mcp in the Solid tier.
The external pull request merge rate is 16.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, SamMorrowDrums/remarkable-mcp currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for SamMorrowDrums/remarkable-mcp are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.