Query Lineage 2 private server openings by chronicle through the public L2 Calendar API.
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.
| Tool | What it does |
|---|---|
list_servers | List tracked servers, ordered by VIP status + opening date. Filters: chronicle, only_upcoming, new_only, min_rate, max_rate, limit. |
get_chronicles | List every chronicle (slug + display name) to use as a filter. |
search_servers | Free-text search across name, website, rate, chronicle, description and labels. |
get_server | Full public record of one server by exact name (case-insensitive). |
list_labels | Distinct labels in use (PTS, Low rate, Craft...) with colors. |
Every result is JSON, ready for the model to reason about.
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
chroniclefilter.
When hosted, point your client at the streamable HTTP endpoint:
{
"mcpServers": {
"l2calendar": {
"type": "http",
"url": "https://<your-host>/mcp"
}
}
}
{
"mcpServers": {
"l2calendar": {
"command": "npx",
"args": ["-y", "l2calendar-mcp"]
}
}
}
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"]
}
}
}
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.
| Variable | Default | Purpose |
|---|---|---|
L2CALENDAR_API_URL | https://l2calendar.com | Base URL of the L2 Calendar instance to query. |
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
L2 Calendar is a multilingual (EN/ES/PT/RU) calendar and tracker of Lineage 2 private server openings by chronicle — l2calendar.com.
MIT © Dreiev
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y l2calendar-mcpMerge 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.
{
"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 referencel2calendar-mcpnpmL2 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.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..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.