Infinite Backlog MCP Server
Related Servers
Alternatives to Infinite Backlog MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate Chromium browsing with Playwright-compatible tools for web research, testing, and routine tasks, including persistent profiles, extensions, proxy-aware regional QA, and humanized input over npm or Docker.280 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to control a visible Chromium browser via Playwright with tools for tabs, page reading, element finding, form input, mouse/keyboard actions, screenshots, console/network inspection, JavaScript execution, viewport emulation, and batched calls.17 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform real Chromium browser automation using Playwright-compatible tools, including persistent profiles, proxies, extensions, and humanized interactions over stdio or Streamable HTTP.280 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate real Chromium browsing with Playwright-compatible tools, supporting web research, testing workflows, persistent profiles, proxies, extensions, and stdio or Streamable HTTP deployment.280 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate real Chromium browsing through Playwright-compatible tools, including humanized interactions, persistent profiles, proxy matching, and npm/Docker or stdio/Streamable HTTP deployment.280 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a Chromium-based browser for web research, testing, and automation with Playwright-compatible tools, persistent profiles, proxy matching, extension loading, and humanized input across local or containerized deployments.280 npmMIT
TDQS
Scored across 50 tools
Most tools target clearly distinct resources and actions, and descriptions explain the boundaries between similar-looking tools such as add_game_to_collection vs add_game_platform_copy and the various set_game_* operations. There is still some potential confusion among the many collection/lists/play-record read tools and the browser-control tools mixed into the same surface.
The set is overwhelmingly consistent snake_case verb_noun naming (list_collection, add_game_to_collection, set_game_progress, remove_play_session, delete_list). Minor deviations like current_url, login, and open_site are readable but not perfectly aligned with the dominant pattern.
Fifty tools is very heavy for an MCP surface, even for a broad backlog-management domain. Many operations are legitimately distinct, but the count likely makes tool selection and schema overhead burdensome for an agent.
The surface covers the domain thoroughly: collection copies, progress, acquisition, tags, ratings, reviews, DLC, play records, playthroughs, sessions, custom lists, wishlist, achievements, stats, and browser/session handling. Obvious lifecycle operations have corresponding create/read/update/delete or equivalent tools.