Skip to main content
Glama

Related Servers

Alternatives to leanpub-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to render Markdown to HTML, estimate page counts, verify document delivery constraints, and atomically ship documents through a zero-dependency JSON-RPC stdio server.
      4
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Zero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.
      10
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to pull live FX and crypto prices, store and read JSON records in a DynamoDB-backed key-value store, and run business calculations such as invoice totals, shipping estimates, and inventory-status checks. It runs over streamable HTTP on AWS Lambda with SigV4-authenticated access, or locally via stdio.
      -
    • F
      license
      A
      quality
      B
      maintenance
      Enables creating and modifying iKAOS Story prototype content, including reading context, saving content with optimistic revision control, and managing images, through a stdio MCP server that talks to the authenticated iKAOS Story API.
      7
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables local MCP access to both Skilljar REST APIs (v1 and v2), reproducing the official 73-tool v2 surface and adding v1-only capabilities such as per-lesson progress, webhooks, asset upload, commerce, learning paths, and instructor-led training. Keeps credentials on your machine via stdio transport.
      112
      110 PyPI
      Apache 2.0

    TDQS

    C2.9/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target distinct actions (get, create, publish, preview) on specific entities. However, the three preview tools (preview_book, preview_subset, preview_single) and the three reader-email tools are closely related, though descriptions sufficiently clarify their different use cases.

    Naming Consistency5/5

    Tool names follow a consistent snake_case verb_noun pattern throughout, such as get_book, create_coupon, publish_course, and wait_for_job. Minor compound names like check_book_exists still fit the established convention without introducing style inconsistencies.

    Tool Count2/5

    With 28 tools, the set exceeds the 25-tool threshold for 'too many.' While the scope spans multiple entity types (books, courses, bundles, coupons, readers, jobs), the count feels heavy, especially since several entities only have creation tools (e.g., create_bundle, create_track), inflating the surface without corresponding coverage.

    Completeness2/5

    The tool surface has significant gaps. Books have create/publish/preview/status transitions, but there is no list_books or update_book. Bundles and tracks only have create operations—no get, update, or delete—and courses lack get/update/delete as well. This incompleteness will force agents to rely on out-of-band knowledge or fail when managing those entities.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues