Skip to main content
Glama
RadiusStack MCP Server

RadiusStack MCP Server

by deangoldhill

RadiusStack MCP Server

A stdio Model Context Protocol server for safe, targeted RadiusStack operations.

Tools

Tool

RadiusStack permission

Purpose

radiusstack_get_live_stats

reports read-only

Current live statistics

radiusstack_list_users

users read-only

Paginated users, with passwords redacted

radiusstack_get_user_stats

users read-only

Usage/authentication statistics for one user

radiusstack_create_user

users read-write

Create one RADIUS user

radiusstack_update_user

users read-write

Change selected user properties, including disabled state

The server deliberately does not proxy arbitrary API routes, return user passwords, manage API keys, control HA, restart containers, operate certificates, or delete users.

Related MCP server: unifi-safe-mcp

Install and configure

The scoped npm package will be available after the first release is published. Until then, install from a checked-out repository with npm install and use the node command below.

Create a dedicated RadiusStack API administrator/key with only the permissions required by the tools you plan to use. For read-only monitoring, grant reports: read-only and users: read-only. For user creation/updates, additionally grant users: read-write. Do not use a platform administrator key.

Claude Desktop

Add this to your Claude Desktop MCP configuration:

{
  "mcpServers": {
    "radiusstack": {
      "command": "npx",
      "args": ["-y", "@radiusstack/mcp-server"],
      "env": {
        "RADIUSSTACK_URL": "https://radius.example.com",
        "RADIUSSTACK_API_KEY": "replace-with-dedicated-least-privilege-key"
      }
    }
  }
}

Other MCP clients

Run npx -y @radiusstack/mcp-server as a stdio MCP server, setting RADIUSSTACK_URL and RADIUSSTACK_API_KEY in the client environment. RADIUSSTACK_URL must be an http or https URL; use HTTPS outside a trusted LAN.

Development

npm install
npm test
RADIUSSTACK_URL=https://radius.example.com RADIUSSTACK_API_KEY=... npm start

Publishing

  1. Create the public GitHub repository deangoldhill/radiusstack-mcp-server and push this directory.

  2. Create the public npm organization/scope @radiusstack (or change name in package.json to an available unscoped package name).

  3. Authenticate with the npm account that owns the scope: npm login.

  4. From a clean release checkout, run npm test && npm publish --access public.

  5. Create and push a signed tag such as v0.1.0. The included GitHub Action can publish later tagged releases when an NPM_TOKEN repository secret is configured.

  6. Confirm installation from a clean machine: npx -y @radiusstack/mcp-server --help.

Use semantic versioning. Publish only from a clean, reviewed commit; package contents can be checked before upload with npm pack --dry-run.

Security notes

  • API keys are supplied only through environment variables and are never logged or returned.

  • radiusstack_list_users strips the RadiusStack API's password field before emitting tool output.

  • The MCP tools are intentionally allowlisted and expose no generic request or command-execution capability.

  • MCP clients should require user confirmation for mutations. The creation and update tools are marked as non-read-only.

License

MIT

Available Tools

5 tools
radiusstack_create_userCreate RadiusStack userB

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

Inputs: password (required), username (required), planId, profile, +3 more.

radiusstack_get_live_statsGet RadiusStack live statisticsB
Read-onlyIdempotent

Read current RadiusStack live statistics. Requires reports read permission.

Inputs: no named parameters.

radiusstack_get_user_statsGet RadiusStack user statisticsA
Read-onlyIdempotent

Read usage and authentication statistics for one RadiusStack user.

Inputs: username (required).

radiusstack_list_usersList RadiusStack usersA
Read-onlyIdempotent

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

Inputs: page, search, pageSize.

radiusstack_update_userUpdate RadiusStack userB

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

Inputs: username (required), planId, profile, disabled, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      D
      quality
      D
      maintenance
      Enables read-only, bounded access to UniFi Network appliance health, devices, and active clients through three safe MCP tools with TLS verification and redirect rejection.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely invoke only allowlisted, read-only tools on a local Kali Linux host over an encrypted network with OAuth2 authentication and least-privilege enforcement.
      2
      Apache 2.0