SoundCloud MCP Server
由你的代理读取 SoundCloud 个人资料中的曲目、评论、消息和播放次数。
托管 MCP 服务器
npx add-mcp 'https://cotlet.dev/mcp/v1/soundcloud'可安装到 Claude Code、Codex、Cursor 等客户端
文档
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
SoundCloud API and MCP server: Let your AI agent look after your SoundCloud.
SoundCloud has a public API but no official MCP server (checked 27 Oct 2026). Since May 2026 any Artist Pro member can create API keys alone; the API uploads, edits tracks and builds playlists. Cotlet runs 10 SoundCloud tools hosted, over MCP for agents and REST for scripts, including reads the API has no endpoint for.
Tracks, playlists, comments and stats for your SoundCloud profile. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with SoundCloud
- Page: https://cotlet.dev/integrations/soundcloud-api-mcp-server
What can you automate in SoundCloud?
- Weekly plays and likes report
- Find new comments to answer
- Check direct messages
- Check a profile before writing
- Tidy genres and tags
- Followers and upload time left
Does SoundCloud have an MCP server or an API?
- The API has no Insights for a period and no direct messages. Its track counts are lifetime totals.
- API keys need Artist Pro, $99 a year in the US. SoundCloud's API Terms also say content read through the API may not be used "as input to any artificial intelligence technology".
- Zapier has 2 triggers and no actions. Make has a SoundCloud app on the same API; n8n has no SoundCloud node.
| What you need | SoundCloud API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Edit track details | Yes, Artist Pro keys | Yes, on your keys | Yes |
| Read comments | One track at a time | One track at a time | One track or all tracks |
| Plays and likes for a period | No | No | Yes |
| Read direct messages | No | No | Yes, read-only |
| Runs with your computer off | Yes, if you host it | Only if you deploy it | Yes, hosted |
Checked 27 Oct 2026. Sources: SoundCloud: Registering your app (Artist Pro required), SoundCloud API guide, SoundCloud Developers: self-serve API keys, SoundCloud OpenAPI file, SoundCloud API Terms of Use, SoundCloud plans
How does Cotlet connect to SoundCloud?
- Sign in to SoundCloud. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
Cotlet never stores your SoundCloud password, and no tool posts, sends or deletes anything.
Connect SoundCloud to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Turn on SoundCloud for agents. Create a Cotlet account, sign in to SoundCloud in its Cloud Browser and press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1/soundcloud in the MCP or connector settings of your agent.
- Allow the connection. Chat apps open a Cotlet sign-in. Code editors, n8n and scripts take an API key from the console.
SoundCloud shares https://cotlet.dev/mcp/v1 with every other app you enable. Turned SoundCloud on after you connected? Refresh the connector to load its tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-soundcloud \
https://cotlet.dev/mcp/v1/soundcloud \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-soundcloud": {
"url": "https://cotlet.dev/mcp/v1/soundcloud",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-soundcloud]
url = "https://cotlet.dev/mcp/v1/soundcloud"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: soundcloud_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: soundcloud_write
How to use the SoundCloud REST API
Create your Cotlet API key
Create a Cotlet API key with access to SoundCloud and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect SoundCloud in Cotlet and enable it for agents. Account access: Your own SoundCloud account (Artist Pro for audience Insights and scheduled releases).
Make your first SoundCloud API request
REST:
curl "https://cotlet.dev/api/v1/soundcloud/tracks?limit=5" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read tracks and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "soundcloud",
"tool": "list_tracks",
"result": {
"tracks": [
{
"track_id": "2148839017",
"title": "Night Drive",
"privacy": "scheduled",
"release_at": "2026-10-16T18:00:00+02:00",
"genre": "House",
"plays": 0,
"likes": 0,
"comments": 0,
"reposts": 0,
"url": "https://soundcloud.com/yourname/night-drive"
},
{
"track_id": "2141120034",
"title": "Harbour Lights",
"privacy": "public",
"release_at": null,
"genre": "House",
"plays": 4210,
"likes": 188,
"comments": 31,
"reposts": 42,
"url": "https://soundcloud.com/yourname/harbour-lights"
}
],
"next_cursor": null
}
}
Lists the tracks on your profile, newest first. Privacy is public, private or scheduled, and scheduled tracks show their release time.
Counts are lifetime plays, likes, comments and reposts; get_insights returns them for a period. Pages hold up to 200 tracks; pass next_cursor back as cursor.
limit: 1 to 200. Default: 50.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
SoundCloud workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Plays, likes, comments, reposts and downloads for a period, for your profile or one track, with top tracks. Use get_insights in your configured content report. |
| Make | HTTP > Make a request | Comments on your tracks, newest first, with author, text, waveform timestamp and whether you replied. Use list_comments in your configured content report. |
| Python or Node.js | REST API | Your direct message threads with the other person, last message and unread state. Use list_conversations in your configured content report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads SoundCloud; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
SoundCloud API endpoints and MCP tools
Tracks and insights
Counts for a period come from get_insights; per-track counts are lifetime totals. update_track changes text fields only, never audio or sharing.
- List tracks (
list_tracks, read): Your tracks, public and private, newest first, with plays, likes, reposts and comments. - Get track (
get_track, read): One track: title, description, genre, tags, sharing, secret link, plays, likes and comments. - Get insights (
get_insights, read): Plays, likes, comments, reposts and downloads of your profile for a time window, and per track. - Update track (
update_track, write): Change the title, description, genre, tags or comment setting of one of your tracks.
Comments and messages
Read-only. Your agent can read comments and direct messages and draft answers, but posts and sends nothing.
- List comments (
list_comments, read): Comments on one of your tracks, or the newest comments on all your tracks. - List conversations (
list_conversations, read): Your SoundCloud message threads, newest first: who, the last message, read or not. - Get conversation (
get_conversation, read): The messages between you and one person, newest first. - Find conversation (
find_conversation, read): Check whether you have already messaged a SoundCloud profile, by its link.
Profiles
Your own profile with upload time left, and any public profile by its link.
- Get profile (
get_profile, read): Your own SoundCloud profile: name, city, bio, followers, tracks, plan and upload time left. - Resolve profile (
resolve_profile, read): Look up a SoundCloud profile by its link: user id, name, city, bio and follower counts.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/soundcloud-api-mcp-server#tools
Who can see my SoundCloud session, and how do I revoke it?
- What we store. Your signed-in SoundCloud profile, AES-256-GCM, kept in Finland. No password.
- What your agent gets. The 10 SoundCloud tools. Not the session cookie.
- What the session sees. Your private tracks and secret links, Insights, comments and DMs.
- What no tool touches. Your plan, payouts, password, uploads, and sending or deleting anything.
- If SoundCloud asks to verify. You type the code yourself. We never do.
- How to cut access. Disable for agents, reset the browser or delete the API key. The next call stops.
cotlet.dev rates A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or outside pentest so far.
Is it against SoundCloud's terms? Account safety
You must not employ any techniques or make use of any services, automated or otherwise, designed to misrepresent the popularity of Your Content on the Platform, or to misrepresent your activity on the Platform, including without limitation by the use of bots, botnets, scripts, apps, plugins, extensions or other automated means to register accounts, log in, add followers to your account, play Content, follow or unfollow other users, send messages, post comments, or otherwise to act on your behalf, particularly where such activity occurs in a multiple or repetitive fashion.
The clause aims at faked plays, follows and engagement, and SoundCloud may suspend an account "with or without prior notice". Automation in your account is a grey area under its words even when it only reads. We found no public case of an account closed for an AI agent or MCP tool (checked 27 Oct 2026).
How we keep your account looking like you:
- One account, yours, signed in by you
- Your Cloud Browser keeps its own IP and cookies
- No comments, messages, follows, likes, reposts or plays: no tool posts or fakes popularity
- Nine of ten tools only read; update_track edits your own track text
- If SoundCloud asks for a check, the call stops and you do it yourself
Reading is not what the clause targets, but it is your account: keep it to the jobs you would do by hand.
What happens when SoundCloud changes?
- 12 h between tests of the SoundCloud tools
- 24 h between tests of the track edit
- 0/14 checks passed on Nov 6, 2026
- $0 for a call to a SoundCloud tool paused for a fix
SoundCloud moved its API to OAuth 2.1 in 2024 and changed its ID fields in 2025 (developer blog), and its web app changes too. A broken tool is ours to fix, and your prompts do not change. status.cotlet.dev checks the site, console and API every 3 minutes.
Edits, undo and mistakes
- Reads the track first. update_track loads the track as saved and sends it back whole with your changes.
- Changes only what you named. update_track sends the fields you gave; the rest stay as saved.
- Leaves sharing alone. Audio, artwork and privacy are not touched.
- Reports back. The track as saved, so you can compare.
| Action | Undo |
|---|---|
| Edit track details | Call update_track with the old values from get_track |
| Read comments, messages and Insights | Nothing changes; reading does not mark a thread read |
| Look up a profile | Nothing changes |
0 of 10 tools ask first. update_track runs at once, because it only edits text on your own track and you can set it back.
No tool posts, sends or deletes. Your agent can draft a reply, and you paste it into SoundCloud yourself.
MCP call:
{
"name": "get_insights",
"arguments": {
"window": "DAYS_30"
}
}
REST:
curl "https://cotlet.dev/api/v1/soundcloud/insights?window=DAYS_30" \
-H "Authorization: Bearer $COTLET_API_KEY"
Response:
{
"window": "DAYS_30",
"totals": {
"plays": 41,
"likes": 5,
"comments": 2,
"reposts": 1,
"downloads": 0
},
"tracks": [
{
"track_id": "2400000001",
"title": "Low Tide",
"plays": 12,
"likes": 2,
"comments": 1,
"reposts": 0,
"downloads": 0
}
]
}
From a script or cron job, the same tools answer over REST at /api/v1/soundcloud, on the same key and price. A failed call is free. The tools table shows the REST path of every tool.
How much does the SoundCloud MCP server cost?
About $14 a month for an artist who checks comments daily and messages and plays weekly, 2,400 credits. Your SoundCloud plan is billed by SoundCloud as before.
| Job | Calls | Credits |
|---|---|---|
| Check new comments, daily | 2 × 30 | 600 |
| Check direct messages, weekly | 3 × 4 | 120 |
| Plays and likes report, weekly | 1 × 4 | 40 |
| Tidy genres and tags | 3 × 2 | 60 |
| Check a profile before writing | 2 × 4 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,400 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No Artist Pro needed for any of the 10 tools
The month is our own example, since SoundCloud publishes no typical artist numbers: two reads of new comments a day, one message check and one plays report a week. Artist Pro costs $99 a year in the US (SoundCloud plans, 27 Oct 2026). Dollars at the $29 pack rate.
SoundCloud MCP server on GitHub, Composio or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| jamiew/soundcloud-mcp | Search, library, playlists, likes, reposts, follows and posting a comment; runs locally or on a Cloudflare Worker you deploy. MIT, last push 23 Oct 2026. | Needs your own Artist Pro API app. Its README notes comments cannot be deleted through the API. |
| David-J-Shibley/soundcloud-mcp and others | Upload, list, update and delete tracks; a few more servers cover playlists and library. 0 to 3 stars each. | Your keys, your machine, your upkeep. No Insights for a period or DMs. |
| Composio SoundCloud toolkit | Hosted, 51 tools on the public API: tracks, playlists, likes, reposts, follows, comment reads. | Same API gaps, and the API Terms bar its content as AI input. |
| Zapier and Make | Zapier: 2 triggers for liked tracks and new tracks from people you follow. Make: upload, update, comment, follow, like. | No Insights, no DMs. |
If you have Artist Pro and only need uploads and playlists from a script, the official API is free and allowed. Pick Cotlet when the agent should read comments, DMs and Insights for a period without you running a server.
Run our SoundCloud MCP server on your own computer
All 10 SoundCloud tools are also public on GitHub, as an MCP server and REST API in Python. It reads your session from your own Chrome, so it needs no Artist Pro app, and you can try it on your account and see how each tool talks to SoundCloud. It is a trimmed version of what runs on cotlet.dev, free to use in your own business.
- Free for personal use, learning and testing
- Runs while your computer is on, signed in through your own Chrome
- You update it yourself when SoundCloud changes
- License Elastic 2.0: free in your own business; ChatGPT, your phone and 24/7 runs need hosted Cotlet
- Code: https://github.com/cotletdev/soundcloud-api-mcp-server
Who runs Cotlet
Behind Cotlet is Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the SoundCloud tools go to contact@cotlet.dev.
SoundCloud API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, find SoundCloud under Integrations in the console and sign in to SoundCloud in its Cloud Browser. The trial starts when you sign up, and no card is asked.
How do I connect SoundCloud to ChatGPT or Claude?
Sign up at cotlet.dev, log in to SoundCloud once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your SoundCloud account through Cotlet, in their phone apps too.
What can ChatGPT do in SoundCloud?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in SoundCloud: weekly plays, likes and reposts report; find new comments to answer; check your direct messages. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need Artist Pro to use SoundCloud with Cotlet?
No. All 10 tools work on a free account without API credentials. get_profile shows upload_seconds_left and your plan. Listener countries, cities and top listeners are Artist Pro screens and are not in these tools.
What can it not do yet?
It cannot send messages, reply to or delete comments, create playlists, upload or schedule tracks, change a track's privacy, or list your audience by country and city. Messages and comments are read-only. SoundCloud blocks those actions in a Cloud Browser, so they are not offered.
Does update_track change my privacy or audio?
No. It changes the title, description, genre, tags and the comments switch of one of your own tracks, and leaves the other fields as they are. Sharing, audio and artwork stay. To undo a change, call update_track again with the old values from get_track.
Do get_insights counts match the Insights page?
The totals for the window are the ones the Insights toolbar shows. The per-track counts are lifetime totals for your first 50 tracks, most played first, not counts for the window.
Why not register my own SoundCloud API app?
You can if you have Artist Pro: since May 2026 the keys are self-service. The API then uploads, edits and builds playlists, but it has no endpoint for Insights for a period or DMs, and its terms bar content read through it as input to AI.
Does SoundCloud have webhooks?
No. The API sends no events, and the 2 Zapier triggers cover only tracks you like and new tracks from people you follow. To check new comments or DMs, run your agent on a schedule with list_comments or list_conversations.
Is the MCP server different from the REST API?
No, only the entry point. Both carry the same 10 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with SoundCloud?
No. Cotlet is independent and not affiliated with SoundCloud Global Limited & Co. KG.
Can I use the SoundCloud API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.