@asyntai/mcp
OfficialRelated Servers
Alternatives to @asyntai/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to connect to remote OAuth 2.0-protected MCP servers through a zero-config stdio-to-Streamable HTTP bridge with automatic discovery, PKCE login, and silent token refresh.393 npm1MIT
- AlicenseNot gradedqualityBmaintenanceBridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.25 npm54MIT
- AlicenseNot gradedqualityAmaintenanceConnects web-based AI chat clients such as Claude, ChatGPT, Grok, and Postman to a local machine through a single OAuth-gated MCP endpoint, so they can build and edit projects, run whitelisted shell commands, search files, inspect databases and local APIs, drive browsers and DevTools, manage background jobs, and control Postman without granting unrestricted shell access. It also supports local IDEs and offline use by connecting directly over localhost.MIT
- AlicenseNot gradedqualityDmaintenanceEnables stdio-only MCP clients to connect to Agent Community's hosted Streamable HTTP MCP server for accessing hosted agents and tools.4 npmMIT
- AlicenseNot gradedqualityDmaintenanceBridges stdio-based LLM harnesses to OAuth-protected remote MCP servers via Streamable HTTP, handling PKCE browser login and token refresh automatically.8 npmMIT

@opsmaxx/mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables stdio-only MCP clients like Claude Desktop to connect to a running OpsMaxx desktop app by relaying messages to its authenticated HTTP MCP bridge, so they receive the same access controls, approvals, secret redaction, and audit logging as HTTP clients.117 npmMIT
TDQS
Scored across 54 tools
Most tools have distinct purposes, but a few pairs like set_data_feed and set_data_feed_max are nearly identical, differing only by plan tier, which could cause misselection. Overall, descriptions clarify intent well enough.
The naming convention is inconsistent: it mixes 'get' and 'list' for reads, 'add' and 'create' for writes, and 'set' vs 'update' for changes. Some tools use singular (get_website) while others use plural (list_websites), and 'ask_ai' stands out as unique.
With 54 tools, this is far beyond the typical 3-15 range and exceeds the 25+ threshold for 'too many'. The sheer number makes the API overwhelming and difficult to navigate, even for a comprehensive chatbot management platform.
The tool set covers many domains (websites, knowledge base, images, products, conversations, analytics, etc.), but lacks update operations for several resources like products, images, and knowledge entries. There is also no delete_website or update_website, leaving noticeable CRUD gaps.