Skip to main content
Glama
ER:LC MCP

ER:LC MCP

by 1SiDPlayer

ER:LC MCP

An MCP server for the ER:LC Private Server API.

The project exposes ER:LC API v2 through a small set of convenient tools and also includes the documented v1 endpoints for compatibility.

Features

  • API v2 server status

  • players and v2 location data

  • staff

  • queue

  • vehicles and extended v2 vehicle data

  • join logs

  • kill logs

  • command logs

  • moderator calls

  • emergency calls

  • remote server commands

  • API v1 compatibility

  • v1 bans

  • structured API errors and Retry-After handling

Related MCP server: anyapi-mcp

Requirements

  • Node.js 20+

  • an ER:LC private server with the API server pack

  • a private server API key

ER:LC requires the API pack before the private server API can be used.

Setup

npm install
npm run build

Set the key in the environment:

ERLC_SERVER_KEY="your-key" npm start

PowerShell:

$env:ERLC_SERVER_KEY="your-key"
npm start

Never commit a real server key.

Authorizing the computer that runs the MCP

Reading data uses the server key. Remote commands have an additional ER:LC safety check: the source IP must be trusted.

  1. Open the ER:LC Server Owner API Dashboard.

  2. Sign in with Roblox.

  3. Select the private server.

  4. Open Settings.

  5. Add the public IP address of the computer or server that will run this MCP to the trusted IP list.

  6. Add a comment so the rule is easy to identify later.

  7. Save the rule.

After the IP is trusted, that machine can send POST command requests. An untrusted source can receive ER:LC error code 4000.

If the MCP runs on a VPS, Raspberry Pi behind a different internet connection, cloud host, or another machine, authorize the public outbound IP of that machine. Do not enter a local address such as 192.168.x.x.

For a public application used by many unrelated server owners, ER:LC provides a separate public application/global-key authorization system. Do not register a one-server integration as a public application.

Tools

API v2

  • erlc_server

  • erlc_players

  • erlc_vehicles

  • erlc_staff

  • erlc_queue

  • erlc_logs

  • erlc_command

API v1 compatibility

  • erlc_v1_server

  • erlc_v1_players

  • erlc_v1_staff

  • erlc_v1_joinlogs

  • erlc_v1_queue

  • erlc_v1_killlogs

  • erlc_v1_commandlogs

  • erlc_v1_modcalls

  • erlc_v1_bans

  • erlc_v1_vehicles

erlc_command accepts version: "v1" or version: "v2" and defaults to v2.

API v1 is included for compatibility. New integrations should normally use v2 where possible.

MCP client compatibility

The server uses the standard MCP SDK and stdio transport. It is suitable for MCP clients that can launch a local stdio server, including clients in the Claude Desktop, Cursor and developer-tooling ecosystem.

Other MCP-capable applications can use it when they support local stdio servers and allow environment variables to be passed to the process.

This project is different from ER:LC's official documentation MCP. Their hosted MCP exposes documentation search. This project exposes your private server API as callable tools.

See docs/COMPATIBILITY.md for configuration examples and transport notes.

Rate limits

ER:LC applies rate limits per IP/application and may apply tighter limits to individual routes. Clients should respect 429 responses and wait for the full Retry-After period before retrying.

Do not aggressively poll the API. Repeated invalid server keys or ignored rate limits can lead to temporary or longer blocks.

Documentation

  • docs/TOOLS.md: every MCP tool

  • docs/AUTHORIZATION.md: server key, trusted IPs and public applications

  • docs/COMPATIBILITY.md: MCP client compatibility

  • docs/API-COVERAGE.md: v1/v2 coverage

  • docs/DEVELOPMENT.md: development notes

License

MIT. See LICENSE.

ER:LC and Police Roleplay Community are trademarks of their respective owners. This project is unofficial and is not affiliated with Police Roleplay Community.

Available Tools

17 tools
erlc_commandC

Run a private server command through Virtual Server Management. Defaults to API v2.

Inputs: command (required), version.

erlc_logsC

Get selected API v2 log and call collections.

Inputs: join, kills, commands, modCalls, +1 more.

erlc_playersB

List connected players using API v2, including location and wanted data when supplied.

Inputs: no named parameters.

erlc_queueB

Get the current queue using API v2.

Inputs: no named parameters.

erlc_serverC

Get ER:LC API v2 server information. Optional fields can include players, staff, logs, queue, calls and vehicles.

Inputs: queue, staff, players, joinLogs, +5 more.

erlc_staffB

Get current server staff using API v2.

Inputs: no named parameters.

erlc_v1_bansB

Get the API v1 ban list.

Inputs: no named parameters.

erlc_v1_commandlogsD

Get API v1 command logs.

Inputs: no named parameters.

erlc_v1_joinlogsC

Get API v1 join logs.

Inputs: no named parameters.

erlc_v1_killlogsC

Get API v1 kill logs.

Inputs: no named parameters.

erlc_v1_modcallsC

Get API v1 moderator call logs.

Inputs: no named parameters.

erlc_v1_playersC

Get API v1 player list.

Inputs: no named parameters.

erlc_v1_queueC

Get API v1 queue.

Inputs: no named parameters.

erlc_v1_serverC

Get API v1 server status.

Inputs: no named parameters.

erlc_v1_staffB

Get API v1 staff data. This endpoint is deprecated by ER:LC.

Inputs: no named parameters.

erlc_v1_vehiclesC

Get API v1 spawned vehicles.

Inputs: no named parameters.

erlc_vehiclesB

List spawned vehicles using API v2, including extended vehicle data when supplied.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • 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
      80 npm
      1
      Apache 2.0
    • 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
      135 npm
      5
      MIT
    • A
      license
      C
      quality
      C
      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