LiquidSoapMCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_versionA | Get the LiquidSoap version this server supports (2.4.0) |
| get_documentationB | Fetch a specific section of the LiquidSoap 2.4.0 documentation |
| search_functionsA | Search for functions or operators in the LiquidSoap API reference |
| get_changelogA | Get the changelog and breaking changes for LiquidSoap 2.4.0 |
| get_examplesA | Get code examples for common LiquidSoap tasks |
| list_sectionsA | List all available documentation sections with descriptions |
| validate_script_syntaxA | Provide basic syntax validation and best practices for a LiquidSoap script |
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 7 tools
Each tool has a clearly distinct purpose: version info, changelog, documentation sections, function search, examples, section listing, and script validation. Even list_sections and get_documentation have a natural complementary relationship without overlap.
All tool names follow a consistent verb_noun snake_case pattern (get, list, search, validate), with no mixing of conventions or vague verbs. The naming is predictable and readable.
7 tools is well-scoped for a documentation and validation server. Each tool earns its place, covering the core use cases without redundancy or bloat.
The tool surface covers the domain comprehensively: version, changelog, documentation access, function lookup, examples, section navigation, and script validation. There are no obvious dead ends or missing operations for the stated purpose.