ER:LC MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ERLC_SERVER_KEY | Yes | Your ER:LC private server API key. Set this environment variable to authenticate with the ER:LC API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| erlc_serverC | Get ER:LC API v2 server information. Optional fields can include players, staff, logs, queue, calls and vehicles. |
| erlc_playersB | List connected players using API v2, including location and wanted data when supplied. |
| erlc_vehiclesB | List spawned vehicles using API v2, including extended vehicle data when supplied. |
| erlc_staffB | Get current server staff using API v2. |
| erlc_queueB | Get the current queue using API v2. |
| erlc_logsC | Get selected API v2 log and call collections. |
| erlc_commandC | Run a private server command through Virtual Server Management. Defaults to API v2. |
| erlc_v1_serverC | Get API v1 server status. |
| erlc_v1_playersC | Get API v1 player list. |
| erlc_v1_staffB | Get API v1 staff data. This endpoint is deprecated by ER:LC. |
| erlc_v1_joinlogsC | Get API v1 join logs. |
| erlc_v1_queueC | Get API v1 queue. |
| erlc_v1_killlogsC | Get API v1 kill logs. |
| erlc_v1_commandlogsD | Get API v1 command logs. |
| erlc_v1_modcallsC | Get API v1 moderator call logs. |
| erlc_v1_bansB | Get the API v1 ban list. |
| erlc_v1_vehiclesC | Get API v1 spawned vehicles. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.