SoundCloud MCP Server
An MCP server that gives an assistant access to the SoundCloud API — search and discovery, your library, playlist management, social actions, and messaging.
README
SoundCloud MCP Server
An MCP server that gives an assistant access to the SoundCloud API — search and discovery, your library, playlist management, social actions, and messaging.
Runs locally over stdio. Public search works with app credentials alone; personal data and writes require a one-time browser login that persists and auto-refreshes its token.
Setup
-
Install dependencies:
npm install -
Create a SoundCloud app at https://soundcloud.com/you/apps and note the Client ID and Client Secret. Set the app's Redirect URI to match your
.env(defaulthttp://localhost:8888/callback). -
Copy the example env and fill it in:
cp .env.example .env -
Build:
npm run build
Authenticate (one time, for personal data)
npm run auth
This opens your browser, captures the OAuth callback automatically, and saves
tokens to ~/.soundcloud-mcp/tokens.json (mode 600). The token auto-refreshes,
so you normally only do this once. Use npm run auth -- --no-browser to print the
URL instead of opening it.
You can also log in from within a client by calling the connect_soundcloud
tool, and check state with auth_status.
Run
Standalone (uses the local .env):
npm start
Claude Desktop
-
npm run buildfirst — Claude Desktop runs the compiledbuild/index.js. -
Open the config file (or Settings → Developer → Edit Config):
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Add the server, using absolute paths and your app credentials in
env:{ "mcpServers": { "soundcloud": { "command": "node", "args": ["/absolute/path/to/soundcloud-mcp/build/index.js"], "env": { "SOUNDCLOUD_CLIENT_ID": "your-client-id", "SOUNDCLOUD_CLIENT_SECRET": "your-client-secret" } } } } -
Fully quit and reopen Claude Desktop (closing the window isn't enough).
Gotchas:
- Paths must be absolute —
~and shell variables are not expanded. - Claude Desktop launches from the GUI, so it may not find a version-managed
node(nvm/nodenv/asdf). If the server won't start, set"command"to the absolute node path fromwhich node(e.g.nodenv which node), such as/Users/you/.nodenv/versions/22.22.0/bin/node. - Run
npm run authonce in a terminal so personal-data tools and writes work; public search works without it. Tokens persist to~/.soundcloud-mcp/tokens.jsonindependent of Claude Desktop, so you don't re-auth per client. - Only set
SOUNDCLOUD_REDIRECT_URIif you changed it from the default; it must match your SoundCloud app exactly.
Other MCP clients work the same way: run node build/index.js with the two
credential env vars set. The npm scripts additionally load a local .env
natively via Node's --env-file-if-exists (no dotenv dependency; needs Node 22+).
Tools
- Auth:
connect_soundcloud,auth_status,sign_out - Discovery:
search_tracks,search_playlists,search_users,get_track,get_user,get_playlist,get_related_tracks,get_stream_url,get_comments - Library (login):
get_profile,get_likes,get_playlists,get_recommended_tracks - Social (login):
like_track,unlike_track,follow_user,unfollow_user,add_comment - Playlists (login):
create_playlist,update_playlist,add_tracks_to_playlist,remove_track_from_playlist,delete_playlist - Messaging (login):
get_conversations,get_conversation,get_messages,send_message,start_conversation,mark_conversation_read
Environment variables
| Variable | Required | Description |
|---|---|---|
SOUNDCLOUD_CLIENT_ID |
yes | App client ID |
SOUNDCLOUD_CLIENT_SECRET |
yes | App client secret |
SOUNDCLOUD_REDIRECT_URI |
yes | Must match the app's redirect URI exactly (default http://localhost:8888/callback) |
SOUNDCLOUD_TOKEN_FILE |
no | Token storage path (default ~/.soundcloud-mcp/tokens.json) |
MCP_DEBUG |
no | Set true for verbose request logging to stderr |
Architecture
config.ts— env + constantstokenStore.ts— persists/refreshes user tokens on diskoauth.ts— OAuth flows (PKCE auth-code, client-credentials, refresh) + browser loginapi.ts— SoundCloud API client, fed an async token providertools.ts—registerAll(server, api): all tools/prompts/resources, transport-agnosticindex.ts— stdio entrypointauth.ts— one-time login CLI
Tool registration is decoupled from the stdio transport, so a future remote
(Streamable HTTP) entrypoint can reuse registerAll without changes.
MCP conventions
Built against the MCP 2025-06-18 spec: tools carry title + behavior
annotations (readOnlyHint/destructiveHint/idempotentHint/openWorldHint),
read tools return structuredContent alongside text, and track/playlist tools
emit resource_link blocks (permalink, artwork, audio stream) so clients can render them.
OAuth is handled locally per the spec's guidance that stdio servers take
credentials from the environment rather than the transport-level OAuth flow
(which is reserved for the future remote HTTP mode).
Notes
Unofficial integration, not affiliated with SoundCloud. Use within the
SoundCloud API Terms of Use.
The legacy /charts endpoint is no longer served by the public API and has been removed.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.