Skip to main content
Glama
RadiusStack MCP Server

RadiusStack MCP Server

by deangoldhill

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RADIUSSTACK_URLYesThe Base URL of the RadiusStack server. Must be an http or https URL; use HTTPS outside a trusted LAN.
RADIUSSTACK_API_KEYYesA dedicated RadiusStack API administrator/key with only the permissions required by the tools you plan to use.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
radiusstack_get_live_statsB

Read current RadiusStack live statistics. Requires reports read permission.

radiusstack_list_usersA

List RadiusStack users. Password fields are removed before results are returned.

radiusstack_get_user_statsA

Read usage and authentication statistics for one RadiusStack user.

radiusstack_create_userB

Create a RADIUS user. This changes RadiusStack. Confirm the requested username and settings before calling.

radiusstack_update_userB

Update selected RadiusStack user settings. This changes RadiusStack. Confirm changes before calling.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a distinct resource and action: live server stats, user listing, per-user stats, user creation, and user update. The two stats tools are clearly separated by scope (global live stats vs. single-user usage/auth stats).

Naming Consistency5/5

All tools use the same radiusstack_ prefix followed by a clear verb_noun pattern. The naming is predictable and consistent across the entire surface.

Tool Count5/5

Five tools are well within the ideal range for a focused RADIUS user-management server. Each tool maps to a meaningful operation and there is no obvious bloat.

Completeness3/5

The set covers listing, creating, updating, and reading stats for users, but lacks user deletion and a direct get-user/profile operation. These are notable lifecycle gaps for a user-management domain and may force workarounds.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues