Freesound MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREESOUND_API_KEY | Yes | Your Freesound API token |
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 |
|---|---|
| freesound.searchC | Search sounds from Freesound |
| freesound.downloadC | Download a sound from Freesound by sound ID |
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 2 tools
The two tools have completely distinct purposes: one is for downloading a specific sound by ID, and the other is for searching sounds based on criteria. There is no overlap or ambiguity between these operations, making it clear when to use each tool.
Both tools follow a consistent naming pattern with the prefix 'freesound.' followed by a verb (download, search) that clearly describes the action. This uniformity makes the tool set predictable and easy to understand.
With only two tools, the server feels too minimal for a comprehensive Freesound integration. While search and download are core operations, obvious gaps like browsing, getting sound details, or managing user content are missing, limiting functionality.
The tool set is severely incomplete for interacting with Freesound. It lacks essential operations such as retrieving sound metadata, listing categories, or handling user authentication, which are necessary for full agent workflows in this domain.