Skip to main content
Glama
asyntai

@asyntai/mcp

Official
by asyntai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @asyntai/mcp

No user-submitted related servers found.

    Related Servers

    • mcp-remote

      abluva
      A
      license
      Not graded
      quality
      A
      maintenance
      Bridge 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.
      28 npm
      54
      MIT

    • mcp-auth-proxy

      manio143
      F
      license
      Not graded
      quality
      D
      maintenance
      Bridges stdio-based LLM harnesses to OAuth-protected remote MCP servers via Streamable HTTP, handling PKCE browser login and token refresh automatically.
      3 npm
      -
    • @opsmaxx/mcp by OpsMaxx

      @opsmaxx/mcpofficial

      OpsMaxx
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      77 npm
      MIT

    • FastMCP Remote Proxy

      shahil04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local MCP clients to access tools from a remote FastMCP server over stdio, handling OAuth authentication and Streamable HTTP communication.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 54 tools

    Disambiguation4/5

    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.

    Naming Consistency2/5

    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.

    Tool Count1/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources