Libsyn MCP Server

Эпизоды, расписание и статистика для вашего подкаста на Libsyn.

Размещённый MCP-сервер

npx add-mcp 'https://cotlet.dev/mcp/v1/libsyn'

Устанавливается в 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

Libsyn API and MCP server: Let your AI agent publish your Libsyn podcast.

Libsyn has no MCP server and lists API access only on its Professional and Enterprise plans, sold through its sales team, with no public reference or self-serve key (checked 27 Oct 2026). Cotlet runs 14 Libsyn tools hosted on Basic, Advanced and Max, over MCP for agents and REST for scripts.

Episodes, scheduling and stats for your Libsyn podcast. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

What can you automate in Libsyn?

  • Schedule an episode from a file
  • Fix show notes on a whole season
  • Attach transcripts in bulk
  • Renumber seasons and episodes
  • Rank episodes by first 30 days
  • Build the monthly sponsor report

Does Libsyn have an MCP server or an API?

  • FTP on every plan uploads a file and can publish it at once from its ID3 tags. It cannot hold a release for later, edit notes or read stats.
  • The official WordPress plugin, Libsyn Publisher Hub, was closed on 7 Mar 2024 for a security issue and can no longer be downloaded.
  • Zapier, n8n and Pipedream have no Libsyn app (all three pages answer 404). The only documented public endpoints are on the status page.
What you needLibsyn FTPProfessional APICotlet
Upload an audio or video fileYesNot publicYes, from a link
Schedule a release for a set timeNo, publishes at onceNot publicYes, after your OK
Edit show notes on old episodesNoNot publicYes
Downloads by country, app and destinationNoStats API, LibsynProYes, Advanced and up
Plans it works onAllProfessional, EnterpriseAll

Checked 27 Oct 2026. Sources: Libsyn plans and pricing (API on Professional and Enterprise), LibsynPro enterprise podcasting (Stats API), Libsyn Master Terms (9 Sep 2026), WordPress.org: Libsyn Publisher Hub closed

How does Cotlet connect to Libsyn?

  1. Sign in to Libsyn. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your Libsyn password, and no episode reaches a feed until you approve it.

Connect Libsyn 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.

  1. Enable Libsyn for agents. Create a Cotlet account, log in to Libsyn in its Cloud Browser and press Enable for agents.
  2. Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the MCP server or connector settings of your agent.
  3. Confirm who you are. Chat apps send you through a Cotlet sign-in. Code editors, n8n and scripts take an API key from the console.

Libsyn shares the address https://cotlet.dev/mcp/v1 with every other app on your account. Turned Libsyn on after you connected? Refresh the connector and the podcast tools appear.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-libsyn \
  https://cotlet.dev/mcp/v1 \
  --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-libsyn": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-libsyn]
url = "https://cotlet.dev/mcp/v1"
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: libsyn_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: libsyn_write

How to use the Libsyn REST API

Create your Cotlet API key

Create a Cotlet API key with access to Libsyn and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Libsyn in Cotlet and enable it for agents. Account access: Your own Libsyn account (the account owner or a user with publishing rights).

Make your first Libsyn API request

REST:

curl https://cotlet.dev/api/v1/libsyn/shows \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read shows 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": "libsyn",
  "tool": "list_shows",
  "result": {
    "shows": [
      {
        "show_id": "412907",
        "title": "The Solo Founder Show",
        "plan": "Advanced"
      },
      {
        "show_id": "518344",
        "title": "Founder Shorts",
        "plan": "Basic"
      }
    ]
  }
}

Returns every podcast your Libsyn account can open, with its show ID, title and plan. Use the show_id from each item as the show_id parameter of the other tools.

If you have one show, the other tools default to it.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Libsyn workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestEpisodes of a show, newest first, with status, release date and ad count. Use list_episodes in your configured content report.
MakeHTTP > Make a requestDownloads in the first 7, 30 and 90 days, all time, and per day for a date range. Use get_episode_stats in your configured content report.
Python or Node.jsREST APIDownloads split by country, listening app or publishing destination. Advanced Plan and higher. Use get_downloads_breakdown 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 Libsyn; 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.

Libsyn API endpoints and MCP tools

Shows and episodes

Drafts, scheduled and published episodes, 100 a page. With one show on the account, every tool picks it by default.

  • List shows (list_shows, read): Podcasts in your Libsyn account with show ID, title and plan.
  • List episodes (list_episodes, read): Episodes of a show, newest first, with status, release date and ad count.
  • Get episode (get_episode, read): Title, description (show notes), status, release date, season, episode number, type, rating, author and media file info.

Upload, draft, schedule and publish

Uploads count toward your plan's monthly hours. A show's first episode must go out at once; scheduling works from the second.

  • Upload media file (upload_media, write): Add an audio, video or PDF file to your media library from a URL. Nothing is published.
  • Create episode draft (create_episode, write): New episode saved as a Draft. Nothing reaches listeners until you schedule or publish it.
  • Schedule episode (schedule_episode, write, asks first): Release a draft at a set time to every destination your show is connected to.
  • Publish episode (publish_episode, write, asks first): Publish a draft now to every destination your show is connected to.

Show notes, numbering and transcripts

Edits on a published episode change the RSS feed. Transcripts go in as SRT or VTT only.

  • Update episode (update_episode, write, asks first): Change the title, show notes or details of a draft or published episode; the RSS feed updates.
  • Bulk edit episodes (bulk_edit_episodes, write, asks first): Set author or season on many episodes at once and renumber them in order.
  • Upload transcript (upload_transcript, write, asks first): Attach an SRT or VTT transcript; Libsyn adds it to the feed for Apple Podcasts and other apps.

Downloads and exports

IAB downloads by default. Country, app and destination splits and the Stats Export need the Advanced plan or higher.

  • Get show stats (get_show_stats, read): Show downloads: all time, this week, this month, and per day for a date range.
  • Get episode stats (get_episode_stats, read): Downloads in the first 7, 30 and 90 days, all time, and per day for a date range.
  • Get downloads breakdown (get_downloads_breakdown, read): Downloads split by country, listening app or publishing destination. Advanced Plan and higher.
  • Export stats report (export_stats_report, read): Stats Export as a download link: one file per report, zipped. Advanced Plan and higher.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/libsyn-api-mcp-server#tools

Who can see my Libsyn session, and how do I revoke it?

  • What we store. Your logged-in Libsyn profile, AES-256-GCM encrypted, in Finland. Not your password.
  • What your agent gets. The 14 Libsyn tools. Never the cookie or your FTP password.
  • What the session sees. What your Libsyn user sees: shows, drafts, notes and stats.
  • What no tool touches. Billing, plan, ad settings, destinations, users, deletes.
  • If Libsyn logs you out. We email you a link to log in again. We never type your password.
  • How to cut access. Disable for agents, reset the browser or delete the API key.

Our site has A+ grades on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.

Is it against Libsyn's terms? Account safety

Customer will not: ... use any robot, spider, data scraping, extraction tool or similar mechanism with respect to the Libsyn Platform

Libsyn Master Terms, section 5.1(g), 9 Sep 2026

An agent working in your Libsyn login fits those words, and the same terms let Libsyn suspend or throttle an account it sees as a "platform" or "policy risk". Section 7 also bans bots and headless browsers that inflate downloads; our tools read stats and never play an episode. We found no public case of a Libsyn account closed for automation (checked 27 Oct 2026).

How we keep your account looking like you:

  • Your own Libsyn login, entered by you
  • One Cloud Browser with its own IP and cookies
  • Releases, edits and transcripts wait for your OK
  • No tool deletes an episode or plays one
  • If Libsyn objects, we pause the Libsyn tools for everyone within 24 h

Edits to a whole back catalog change your feed many times. Run them in batches of a season, not all 300 episodes in one evening.

What happens when Libsyn changes?

  • 12 h between tests of the Libsyn reads and drafts
  • 24 h between tests of releases listeners would get
  • $0 for a call to a Libsyn tool paused for repair

When Libsyn reworks the episode form or the Stats page, the fix happens on our side. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Checks the slot. Another episode at that time or number stops the run.
  2. Uploads and drafts. The file, notes, season and number go into a draft.
  3. Waits for your OK. The release time shows up in your Cotlet console.
  4. Reports the link. Episode URL, release time and the next free slot.
ActionUndo
Upload a fileDelete it by hand; it still counts toward the month's hours
Create a draftDelete it in Libsyn, nobody saw it
Schedule a releaseMove or cancel it before the time
Publish nowNo, apps that refreshed the feed keep it
Edit notes or numbersOnly by editing it back by hand
Attach a transcriptRemove it on the Assets tab

5 of 14 tools ask first: schedule, publish, edits, bulk edits and transcripts, everything that changes your public feed. Uploads and new drafts reach no listener, so they run at once. Turn the wait off per tool for a weekly run.

A release goes to every destination the show is connected to, Apple Podcasts, Spotify and YouTube included, at the same moment.

MCP call:

{
  "name": "schedule_episode",
  "arguments": {
    "episode_id": "38415502",
    "release_at": "2026-10-15T06:00:00-04:00"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/libsyn/episodes/38415502/schedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"release_at":"2026-10-15T06:00:00-04:00"}'

Response:

{
  "episode_id": "38415502",
  "status": "scheduled",
  "title": "Pricing your first product",
  "release_at": "2026-10-15T06:00:00-04:00",
  "url": "https://yourname.libsyn.com/pricing-your-first-product"
}

Cron jobs and scripts call the same tools over REST at /api/v1/libsyn, with one key and one price. A breakdown on a plan below Advanced fails with a plan error and costs nothing. The tools table lists the REST path of each tool.

How much does the Libsyn MCP server cost?

About $13 a month for a weekly show on Libsyn Advanced, 2,200 credits. Libsyn bills your hosting plan as before.

JobCallsCredits
Upload, draft and schedule an episode4 × 4160
Attach the episode transcript2 × 480
Downloads of the newest episode, weekly3 × 4120
Sponsor report by country and app9 × 190
Swap a sponsor link in 12 old episodes25 × 1250
Cloud Browser, 30 days1,500
Total2,200
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No Libsyn Professional plan needed

The month is our example: four weekly episodes on Advanced ($25 a month at Libsyn on 27 Oct 2026), each with a transcript, plus one sponsor link swapped in 12 older episodes. Libsyn charges by upload hours, not downloads, so a bigger audience costs the same. Dollars at the $29 pack rate.

Libsyn MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
GitHubNo Libsyn MCP server. ytechie/libsyn-stat-scraper (6 stars) logs in and downloads the stats CSV.Last push 24 Nov 2016, stats only. The other Libsyn repos last changed between 2017 and 2022.
AuphonicCleans the audio and uploads it to Libsyn over FTP.FTP limits stay: no schedule, no notes edits, no stats.
FunnelPulls Libsyn stats into marketing reports.Reads stats for dashboards; publishes nothing.
Transistor and other hostsOfficial MCP that drafts, schedules, bulk-edits and reads stats. Transistor starts at $19 a month.You move the show, its feed and its stats history off Libsyn.

Pick Auphonic if a clean upload is all you need. Pick another host if you were going to move anyway. Pick Cotlet if the show stays on Libsyn and an agent should do the weekly publishing and the sponsor numbers.

Also listed on: Odel, mcpbeat

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 Libsyn tools go to contact@cotlet.dev.

Libsyn API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Libsyn under Integrations in the console and log in to Libsyn in its Cloud Browser. The trial starts when you sign up and asks for no card.

How do I connect Libsyn to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Libsyn 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 Libsyn account through Cotlet, in their phone apps too.

What can ChatGPT do in Libsyn?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Libsyn: schedule a podcast episode from a file; find your best-performing podcast episodes; update sponsor links in old show notes. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need the Professional plan or an API key?

No. Cotlet works in your own Libsyn account on any plan. Libsyn lists its API only on Professional and Enterprise (checked 11 Oct 2026). Download breakdowns and stats exports need the Advanced Plan or higher, the plans with advanced stats.

Does Cotlet change my Libsyn plan limits?

No. The monthly audio hours come from your Libsyn plan (Basic 3, Advanced 10, Max 55 as listed on libsyn.com/plans-and-pricing, checked 11 Oct 2026), and Cotlet does not change them.

Does Libsyn have webhooks?

No. Libsyn sends no events out, so nothing tells an agent that an episode went live or downloads came in. Run your agent on a schedule instead, for example a Monday list_episodes and get_episode_stats pass.

Can I still use the Libsyn WordPress plugin?

No. WordPress.org closed Libsyn Publisher Hub on 7 Mar 2024 for a security issue, and it cannot be downloaded. The Libsyn tools on Cotlet draft and schedule in Libsyn itself, so nothing runs on your site.

Does the agent work on more than one show?

Yes. list_shows returns every show your Libsyn login can open, and each tool takes a show_id. With one show, the tools pick it on their own.

Is the MCP server different from the REST API?

Only the way in. Both carry the same 14 tools, inputs and answers, one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Libsyn?

No. Cotlet is independent and not affiliated with Liberated Syndication (Libsyn).

Can I use the Libsyn 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.