ER:LC MCP
Related Servers
Alternatives to ER:LC MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.18135 npm5MIT
- AlicenseCqualityBmaintenanceLocal stdio MCP server for VRChat friends, worlds, groups, events, notifications, status, avatars, and VRCX history.73390 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect to Chans through a local stdio bridge, exposing Chans API tools based on the provided API key's scopes.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to manage Discord servers, channels, roles, permissions, messages, threads, webhooks, moderation, and declarative server blueprints through MCP tools over local stdio.MIT

anyapi-mcpofficial
AlicenseAqualityBmaintenanceLocal stdio MCP server for AnyAPI - hundreds of scraping and data APIs behind one key, priced per request in USD.1080 npm1Apache 2.0- AlicenseCqualityCmaintenanceEnables 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.85MIT
TDQS
Scored across 17 tools
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.
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.
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.
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.