nolicense-nearby-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOLICENSE_API_BASE | No | Optional: the base URL of the No License Nearby API | https://license.nomusicnearby.com |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tracksB | Use this when the user wants to find licensable music by mood, genre, energy, key, or title words. |
| get_trackB | Use this when the user wants the full details of one track. |
| get_preview_urlA | Use this when the user wants to listen to (audition) a track. The URL is for auditioning only; any use of the track in a project requires a license. |
| list_license_tiersB | Use this when the user asks what licenses cost or which license fits their project. |
| quote_licenseC | Use this when the user wants a price estimate for licensing specific tracks for a use. |
| get_license_checkout_linkA | Use this when the user is ready to buy a license for a track. There is no instant checkout: the human requests and pays the license on the No License Nearby website. This tool never submits anything and never takes payment. |
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 6 tools
Each tool targets a distinct step in the music licensing workflow: search, track details, audition, license tier info, price quote, and checkout link. The descriptions clearly differentiate search_tracks from get_track and list_license_tiers from quote_license.
All tools follow a consistent snake_case verb_noun pattern (search_tracks, get_track, get_preview_url, list_license_tiers, quote_license, get_license_checkout_link). No mixed conventions or vague verbs.
Six tools is well-scoped for a music licensing assistant, covering discovery through checkout without redundancy. Each tool earns its place in the workflow.
The surface covers the full user journey from search to preview to license information to quote to checkout link. No critical operations appear missing given the intentional design that transactions happen on the external website.