Skip to main content
Glama
OpenRhyme

openrhyme-mcp

Official
by OpenRhyme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openrhyme-mcp

No user-submitted related servers found.

    Related Servers

    • call-copilot

      AnisurRahmann
      A
      license
      Not graded
      quality
      A
      maintenance
      Search and read locally-recorded meeting transcripts over stdio. Read-only, no network. Exposes list_sessions, get_session, and search_transcripts to any MCP client.
      46 PyPI
      7
      MIT

    • Titen

      RamaAditya49
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a drop-in MCP memory server over stdio using a local SQLite store, enabling agents to store, search, and audit memory with provenance, scoped access, and contradiction tracking without requiring API keys, LLMs, or embedding providers.
      142 npm
      15
      Apache 2.0

    • pywel

      RolandSaint
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query a local, offline Crimson Desert knowledge base through stdio MCP, providing versioned entity/claim lookups, bounded search, codebook decoding, and typed responses with provenance context.
      Apache 2.0
    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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: events queries captured activity data, status reports engine/server state, apps lists the allowlist and running apps, and allow_app/deny_app make targeted allowlist changes. There is no functional overlap between any of these tools.

    Naming Consistency4/5

    The read-only tools use noun-style names (events, status, apps) while the mutations use verb_noun style (allow_app, deny_app). This is fairly predictable and readable, though not as uniform as a single verb_noun convention throughout.

    Tool Count5/5

    Five tools is well-scoped for this server's purpose: querying activity events, checking engine status, listing apps, and managing the allowlist. Each tool earns its place without the surface feeling bloated or thin.

    Completeness5/5

    The core workflows are fully covered: retrieve activity data, inspect engine health, view the allowlist, and add or remove apps from it. Since events are an append-only raw log, update/delete operations are not expected here, so there are no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources