Connect Your Server
To clanme
clanme watches your server’s TPS, memory, entities, and player activity around the clock, and alerts you by email, webhook, browser push, or in-game message the moment something breaks. Behind the alerts is a full analytics dashboard, with player retention, session lengths, peak hours, and uptime history, live within 60 seconds of install.
Alerts
Know before your players do
Proactive notifications with server context already included. The email doesn't just say something broke, it tells you which world, which plugin, and what the numbers were at that moment. All four channels are opt-in per server and fire in parallel.
Server offline
No heartbeat for 5 minutes. Email includes last known TPS, player count, and memory % before silence.
TPS drop
5-minute TPS falls below your threshold (default 14.0). Email names the world with the highest entity count.
Memory pressure
Heap above 90% of max. Includes GC pressure %, entity count, and time to ceiling at current rate.
Entity spike
Any world at 3× its 7-day normal level. Email names the world, count vs average, and current TPS.
Plugin correlation
TPS drops within 5 minutes of a new plugin loading. Email names the plugin and shows TPS before and after.
Death spike
Deaths per hour at 3× your 30-day baseline. Surfaces griefing, mob farm issues, and exploit patterns early.
Player count peak
New all-time concurrent player record. A positive alert, share it with your community.
Weekly retention digest
Every Monday: new players this week, % who returned, vs the same week last month. The most important signal.
Server Health
TPS, memory, and entities, all in one place
Real-time performance metrics logged every 60 seconds. When something goes wrong you'll see exactly when it started, which world caused it, and how it trends over time.
TPS (1m / 5m / 15m)
Logged every heartbeat and charted over time. Know exactly when your TPS started dropping.
MSPT
Milliseconds per tick, the raw lag number. Captures spikes that averaged TPS smooths over.
Heap memory
Used vs. max, with a linear regression projecting estimated time to 90% ceiling.
Entity count per world
Per-world breakdown, not a server-wide average. Identifies the exact world killing your TPS.
Loaded chunks per world
How much of each world is currently loaded. High chunk counts are a common hidden memory drain.
JVM GC pressure
Cumulative garbage-collection pause time between heartbeats. The precursor to stop-the-world lag.
Server health score
A 0–100 composite of TPS stability, uptime %, memory headroom, and entity load. Updated every minute.
Uptime history
Uptime ratio across 24 hours, 7 days, and 30 days, from the same heartbeat stream that powers the offline alert.
Per-world TPS breakdown
TPS and entity load attributed by world. Stop guessing which of your worlds is the culprit.
Players
Real player data, not the SLP sample
The plugin gives you the full player list, not the 12-person cap that SLP polling is limited to. Live counts updated every heartbeat, accurate session timestamps from plugin events.
Live player count
Updated every heartbeat from plugin events, not the cached SLP response polled every few minutes.
Full player list
Every online player by UUID and name. SLP returns at most 12 and can be suppressed entirely by admins.
Just-spotted feed
The 12 most recently seen players with Minecraft heads and timestamps, refreshed every 30 seconds.
Player roster
Everyone spotted in the last 30 days with their last-seen timestamp and cumulative play history.
True session tracking
Exact login and logout timestamps from plugin events, not inferred from the gap between polls.
Session duration
How long each play session lasted, per player. Surface patterns like weekend-only or late-night players.
New player detection
First-ever-seen flag per player based on UUID history. Tells you exactly how many faces are new.
Player profile pages
Per-player page showing every server spotted on, sessions, and first and last seen timestamps.
Deaths & PvP kills
Deaths and PvP kills counted per hour and charted over time. The same data behind the death spike alert, broken out so you can spot patterns yourself.
Chat activity rate
Chat messages per interval as a count only, no content is ever captured. A quiet chat on a full server tells you something too.
Growth
The metrics that tell you if your server is actually growing
Week-over-week data that answers whether players are coming back, sessions are getting longer, and your community is trending upward, or quietly shrinking.
New vs returning ratio
Weekly: how many new players came back for a second session. Most admins are optimising for the wrong thing.
Session length trends
Are average sessions getting longer or shorter week over week? A shortening average is an early warning.
Unique player counts
Daily, weekly, and monthly uniques. Tells you whether you're seeing the same faces or actually growing.
Week-over-week retention
What % of last week's new players returned this week, vs the same comparison period last month.
Peak hour heatmap
Busiest hours of each day across 30 days. Schedule events and maintenance based on your actual community.
30-day player count trends
Peak and average concurrent players charted over the last 30 days. Is your server growing or shrinking?
All-time peak record
Best concurrent player count ever recorded, with the exact timestamp and full player list at that moment.
Configuration
Know what's actually running
The plugin reports what your server is, not just how it performs. Useful when multiple admins touch the server, when a plugin update causes a regression, or when you genuinely can't remember what's installed.
Plugin list
Every loaded plugin with name, version, and when it was last seen in a heartbeat. Owner-only by default, shared publicly only if you opt in via config.yml.
Outdated plugin detection
Versions checked against the latest Modrinth and Hangar releases. See which plugins are behind before you start debugging them.
Server config snapshot
Difficulty, PvP, game mode, view distance, simulation distance, and online mode, captured every heartbeat. Spot the change nobody owned up to.
Restart history
Restart count, last restart timestamp, and mean time between restarts across any date range.
Owner tools
Built for how you actually run a server
Everything above is what the plugin tracks. These are the controls that come with the dashboard, included with every account.
Team access
Invite co-admins with full dashboard access, or read-only viewers who can see every chart but can't touch settings. One email invite, no shared passwords.
Read-only API keys
Generate a key and pull current player count, TPS, memory, and uptime from a JSON endpoint. Built for Discord bots, status pages, and custom overlays.
Private mode
Keep your server out of the directory entirely. Your page lives at a private URL only you can share, and monitoring works the same either way.
Maintenance mode
Restarting on purpose? Set a window from the dashboard and every alert stays silent until it ends. No 3am offline email for a planned reboot.
Getting started
Up and running in three steps
Sign in and add your server
Create your account at clan.me/login with just an email, add your server from the dashboard, and copy the plugin token it generates.
Drop the .jar in your plugins folder
Available on Modrinth, Hangar, and SpigotMC. No ports to open, no firewall changes. Heartbeats go outbound only.
Add your token to config.yml and restart
# plugins/clan_me/config.yml
plugin_token: "your-token-here"
Your dashboard flips to Connected within 60 seconds of the first heartbeat.
The plugin sends outbound heartbeats only, capturing server performance metrics and never storing chat content, only message rate. Player names and UUIDs are linked to public Mojang profiles; players may opt out at clan.me/optout.
Common questions
What versions does the plugin support?
The plugin supports Paper 1.21 and newer. Spigot compatibility is planned.
Does the plugin require open ports?
No. The plugin sends outbound heartbeats only, a POST to clan.me every 60 seconds. Nothing needs to reach your server from outside. Your firewall and network config stay exactly as they are.
How far back does analytics data go?
Raw heartbeat data is kept for 30 days. Hourly aggregates used for charts are kept for 18 months, so your trend history builds the longer you stay connected.
Is player data GDPR compliant?
Yes. Player names and UUIDs are linked to public Mojang profiles. Players can opt out at clan.me/optout for full erasure. See our Privacy Policy for the full Article 17 detail.
Is any of this paid?
No. All analytics features are free. We may introduce optional paid features later, existing free functionality will stay free.
Can I keep my analytics page private?
Yes. Flip your server to private from the dashboard and it disappears from the directory, with your page accessible only at a private URL you control. Monitoring and alerts continue running regardless of visibility.
What's the performance overhead?
Negligible. The plugin runs a single scheduled task every 60 seconds and has no listeners on hot paths like PlayerMoveEvent. The heartbeat POST is async, so it can never block the main thread. Most admins report no measurable TPS impact.
What happens if clan.me is unreachable?
Nothing, from your server's perspective. The plugin queues unsent heartbeats locally and retries silently. There's no blocking timeout and no crash if the connection fails. Your server is completely unaffected.
Does the plugin auto-update itself?
No. It checks for a newer version on startup and logs a single notice to console if one is available, then does nothing else. It never downloads or replaces files on your server.
I use BungeeCord or Velocity. Do I need the plugin on each backend?
Yes, one plugin instance per backend, each with its own token and analytics page. The proxy itself needs nothing installed. Backends are tracked independently, so you get per-server TPS and player data across your whole network.
My server runs in offline mode. Does the plugin work?
Partially. TPS, memory, uptime, and entity data all work normally. Player identity features, session tracking, retention, and the player roster, rely on Mojang UUIDs, which offline mode replaces with locally generated ones, so those metrics will be unreliable.
What exactly does the plugin send?
Performance metrics (TPS, MSPT, memory, entity counts per world, loaded chunks), session join and quit counts, death and PvP kill counts, chat message rate as a count with no content, plugin list, and server config. No IP addresses, no chat content, no player inventory or location data. The full payload schema is documented.
Will players see a message when they join?
Yes. A single line informs players that session data is sent to clan.me. It's required as part of our GDPR and COPPA compliance posture. The exact wording is configurable in config.yml, but it cannot be fully suppressed.
What happens to my data if I uninstall the plugin?
Your analytics history stays accessible on your dashboard for 90 days after the last heartbeat, then it's automatically deleted. Email us if you want an export before then. Reconnecting the plugin at any point resets the 90-day window.
I manage multiple servers. Do I need separate accounts?
No. One clan.me account covers all your servers. Add each server from your dashboard and switch between them from a single login.
Can my co-admins see the dashboard without sharing my login?
Yes. Invite them by email from the dashboard. Co-admins get full access including alert settings, read-only viewers can see every chart but can't change anything or invite others.
Can I pull stats into my own bot or dashboard?
Yes. Generate a read-only API key from your dashboard and query a JSON endpoint for current player count, TPS, memory, and uptime. Keys are per-server, rate-limited, and revocable at any time.
Will I get alert spam during planned restarts?
No. Turn on maintenance mode before you restart, pick a window, and all alert evaluation pauses until it ends. Alerts that would have fired during the window are discarded, not queued.
I already get metrics from my host's panel or Grafana. What's different?
Host panels show you server health: CPU, RAM, whether the process is alive. clan.me tracks player behaviour: who came back, how long sessions last, what hours your community is most active. It also watches for patterns that panels miss, rising entity counts, memory trending toward a ceiling, TPS slowly creeping down, and alerts you before they escalate into something players notice.
My server is already listed on clan.me from polling. What does the plugin add?
Polling gives you a public page, a live player count, and basic uptime. The plugin adds everything polling can't reach: TPS history, session analytics, player retention, entity counts per world, death tracking, proactive alerts, and a private owner dashboard. It's the difference between knowing your server is online and knowing what's actually happening on it.
Full analytics, live in 60 seconds.
Install the plugin and get TPS trends, player retention, session analytics, proactive alerts across four channels, and 18 months of chart history, all free.
Connect your server
Access Owner's Dashboard