Claude & Codex
Music library MCP server
Connect Claude or Codex to MyMusik. Manage tags, folders and playlists, control playback, cut tracks, and import or export music with AI.
Connect Claude or Codex from Insights
Open Insights inside the running MyMusik app. Its route is /insights. The Connect a device card gives you a ready-made prompt with the connection details for this app instance.
- Open MyMusik and go to Insights (/insights). Find Connect a device.
- Choose the shield icon, select the permissions and access duration, then Apply. Read only is a useful starting point for exploring your library.
- Choose Copy AI prompt. On a compact screen, the button may be labeled AI. It creates a fresh, one-use invitation with your selected permissions, separate from the visible QR invitation.
- Paste the prompt into Codex, Claude or another agent with MCP or HTTP tools that can reach your app. Ask it to connect, wait for a verified connection, then describe the music task you want it to perform.
/insights belongs to your MyMusik app, not to this website. Use a version with Copy AI prompt and MCP support. Keep MyMusik running while the agent works.
Control your music app with AI
Manage your music library with AI across the whole workflow: finding tracks, organizing your collection, editing audio and listening. MyMusik’s music MCP server gives your agent access to app operations according to the permissions you choose. Describe the result you want, and the agent can combine several actions for you.
These are example requests, not automatic actions or guaranteed selections. Ask to review a proposed change when you want a checkpoint; permissions determine what the connection can actually do.
Find music without browsing every page
“Find albums by [artist] in my library and show me the tracks.” Let the agent search songs, albums, artists, playlists and app-managed folders, then help you choose.
Keep listening while you work
“Play [playlist], then pause when I ask.” With playback access, an agent can operate the player and queue while you stay in your conversation.
Build a playlist from a conversation
“Suggest 12 tracks from these artists. Show me the selection, then save it as Workday when I approve.” Use the agent to gather tracks and create a playlist with library-editing access.
Manage tags across your library
“Add the Road trip tag to these songs and albums. Keep their existing tags.” Create, rename, assign and remove library tags on supported music items. Use tags to organize a collection around your own categories.
Create and organize nested folders
“Create a Road trips folder with a Summer subfolder and add these albums.” Create, rename and move app folders and their entries. These folders organize library references; your original files stay in place.
Update track and album details
“Show me the tracks with an incorrect album name, then apply the corrections I approve.” Edit supported library metadata and keep names consistent across your collection.
Import, cut and export music with AI
Give your agent a complete music task and let it work through the app’s import, audio-editing and export tools. It can check job progress and report the result in your conversation.
Choose Custom access with the resource groups needed for the whole task. For example, editing audio and creating a song can require both Imports and files and Music library permissions. The app and agent must also support saving or downloading the resulting files.
Import music and follow its progress
“Import the audio from this folder, check the results and tell me which tracks need attention.” Use readable files, folders or supported audio URLs. The sources must be accessible to the device running MyMusik; import settings determine whether tracks are accepted automatically or need review.
Cut, trim or extract a track
“Extract 00:30 to 01:00 from this track as a separate song and keep the original.” Work with precise time ranges to remove a section or create a new track from it. Audio editing requires valid ranges and editable local audio.
Export playlists and audio collections
“Export this playlist as M3U8 and prepare a ZIP of its tracks.” Export playlist references or package songs from albums, playlists and library folders as tagged MP3 audio. ZIP exports support up to 1,000 tracks and require exportable audio. M3U8 files reference media locations, so using them elsewhere requires access to those files or URLs.
Choose how much access to give
Use the shield on the connection card to match access to the task. The app checks the session’s permissions when an operation runs.
Changing the selection does not change an existing session. Copy a new AI prompt and reconnect with the new invitation. Treat the prompt as private access to your app and share it only with an agent you trust.
Read only
Explore and summarize accessible library information without allowing changes. Start here to check the connection and discuss a plan.
Remote playback
Allow the player and queue controls needed to manage listening. This preset also grants read access across the public API.
Library editor
Allow supported changes to tracks, albums, artists, playlists, tags and app folders. Use this for organizing your collection and updating library information.
Import manager
Allow operations on imports, audio editing, archives and files. A workflow that also changes library items may need additional Music library permissions.
Custom access
Combine the Playback, Music library and Imports and files resource groups with the access level your task needs. This lets one agent carry out a workflow across the app.
AI music library management with MCP
MCP stands for Model Context Protocol. MyMusik exposes its documented app operations as tools an agent can discover and use. The agent can look up the controls relevant to your request and get results back from the app.
App control covers exposed API operations within your access. It does not provide general mouse-and-keyboard control of your computer.
Less manual setup
The copied prompt includes the invitation, connection instructions, permissions and recovery steps. You do not have to write an integration for every music task.
More room for the task
The agent can retrieve just the operation details and result fields it needs, and page through larger results. It can avoid loading the whole API catalog into the conversation.
Check a request before applying it
The MCP server can validate a proposed API request without executing it. This checks its arguments and applicable access rules; the actual operation still performs its own checks when it runs.
Keep the connection within reach
The simplest setup is an agent running on the same computer as MyMusik. A remote agent also needs a network route to your running app.
- For another device on your local network, check Settings → Web Server → Allow Remote Access. Copy a fresh prompt after changing the connection setup.
- An agent running in a cloud sandbox cannot reach your computer’s localhost automatically. Run the agent locally or arrange a reachable connection; the copied prompt includes network guidance.
- If an invitation has expired or was already used, copy a new AI prompt. If MyMusik has closed or been suspended, reopen it before trying again.
A few useful details
Can the AI agent control the full app?
It can work across MyMusik’s exposed app features, including library organization, tags, folders, playlists, playback, imports, audio editing and exports. Available operations depend on your installed version, platform and connection permissions. The agent uses the app’s API to carry out tasks; it does not need to click through each screen.
Will this work with every Codex or Claude setup?
The agent needs usable MCP or HTTP tools, permission to make the connection and network access to your app. Pasting the prompt into a text-only chat cannot establish a connection. Ask the agent to verify access before you give it a music task.
Can I use a standard MCP client?
Yes, with the Framework Python 3 stdio connector when it is available. The copied prompt explains pairing with a one-use invitation and generating the client configuration. Choose one pairing method per invitation. This server does not provide automatic HTTP OAuth setup.
Is this the same as MyMusik’s built-in AI voice?
This connection lets an external agent you choose work with MyMusik. The in-app AI voice feature has its own setup. Your external agent’s account, model and billing requirements still apply; AI-powered app operations may also require service access.
Does the music app or the agent need to stay open?
MyMusik’s native server must remain running and reachable. Quitting or suspending the app stops access. The session has an expiry, and reconnecting may require a new invitation. Ending a connection does not necessarily cancel a job already started in the app.
What information can the agent see?
It can request app data permitted by its session. That data is handled by the agent and model provider you use. Read only prevents writes but still allows data to be read. Choose a narrower Custom scope when appropriate and keep invitations and session credentials private.