Hyperagent MCP
Related Servers
Alternatives to Hyperagent MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that wraps agent-browser to let LLMs control a real browser, providing tools for navigation, interaction, reading page content, accessibility snapshots, screenshots, and session management.1-
- AlicenseBqualityFmaintenanceMCP server that drives chatgpt.com via web UI automation using a session token, enabling long-running tasks, deep research, and image generation.9142 npm2MIT
- AlicenseNot gradedqualityNot gradedmaintenanceA Playwright-based MCP server that exposes a live browser as a traceable, inspectable, debuggable and controllable execution environment for AI agents.5,222 npm57-
- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents drive the locally installed Chrome or Edge, opening pages, taking compact accessibility-tree snapshots with @e references, and clicking, typing, scrolling, or capturing screenshots. It also exposes multi-account and cross-channel tab switching, tab sync rules, and ad-block/perf statistics.MIT
- AlicenseBqualityDmaintenanceAn MCP server that provides LLMs access to other LLMs438 npm81MIT

agentify-desktopofficial
AlicenseNot gradedqualityDmaintenanceMCP server that enables AI tools to control local browser sessions for ChatGPT, Claude, and other AI services, supporting querying, navigation, file uploads, and artifact management.25 npm574Mozilla Public 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: hyperagent_models lists supported models, and hyperagent_chat handles chat interactions. There is no functional overlap between them.
Both tool names follow a consistent snake_case pattern with the 'hyperagent_' prefix, making them easy to understand and predict.
With only 2 tools, the server feels minimal but still covers the core functionality of listing models and chatting. A few more management tools (e.g., thread listing) would be welcome, but the count is not unreasonable for a focused bridge.
The essential operations (list models, send prompts, manage threads implicitly via thread_id) are covered. Minor gaps include the lack of explicit thread management tools like list or delete threads, but the core workflow is supported.