Back to Directory/Productivity

L2 Calendar

Query Lineage 2 private server openings by chronicle through the public L2 Calendar API.

ProductivityTypeScriptv1.0.0

l2calendar-mcp

MCP server for L2 Calendar — query upcoming Lineage 2 private server openings by chronicle directly from any MCP client (Claude Desktop, Cursor, VS Code, Windsurf, Cline...).

It wraps the free, public, CORS-enabled L2 Calendar API and exposes it as MCP tools.

Tools

ToolWhat it does
list_serversList tracked servers, ordered by VIP status + opening date. Filters: chronicle, only_upcoming, new_only, min_rate, max_rate, limit.
get_chroniclesList every chronicle (slug + display name) to use as a filter.
search_serversFree-text search across name, website, rate, chronicle, description and labels.
get_serverFull public record of one server by exact name (case-insensitive).
list_labelsDistinct labels in use (PTS, Low rate, Craft...) with colors.

Every result is JSON, ready for the model to reason about.

Data source

All data comes from the public API:

  • GET https://l2calendar.com/api/servers — up to 50 servers per call, optional ?chronicle=<slug> filter.
  • GET https://l2calendar.com/api/chronicles — the chronicle catalog.

The API is read-only, requires no key and sends Access-Control-Allow-Origin: *.

Fields returned per server: name, website_url, rate, opening_date, opening_time, opening_datetime_utc, description, is_vip, vip_level, multiproff, multicraft, is_new, chronicle and labels.

Note: the public API returns a single page of up to 50 servers (VIP first, then soonest opening). Tools that filter or search operate on that public page. Increase precision with the chronicle filter.

Install

Remote (HTTP) — no install

When hosted, point your client at the streamable HTTP endpoint:

{
  "mcpServers": {
    "l2calendar": {
      "type": "http",
      "url": "https://<your-host>/mcp"
    }
  }
}

Local (stdio) via npx

{
  "mcpServers": {
    "l2calendar": {
      "command": "npx",
      "args": ["-y", "l2calendar-mcp"]
    }
  }
}

Local (stdio) from source

git clone https://github.com/Dreiev/l2calendar-mcp.git
cd l2calendar-mcp
npm install
npm run build
{
  "mcpServers": {
    "l2calendar": {
      "command": "node",
      "args": ["/absolute/path/to/l2calendar-mcp/dist/index.js"]
    }
  }
}

Run the HTTP transport

node dist/index.js --http            # http://127.0.0.1:8787/mcp
node dist/index.js --http --port 9000

GET /health returns { "status": "ok" } for uptime checks.

Configuration

VariableDefaultPurpose
L2CALENDAR_API_URLhttps://l2calendar.comBase URL of the L2 Calendar instance to query.

Example prompts

  • "List the Interlude servers opening soon."
  • "Which Classic servers are new this week?"
  • "Search for High Five servers with rate x1000."
  • "Show me every chronicle L2 Calendar tracks."
  • "Get the details of the server named L2Hispano."

Development

npm install
npm run build      # tsc -> dist/
npm run dev        # run src/index.ts directly (Node >= 22)
npm run start:http # build output over HTTP

About L2 Calendar

L2 Calendar is a multilingual (EN/ES/PT/RU) calendar and tracker of Lineage 2 private server openings by chronicle — l2calendar.com.

License

MIT © Dreiev

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y l2calendar-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-dreiev-l2calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "l2calendar-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

l2calendar-mcpnpm

Compatible MCP Clients

L2 Calendar works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More