MCP Server

Put your library in reach of your AI agents.

Alwayssound ships with a local MCP server you can turn on to support agentic workflows — letting assistants like Claude, ChatGPT, and Gemini read and act on your music library right from your machine.

Claude ChatGPT Gemini Any MCP-capable agent

Alwayssound running

Keep the desktop app open — the MCP server runs locally alongside it and stops when the app quits.

Server enabled

Turn on the MCP server in Settings → MCP and copy your access token from that panel.

An MCP client

Any agent that speaks the Model Context Protocol — Claude Desktop, ChatGPT, Gemini, or your own.

Connect any agent

Generic connection

Every MCP client connects a little differently, but they all need the same two things: the address of the Alwayssound server and a bearer token that authorizes access. Point your client at the local endpoint below.

Enable the server

Open Alwayssound and go to Settings → MCP. Flip the server on. Alwayssound starts listening on your machine at the address below.

server endpoint

http://127.0.0.1:5150/mcp

Copy your access token

In the same MCP settings panel you'll find a bearer token. This authorizes your agent to reach the server. Keep it private.

Configure your client

Add Alwayssound as a remote MCP server in your agent, using the endpoint above and sending your token in an Authorization header:

request header

Authorization: Bearer {BEARER_TOKEN}

Replace {BEARER_TOKEN} with the token from the app. Clients that only speak stdio can bridge to the HTTP endpoint with mcp-remote — see the Claude example below for the exact form.

Claude Desktop

Connect Claude

Claude Desktop reads its MCP servers from a config file. Add Alwayssound to the mcpServers block and restart Claude — Alwayssound's tools appear in the tools menu.

Open your Claude config

In Claude Desktop, open Settings → Developer → Edit Config. This opens claude_desktop_config.json in your editor.

Add the Alwayssound server

Add the mcpServers property below. If it already exists, add the alwayssound entry inside it.

claude_desktop_config.json

"mcpServers": {
  "alwayssound": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "http://127.0.0.1:5150/mcp",
      "--header",
      "Authorization: Bearer {BEARER_TOKEN}"
    ]
  }
}

Replace {BEARER_TOKEN} with the token shown in the MCP instructions inside the Alwayssound app (Settings → MCP). Keep the surrounding quotes and the word Bearer.

Restart Claude

Save the file and fully quit and reopen Claude Desktop. Alwayssound's tools show up in the tools menu — ask Claude about your library and it can read and act on it. Keep Alwayssound running while you work.

Good to know

About your access token

The server binds to 127.0.0.1, so it's only reachable from your own machine — nothing is exposed to the internet. Your token authorizes local agents to reach it. If you ever want to cut off access, rotate the token or switch the server off in Settings → MCP, and existing connections stop working immediately.

Your library, in reach of your agents

Ready to build agentic workflows.

Turn it on in Settings → MCP.