TrackTag MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACKTAG_API_KEY | Yes | Your TrackTag API key. Create one at https://tracktag.me/studio → API & MCP. |
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 |
|---|---|
| find_audio_filesA | Find audio files on this machine by (partial) name — searches Downloads, Desktop, Music and Documents. Use this to resolve a file path when the user mentions a track by name (e.g. after dragging a file into chat, which does not reveal its local path). Free. |
| analyze_trackA | Analyze a LOCAL audio file (mp3/wav/flac/aiff/m4a/ogg, up to 15 MB) with TrackTag AI. Returns BPM, key, genres, moods, instruments, energy and 35+ metadata fields. Costs 1 TrackTag credit (model 'core') or 2 ('ultra') from the user's balance; failed analyses are auto-refunded. Needs the file's real path on this machine — if you only know the track's name (e.g. the user dragged a file into chat), call find_audio_files first. For files over 15 MB or already-hosted audio, use analyze_url. |
| analyze_urlA | Analyze audio from a URL (any public or signed https link, up to 60 MB) with TrackTag AI. Same output and credit cost as analyze_track. |
| get_creditsA | Get the user's remaining TrackTag credit balance and API limits. Free. |
| list_recent_jobsA | List the user's recent TrackTag API analyses (id, status, track, credits). Free. |
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 5 tools
Each tool has a clearly distinct purpose: local file search, local file analysis, URL analysis, credit check, and job history. The two analysis tools are differentiated by input type (local path vs URL), avoiding ambiguity.
All tool names follow a consistent verb_noun pattern with lowercase snake_case: find_audio_files, analyze_track, analyze_url, get_credits, list_recent_jobs. No mixing of styles or vague verbs.
Five tools is well-scoped for the server's purpose: it covers file discovery, two analysis entry points, credit monitoring, and job history without unnecessary redundancy.
The core workflows (find, analyze, check credits, list history) are covered. A minor gap is the lack of a way to retrieve full past analysis results beyond the summary in list_recent_jobs, but this is workable.