A
licenseA
qualityB
maintenanceEnables MCP-capable AI clients to control a local computer over stdio with filesystem operations, ripgrep search, shell command execution, and persistent process sessions.
14
MIT
openrhyme-mcp
Officialby OpenRhyme
Related Servers
Alternatives to openrhyme-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search, record, correct, and review the provenance and version history of memories, and to obtain answers composed from guarded context in which private values are replaced by placeholders and resolved locally on the device. Exposes these capabilities through dependency-free tools over stdio.MIT
- AlicenseNot gradedqualityDmaintenanceProvides a stdio MCP bridge for coding agents to query and record engineering knowledge locally, preserving debugging history, failed attempts, and verified solutions.3 npmMIT
- AlicenseNot gradedqualityBmaintenanceSearch and read locally-recorded meeting transcripts over stdio. Read-only, no network. Exposes list_sessions, get_session, and search_transcripts to any MCP client.230 PyPI7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents to access privacy-redacted document reading, deadline tracking, memory, drafting, and privacy-checked model and web-search tools over stdio.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to commit, recall, revise, inspect history, snapshot, diff, and roll back hosted memories through a stdio MCP interface.218 PyPIBusiness Source 1.1
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
ActivityStale
ResponsivenessNo issues