memobot-mcp
Related Servers
Alternatives to memobot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for creating, listing, updating, deleting memos, and managing attachments via the Memos API.1210 npmMIT
- AlicenseNot gradedqualityDmaintenanceUnofficial MCP server that bridges AI assistants with Bee wearable lifelogging data, enabling retrieval and management of conversations, facts, todos, and locations.49MIT
- AlicenseNot gradedqualityBmaintenanceMCP server wrapping a self-hosted mem0 REST API, enabling memory management with deduplication and mention-aware reranked search.MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables AI tools to read Dedao Brain (formerly Get Notes) web notes from a free account, exposing AI summaries, original transcripts, and audio attachment links or downloads, with an accompanying CLI.MIT
- AlicenseAqualityCmaintenanceMCP server for YouTubeTranscript.dev — extract transcripts, manage history, and power AI assistants with YouTube content.541 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Memoo knowledge graph RAG, enabling search, Q&A, graph traversal, and episode management via the Memoo REST API.3 npmApache 2.0
TDQS
Scored across 11 tools
Each tool targets a distinct data type: account info, API key, notifications, recordings (summary vs transcript), usage stats, config, package, and user info. No overlapping purposes, even between similar-sounding tools like get_current_user and get_user_info.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_api_key, list_recordings). The only minor deviation is check_for_updates using 'check' instead of 'get', but it's still a clear verb and fits the pattern.
Eleven tools is well-scoped for an account management and recording information server. Each tool serves a specific purpose without redundancy, and the number feels neither excessive nor insufficient.
The tool set covers all common read operations for account data and recordings. However, it lacks mutation capabilities (e.g., delete recordings, update settings), which may be expected for a full lifecycle. This is a minor gap given the apparent read-only intent.