Skip to main content
Glama
sambt94

remarkable-mcp

by sambt94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to remarkable-mcp

No user-submitted related servers found.

    Related Servers

    • obsidian-ai-curator

      nwant
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude AI direct access to your Obsidian vault, enabling natural language search, note creation, file management, and automated workflows.
      6,209 npm
      9
      MIT

    • vaultrecall-mcp

      AndrewG0R
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that turns an Obsidian vault into a searchable second brain for Claude with meaning-based search, note read/write, and insight reports like contradictions and stale TODOs.
      MIT

    • Personal Memory MCP Server

      tonyRaafat
      F
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server that gives Claude (and ChatGPT/Gemini) persistent read/write access to your own memory: books, games, projects, notes, and freeform facts.
      -

    • obsidian-mcp

      nuuuri
      A
      license
      Not graded
      quality
      D
      maintenance
      Bidirectional MCP server that connects Claude with an Obsidian vault, enabling note management, full-text search, graph traversal, and daily notes operations.
      2,547 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but remarkable_render_document is explicitly a wrapper for remarkable_render_pages with no selection arguments, creating a slight overlap. The descriptions mitigate this by clarifying the relationship, so it's mostly unambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the remarkable_ prefix, such as list_documents, render_pages, and check_status. This makes the tool names predictable and easy to navigate.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its purpose of managing and rendering reMarkable documents. Each tool serves a distinct function (listing, metadata, rendering, status, cleanup) without unnecessary bloat.

    Completeness4/5

    The tool set covers the core lifecycle for reading and rendering documents: listing, retrieving metadata, rendering all or select pages, checking status, and cleaning up. It lacks write operations like upload or delete, but those fall outside the apparent scope of a rendering-focused server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources