Skip to main content
Glama
1SiDPlayer

ER:LC MCP

by 1SiDPlayer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ER:LC MCP

No user-submitted related servers found.

    Related Servers

    • agenzax-mcp

      Agenzax
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.
      18
      42 npm
      5
      MIT
    • anyapi-mcp by getanyapi-com

      anyapi-mcpofficial

      getanyapi-com
      A
      license
      A
      quality
      B
      maintenance
      Local stdio MCP server for AnyAPI - hundreds of scraping and data APIs behind one key, priced per request in USD.
      10
      30 npm
      1
      Apache 2.0

    • opencode-http-mcp

      xuanpass
      A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients to interact with OpenCode 2.x/3.x servers through direct /api/... HTTP routing and ~85 tools spanning sessions, messages, files, config, providers, projects, input, TUI, and workflows. Runs as a zero-dependency, pure-JavaScript stdio bridge with no SDK or build step.
      85
      MIT

    • discord-mcp

      nesquickwe
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to control a logged-in Discord account through 70+ tools: browsing guilds and channels, sending and reacting to messages, moderating members, managing channels, roles, emojis, and webhooks, plus searching and analyzing captured message history stored in SQLite. Authenticates using tokens already cached by the local Discord client, requiring no bot account or manual token setup.
      133 npm
      MIT
    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

    C2.7/5.0

    Scored across 17 tools

    Disambiguation2/5

    Many tools duplicate the same resource across API v1 and v2 (e.g., erlc_queue vs erlc_v1_queue, erlc_players vs erlc_v1_players), and the aggregate erlc_server overlaps with several specific v2 tools. Descriptions give no guidance on when to prefer one over the other, making misselection likely.

    Naming Consistency4/5

    All tools use the erlc_ prefix in snake_case, with v1 tools marked by v1_ and v2 tools unmarked. This is a predictable pattern, though the absence of an explicit v2 marker is a minor deviation.

    Tool Count3/5

    17 tools is on the heavy side for this domain, and the count is inflated by legacy v1 duplicates alongside v2 equivalents. Consolidation could reduce redundancy while preserving coverage.

    Completeness4/5

    The surface covers server info, players, vehicles, staff, queue, logs, bans, and command execution across two API versions. Minor gaps exist (e.g., no dedicated v2 ban endpoint, no direct moderation actions beyond command), but core workflows are represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources