backloggd-mcp
Related Servers
Alternatives to backloggd-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA read-only MCP server that enables AI assistants to access a user's Steam library, playtime, achievements, friends, wishlist, and store data for backlog analysis, game recommendations, discount monitoring, and play-activity summaries.-
- AlicenseAqualityBmaintenanceAn MCP server that connects AI assistants to the Steam Web API and storefront, enabling game library analysis, mood-based backlog recommendations, wishlist evaluation, and storefront searches.814 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server that exposes your Steam, Epic Games Store, and IGDB game data as tools, enabling game library queries, install status checks, and metadata enrichment.122MIT
- AlicenseAqualityBmaintenanceMCP server enabling AI assistants to search Steam games, retrieve official store metadata, and analyze player review sentiment via public Steam Storefront JSON APIs without an API key.36 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to search and query your LaunchBox game library across all platforms including Steam, GOG, and emulators. It allows users to check ownership for bundles, view game metadata, find duplicates, and analyze playtime statistics through natural language.3MIT
- FlicenseNot gradedqualityCmaintenanceA comprehensive MCP server that enables users to interact with Letterboxd for searching films, viewing member data, and performing actions like rating or reviewing movies. It supports private data access and automated browser actions for managing watchlists, diaries, and custom lists.1-
TDQS
Scored across 45 tools
Tool purposes are mostly distinct and clearly described. Some pairs like get_game_lists vs get_lists or check_games vs query_library have overlapping concepts, but their descriptions and parameters make them distinguishable. The high number of tools introduces some potential confusion, but each has a unique role.
Tool names follow a consistent verb_noun pattern (e.g., add_favorite_game, get_user_profile, delete_list). Even the outlier backloggd_whoami fits the overall style of a self-descriptive command. There is no mixing of conventions or chaotic naming.
At 45 tools, this is well beyond the 'heavy' threshold of 25. While the Backloggd domain is broad, many tools could be consolidated (e.g., combining shelf/rating/review setters into a single log editor, merging query/check/find variants). The large surface area is likely to overwhelm agents.
The tool set covers nearly all core Backloggd workflows: game discovery, library management, ratings, reviews, play sessions, lists, social interactions, and account utilities. Confirmation flows for destructive actions are also present. There are no obvious dead ends; every tool needed for typical use cases exists.