yamtrack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAMTRACK_JWT | No | Static token or JWT for authentication (optional for read-only tools) | |
| YAMTRACK_BASE_URL | No | API base URL. Default http://localhost:8000/api | http://localhost:8000/api |
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 |
|---|---|
| search_mediaB | Search external providers for media by title. |
| get_detailsB | Get metadata for a media item from a provider. |
| list_tracked_mediaB | List the authenticated user's tracked media. |
| get_homeC | Dashboard with in-progress and planning items. |
| get_historyC | Change history for a tracked media item. |
| create_entryB | Start tracking media from an external provider by id. |
| manual_createC | Create a media entry manually (no external provider). |
| update_entryB | Update a tracked media item (status, score, progress, notes). |
| update_progressA | Increase or decrease progress on a tracked item. |
| update_scoreA | Update the score (0-10) of a tracked item. |
| delete_entryB | Delete a tracked media item. |
| sync_metadataC | Re-sync metadata for a media item from its provider. |
| create_episodeC | Mark an episode as watched. |
| get_statisticsC | Aggregated statistics for the authenticated user. |
| get_meA | Get the currently authenticated user. |
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 15 tools
Most tools have distinct purposes, but update_entry overlaps with update_progress and update_score, which could cause confusion. However, descriptions likely clarify the differences.
Tool names mostly follow a verb_noun snake_case pattern (e.g., create_entry, search_media), but 'get_me' deviates slightly and 'manual_create' is adjective_verb. Overall consistent.
15 tools is on the higher end of well-scoped but still reasonable for a media tracking service. Some tools like update_progress and update_score could be merged into update_entry.
Covers core CRUD operations, search, metadata sync, history, statistics, and user info. Missing detailed episode retrieval and discovery features, but core workflow is complete.