The real SourceMod plugins that make a Team Fortress 2 community server actually run well — map rotation, custom weapons, and where to get them, from a decades-old ecosystem.
Team Fortress 2's server-side plugin ecosystem is one of the oldest and most mature in PC gaming — built on SourceMod and Metamod:Source, with over 2,500 community-made plugins available, most distributed as precompiled .smx files through the AlliedModders forums. If you're running a public TF2 server, plugins aren't optional polish — they're how every real community server operates.
The foundation: SourceMod + Metamod:Source
Before any individual plugin, a TF2 server needs two base pieces of software installed:
- Metamod:Source — a plugin-loading layer that sits between the game engine and everything else.
- SourceMod — the actual scripting/plugin framework that runs on top of Metamod, and the thing every plugin below depends on.
Both install by extracting their release archives into your server's game directory — no compilation needed for the base install, only for custom plugins you write yourself. The install order matters: Metamod:Source goes in first since SourceMod depends on it, and both need to match your server's actual engine branch (check the download page for the currently-recommended build rather than grabbing an old link from a years-old forum post, since TF2's engine does get periodic updates that can require a matching Metamod/SourceMod version).
Plugins worth running
TF2's plugin ecosystem breaks down into a few well-established categories, each solving a different real problem for a community server:
- Map management — MapChooser Extended. The standard map-rotation plugin for community servers, adding map voting, nominations, and Rock the Vote (RTV) so players control what's next instead of a static rotation grinding on regardless of what people want to play.
- Weapon and item customization — TF2Items. Lets admins give and modify custom weapons and items server-side, and is a dependency many other popular plugins rely on — custom loadouts, Versus Saxton Hale, and Freak Fortress-style game modes all build on it rather than reimplementing item-granting from scratch.
- Admin and management plugins. SourceMod's built-in admin menu system, extended by various community plugins, handles kicks, bans, map changes and player management without needing raw RCON console access for routine moderation — the difference between a moderator using a menu versus needing console command syntax memorized.
- Stats and player-tracking plugins. Track kills, playtime and other per-player stats across sessions, popular on servers that want leaderboards, rank systems, or reward unlocks tied to activity.
- MvM-specific plugins. A separate category entirely for servers running Mann vs. Machine — wave management, bot behavior tweaks, and MvM-specific economy/currency plugins that don't apply to standard PvP servers at all.
- Quality-of-life plugins. Smaller utilities — a basic team-only radar is a commonly cited example — that improve the moment-to-moment experience without changing core game rules.
Beyond these, SourceMod itself can modify maps at runtime — changing spawn points, adding or removing entities, adjusting item placement — without needing to re-compile the map's .bsp file, which is how a lot of "custom" TF2 servers create unique layouts on stock maps.
Where these plugins actually live
The AlliedModders forums remain the canonical source for TF2 SourceMod plugins — most ship as precompiled .smx files ready to drop into your addons/sourcemod/plugins folder, with source .sp files available if you want to modify one yourself (SourceMod's compiler, spcomp, handles that). With over 2,500 plugins listed there across admin tools, gameplay modes (Versus Saxton Hale, Freak Fortress, prop hunt variants), and MvM-specific utilities, it's worth searching by category rather than browsing the full list — MapChooser Extended and TF2Items alone cover the two most commonly-needed base features for a new server.
Getting your server listed: the GSLT token
A TF2 server needs a Game Server Login Token (GSLT), set as SRCDS_TOKEN in your server's startup config, to appear in the in-game server browser and stay reachable to the public. This is a Steam-account-bound value you generate for free from your Steam account — without it, your server runs fine for people with the direct IP but won't show up for anyone browsing servers in-game.
Sizing your server
- 2 GB RAM / 16 players — a small community server, base SourceMod/Metamod stack plus a couple of light plugins.
- 4 GB RAM / 24 players — our most-picked tier, comfortable running a full plugin stack (map voting, custom items, stats tracking) at a busy player count.
- 6 GB RAM / 32 players — a larger community server running a heavier plugin load with more concurrent players.
Community server culture matters as much as plugins
TF2's longest-running community servers are known as much for their admin culture and server identity (a particular map rotation, a house ruleset, a Discord community around them) as for any specific plugin list. The plugins above are the technical foundation, but a server that becomes someone's regular hangout is usually the result of consistent, fair moderation on top of that foundation — worth keeping in mind if you're building a server you want people to come back to, not just one that technically works.
Nxeon's Team Fortress 2 server hosting runs on NVMe VPS instances at the tiers above, with full SFTP access to drop in SourceMod/Metamod and your plugin list, plus a real place to set your GSLT token so your server actually shows up in-game.
Game server hosting
Deploy in seconds, not weekends
Nxeon · Nxeon editorial
★★★★★ Straight-talking guides from the team that runs the servers.