YotoMCP Local
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOTO_CLIENT_ID | Yes | Your public client ID from the Yoto Developer Dashboard. | |
| YOTO_AUDIO_ROOT | No | Absolute path to the directory containing MP3/M4A files for upload. Required when YOTO_ENABLE_WRITES=true and upload tools are used. | |
| YOTO_ENABLE_WRITES | No | Set to true to enable write operations (create/delete card, upload audio). Disabled by default for safety. | false |
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 |
|---|---|
| yoto_auth_startA | Start Yoto Authorization Code + PKCE login. Open the returned URL, then call yoto_auth_complete. |
| yoto_auth_completeA | Finish the pending local PKCE login after the browser callback arrives. |
| yoto_auth_statusA | Show whether this local server has a Yoto refresh token, without returning the token. |
| yoto_logoutA | Delete the local Yoto token record. This does not call a remote API. |
| yoto_list_cardsA | Read the authenticated user’s MYO cards. No write operation. |
| yoto_get_cardA | Read one MYO card by ID. No write operation. |
| yoto_list_devicesA | Read linked Yoto player names and status. Does not control or modify devices. |
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 7 tools
Each tool has a clearly distinct purpose: auth workflow steps are separate, card operations are get vs list, device listing is unique, and logout is standalone. No two tools could be confused.
All tools use snake_case with a yoto_ prefix, but the auth tools vary in structure (auth_status, auth_complete, auth_start) while others follow verb_noun (get_card, list_cards, list_devices). Minor deviation from a uniform verb_noun pattern.
Seven tools are well-scoped for a local Yoto integration focused on authentication and read-only access. Each tool earns its place without redundancy.
The auth lifecycle (start, complete, status, logout) is fully covered, and read operations for MYO cards and devices are present. Minor gaps include no search/filter for cards and no detailed device inspection, but the core read-only scope is well served.