All MCP Servers
Dev Tools & GitMCP Registrynpm5 toolsA · 83

L2 Calendar MCP server

io.github.Dreiev · Updated

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

At a glance

L2 Calendar is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y l2calendar-mcp`, and declares no required credentials. It exposes 5 tools, including list_servers, get_chronicles and search_servers. It scores A (83/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install L2 Calendar in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install L2 Calendar in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add l2calendar-mcp -- npx -y l2calendar-mcp
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. list_servers, get_chronicles, search_servers). It discovers them automatically.

What tools does L2 Calendar expose? (5)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

  • 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.

What the code can do

Read from the published package source — never executed. Parsed 4 of 4 source files.

This server can make network requests and read your environment variables.

How it was published

  • No provenance attestation — there is nothing linking this published artifact to a specific source commit.
  • 1 npm maintainer — a single point of compromise · last published by dreiev.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 1 month ago — Actively maintained.
  • Repository created 1 month ago — Very new project with little track record yet.
  • 0 GitHub stars — Very little community usage so far.
  • 31 weekly downloads — Very few installs — you would be an early user.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 83

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%99%

    Last commit 40 days ago.

  • Adoption20%17%

    0 stars, 31 weekly downloads.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%100%

    Package and registry entry point at the same repository.

  • Packaging15%100%

    Publishes a pinned version (1.0.0).

Documentation

Full README

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

| 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.

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

Maintain L2 Calendar? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![L2 Calendar on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-dreiev-l2calendar-mcp)](https://mcp-skills-hub.vercel.app/mcps/io-github-dreiev-l2calendar-mcp)

Catalog data refreshed . Something wrong? Report it.