sfx

by gteuscher

Overview Schema Source Related Servers Score Discussions Admin

Python

Local

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation5/5
Each tool has a clearly distinct role: docs, render, preset render, preset listing, tweak, variations, playback, analysis, and saving presets. The only similar pair—render and render_preset—is disambiguated by input type (inline spec vs. named preset).
Naming Consistency4/5
Most tools follow a consistent sfx_<verb>[_<object>] pattern (render, render_preset, list_presets, save_preset, analyze, play). Minor deviations: sfx_docs and sfx_variations are noun-style rather than verb-based, so the pattern is not perfectly consistent.
Tool Count5/5
Nine tools is well-scoped for a sound design toolkit. Each tool covers a distinct stage of the workflow without unnecessary redundancy or bloat.
Completeness4/5
The surface covers the full design workflow: document, render, tweak, randomize, listen, analyze, and save presets. Minor gaps like deleting or editing presets and managing previous renders are absent but not blocking for core sound design.
Average 3.6/5 across 9 of 9 tools scored. Lowest: 2.8/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 5 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral disclosure burden. It only states that it 'saves' and mentions the source modes, but it does not explain side effects like overwriting, naming conflicts, required authentication, or whether the operation is reversible. This is a significant gap for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, front-loaded with the action and resource. No word is wasted, and it provides the two source modes without unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations, empty schema descriptions, and four parameters with alternative modes, this description is too short to be complete. It does not explain the difference between inline spec, render id, out_dir, or how they interact. The output schema exists, so return value explanation is not needed, but the usage logic and parameter relationships remain unclear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It reveals that 'spec' can be inline or sourced from a render id, but does not map the render id to a specific parameter (sound_id vs out_dir) and leaves 'out_dir' completely unaddressed. The description adds partial meaning but not enough to disambiguate the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (save) and resource (spec to the user preset library), which is specific and understandable. It does not explicitly differentiate itself from sibling tools like sfx_render_preset, but the action of 'saving' to the preset library is distinct enough from rendering or listing presets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, no exclusions, and no context about the scenario in which saving a preset is appropriate. The only implication is that you use it when you want to save a spec, but this is not even made explicit as a condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior itself. It lists measured attributes but does not mention side effects, whether files are written (despite an out_dir parameter), or any operational constraints. The presence of out_dir suggests possible output-file behavior that is left unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely compact and front-loaded with the verb and resource. Each segment adds value, including the pointer to definitions in the cookbook, with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although an output schema exists, the description fails to explain the input parameters or usage context. A new agent would not know what sound_id refers to or what out_dir does, making correct invocation uncertain without external documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it mentions neither sound_id nor out_dir. The phrase 'any WAV' does not clarify what sound_id represents or how the optional output directory is used.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool's action ('Measure') and resource ('any WAV'), and lists specific output metrics. It does not explicitly differentiate from sibling tools, but none of the siblings appear to offer the same measurement capability.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Measure any WAV' implies the tool is for audio analysis, but there is no explicit guidance about when to prefer it over sibling tools or when not to use it. Usage context is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that overrides are applied as a JSON merge patch before rendering, but it does not disclose side effects such as file output, whether the preset is modified, or what the render operation entails beyond its name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single focused sentence with no filler. It front-loads the core action and includes the important override-ordering detail without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema may cover return values, but the description still lacks essential context: what out_dir controls, whether rendering writes files, and how this tool relates to the sibling sfx_render. An agent has enough to guess the basic operation but not enough to invoke it confidently in all cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds useful meaning for 'overrides' by specifying JSON merge patch semantics and implies 'name' selects the preset, but it does not explain 'out_dir' at all, leaving a required-use parameter undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action ('Render') and the resource ('a named preset'), and adds the meaningful option of applying a JSON merge patch of overrides. It does not explicitly differentiate from sibling sfx_render, but the 'named preset' phrasing provides reasonable distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is used when you have a named preset and optionally want to override settings before rendering. However, it provides no explicit guidance about when to choose this tool over siblings like sfx_render, sfx_tweak, or sfx_variations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the output destination ('default audio output') and the id-or-path input flexibility, but it omits other behavioral traits such as blocking behavior, error handling, or side effects beyond playback.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no redundant words. Every clause contributes either the action, the input flexibility, or the purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite the tool's simple surface, the absence of annotations and 0% schema coverage leaves important gaps: out_dir's role, whether sound_id is a path or a preset id, and expected return behavior. The description is too thin for an agent to call the tool with full confidence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds some meaning to sound_id ('by id or path'), but out_dir is entirely undocumented, and the relationship between sound_id and out_dir is unclear. This leaves an agent guessing about a required-or-optional parameter's purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies a specific action ('Play a WAV') and a concrete resource ('by id or path'), with a clear user-facing purpose ('so the user can hear it'). This distinguishes it from sibling tools like sfx_render or sfx_analyze, which suggest file generation or analysis rather than audible playback.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The tool's use case is implied: use it when the user needs to hear a WAV through the machine's default audio output. However, it does not explicitly state when not to use it or name alternatives, leaving the agent to infer routing from sibling tool names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full disclosure burden and does so well: it states the output format, the out_dir resolution order (SFX_OUT_DIR env var or ./out), normalization info, and the warning behavior for a missed loudness target. This is rich behavioral context for an annotation-free tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
One dense, front-loaded sentence that opens with the core purpose before detailing return values and defaults. There is no filler or repetition, and every clause adds information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema covers return values, and the description adds useful semantic interpretation (feature definitions pointing to the cookbook, warning conditions). However, for a complex tool with a nested open-object parameter, the spec input structure is left under-specified; the 'cookbook' pointer partially mitigates but doesn't close the gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds real meaning for out_dir by documenting its default resolution, and hints at spec semantics via the returned features list. But the spec parameter is an open object (additionalProperties: true) and the description never states what fields a SoundSpec requires, leaving a significant gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
'Render a SoundSpec to a 16-bit mono WAV' is a specific verb+resource+output-format statement that clearly states what the tool produces. It lists the returned artifacts (file path, id, features, normalization info, warnings) which disambiguates it from siblings like sfx_analyze or sfx_play, though it never explicitly names a sibling like sfx_render_preset to contrast against.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies workflow context by noting it returns an 'id for later tweaks', signaling it is the primary creation step in a pipeline. However, it provides no explicit when-to-use guidance, no exclusions, and never mentions alternatives such as sfx_render_preset, leaving the agent to infer selection logic.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It usefully discloses that the tool creates N randomized siblings, which variation dimensions are jittered, and the resulting ID naming convention. However, it does not mention file-writing side effects, default output location behavior, or whether existing files may be overwritten.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three dense sentences carry concrete, high-value information with no filler. The most important behavior, output naming, and configurable jitter fields are all front-loaded and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Even with an output schema present, the description leaves a meaningful gap: it is not explicit enough about how to specify the source sound via id, path, or inline spec using the available parameters. The behavior of out_dir and count is also under-specified, which an agent needs to know before invoking a render/generation tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds meaning to 'spec' by listing spec.variation fields and clarifies source references via id/path/inline spec. However, it does not explicitly map those source forms to the actual schema parameters (sound_id vs spec), and it leaves count and out_dir semantics mostly to the schema defaults.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Render'), a clear resource ('randomized siblings of a sound'), and the intended use case ('for engine random containers'). It also distinguishes itself from sibling tools like sfx_render by focusing on sibling variation generation rather than single renders.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description establishes a clear context: generating randomized sibling variants when engine random containers are needed. It does not explicitly name alternatives or state when not to use this tool, but the purpose is distinct enough that an agent can infer appropriate usage from the sibling tool names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden and does a good job disclosing key behavior: JSON merge patch semantics, wholesale list replacement, and the requirement to send the full layers list. It does not mention side effects like overwriting output files, but the core behavioral trait is clearly explained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences with the core operation front-loaded, followed by concrete examples and an important caveat about list replacement. Every sentence adds value and there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the non-obvious merge-patch semantics and list replacement behavior, which is the main complexity of this tool. With an output schema present, return-value documentation is not needed, though a note on when to choose this over sfx_render would make it fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It explains the patch object thoroughly with examples and notes that sound_id can be an id or WAV path, but it never explains the out_dir parameter, leaving one of the three parameters undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action: apply a JSON merge patch to a previous render and re-render. It also distinguishes this from a fresh render by explicitly targeting a previous render by id or WAV path, which separates it from sibling tools like sfx_render.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context of tweaking an existing render is implied through 'previous render', and the examples show what kinds of edits are intended. However, there is no explicit guidance on when to use this tool instead of sfx_render or sfx_variations, and no exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry the safety signal. 'List' is clearly read-only, and 'available presets with a one-line summary' tells the agent what output to expect. It doesn't state 'no side effects' explicitly, but the verb makes that unambiguous for this tool type.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, imperative verb, focus on output detail. Nothing wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only listing with an output schema present, no further information is needed to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters foreseeable from context and the input schema; baseline 4 applies. The description adds no requirements but none are needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States the exact action ('List available presets') and specifies the output detail ('one-line summary of each'). This clearly differentiates it from sibling tools like sfx_save_preset or sfx_render_preset.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it (whenever an agent needs to see what presets exist), but does not explicitly state when to prefer it over siblings or call it before save/render operations. Reasonable but no exclusions or alternatives named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavior disclosure. It explains the output granularity for every section value (compact field list vs full JSON schema vs preset specs) and frames the call as a preliminary read step. It does not explicitly state 'read-only', but the documentation context and the directive to call it before designing make side effects unlikely.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with no filler: the first frames the tool, the second enumerates parameter options in pipe-delimited form, and the third gives a usage directive. Information is front-loaded and each sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter documentation tool with no output schema and no annotations, the description is complete: it defines all possible inputs, what they return, and the recommended invocation order relative to the design workflow.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, yet the description fully documents the single section parameter and enumerates all accepted values ('all', 'schema', 'json_schema', 'cookbook', 'presets') with their exact return scopes. This is excellent compensation for the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the tool as the documentation resource for sound design and enumerates the content sections, making it distinct from the sibling rendering/tweaking tools. It lacks an explicit retrieval verb ('get', 'fetch'), so it falls just short of a perfect clarity score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit when-to-use instruction: 'Call with all once before designing sounds.' It does not list exclusions or alternatives, but the sibling tools are clearly different operations, so no ambiguity remains.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

sfx MCP server – quality and maintenance score on Glama

Copy to your README.md:

[![sfx MCP server – quality and maintenance score on Glama](https://glama.ai/mcp/servers/gteuscher/sfx-api/badges/card.svg)](https://glama.ai/mcp/servers/gteuscher/sfx-api)

Score Badge

Copy to your README.md:

[![sfx MCP server – quality and maintenance score on Glama](https://glama.ai/mcp/servers/gteuscher/sfx-api/badges/score.svg)](https://glama.ai/mcp/servers/gteuscher/sfx-api)