radius-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| radius_docs_search | Full-text search over the official Radius documentation (the source behind https://docs.radapp.io/), covering concepts, guides, tutorials, quick-start, and reference/schema pages. Clones or reuses a local cache on first use (may take a few seconds the first time). Returns matching pages with URLs and snippets. |
| radius_docs_read | Fetches the full content of one Radius documentation page from the local docs cache, returned as clean markdown (front matter stripped). Accepts a full https://docs.radapp.io/... URL, a URL path (e.g. "concepts/recipes"), or a bare slug. Use radius_docs_search first if you do not know the exact page. |
| radius_docs_list | Browses the structure of the Radius documentation. Called with no arguments, lists the top-level sections (concepts, guides, reference, tutorials, quick-start, ...). Called with a section name, lists every page under it with its URL and title. |
| radius_docs_syncA | Pulls the latest changes from the radius-project/docs GitHub repo (the source of https://docs.radapp.io/) into the local cache. Call this if answers seem stale; otherwise the cache is reused as-is across calls. |
| radius_source_searchA | Full-text search over a checkout of radius-project/radius: Go source (pkg/, cmd/), architecture docs and design notes (docs/architecture, eng/design-notes), specs, TypeSpec/Bicep type definitions, and more. If no local checkout is configured, this server clones a shallow copy itself on first use (may take a bit the first time). Use this for implementation details, resource-provider internals, or design rationale that isn't covered in the published docs. |
| radius_source_readA | Reads the full content of one file from a checkout of radius-project/radius by its path relative to the repo root, e.g. "pkg/recipes/engine/engine.go" or "docs/architecture/README.md". |
| radius_source_list | Lists files and subdirectories at a given path in a checkout of radius-project/radius. Called with no arguments, lists the repo root. Useful for orienting before radius_source_search/radius_source_read. |
| radius_source_syncA | Pulls the latest changes from radius-project/radius into this server's managed cache. Only applies when no external checkout was configured (RADIUS_REPO_PATH unset and no sibling radius/ directory); otherwise this is a no-op since your checkout is yours to manage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: searching source code, reading a specific file, syncing source cache, and syncing docs cache. No overlap in functionality.
All tools follow a consistent 'radius_{source|docs}_{action}' pattern with snake_case. The verb 'sync' is used for both sync tools, maintaining uniformity.
Four tools is well-scoped for accessing source code and documentation. It covers search, read, and sync operations without unnecessary bloat.
The set covers search, read, and cache management, but lacks a directory listing tool. However, search can be used to find files by name, mitigating the gap.