Live

Libsyn logo

Libsyn API and MCP server

libsyn.com

Libsyn lists an API only on its Professional and Enterprise plans, sold through contact sales, and publishes no API reference or self-serve keys (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Libsyn with 14 endpoints (7 read, 7 write): your AI agent signs in as you and does the work.

Endpoints
14 7 read, 7 write
Updated
How Cotlet connects your agent to Libsyn
  1. Your agent

    Claude Code, Codex, Cursor or a script

  2. Cotlet

    MCP server and REST API · 14 endpoints

    cotlet.dev/mcp/v1

  3. Libsyn logo

    Libsyn

    Signed in as you on libsyn.com

You sign in once. We never store your password.

Official API

Does Libsyn have an official API?

Libsyn lists an API only on its Professional and Enterprise plans, sold through contact sales, and publishes no API reference or self-serve keys (checked 11 Oct 2026). Basic, Advanced and Max podcasters publish in the dashboard or by FTP.

What Libsyn's own tools do compared with Cotlet
Task Libsyn official Cotlet
Upload an episode media file Partly FTP upload, not an API Yes
Create a draft episode with show notes No Yes
Schedule an episode for a set date No Yes
Publish an episode now Partly FTP quickcast folder, details from ID3 tags only Yes
Edit show notes and episode details No Yes
List drafts, scheduled and published episodes Partly Public RSS feed lists published episodes only Yes
Downloads per episode, country, app and destination Partly Stats API for LibsynPro, no public reference Yes
Add an episode transcript No Yes

Sources: Libsyn plans and pricing (API on Professional and Enterprise) · LibsynPro enterprise podcasting (Stats API) · Libsyn Master Terms, section 3.4 APIs · Libsyn help: Use FTP to upload or publish episodes · Libsyn help: Bulk Edit Episodes (author, season, episode number) · Libsyn help: Download Stats Reports (Advanced Plan and higher)

Common use cases

What can an AI agent do in Libsyn?

Cotlet is best for podcasters on Libsyn Basic, Advanced or Max plans who want their AI agent to schedule episodes, edit show notes and pull download stats without running or fixing a server.

  • Schedule a podcast episode from a file Runs: Weekly

    Upload ep-142.mp3 from our bucket, use notes.md as show notes, make it season 3 episode 12 and schedule it for Thursday 6:00 New York time. Your agent calls list_episodes, upload_media, create_episode and schedule_episode.

  • Find your best-performing podcast episodes Runs: Weekly

    Which of my last 10 episodes got the most downloads in their first 30 days? Your agent calls list_episodes and get_episode_stats.

  • Update sponsor links in old show notes

    Replace the old Acme link with https://acme.example/podcast in the show notes of every season 3 episode, and add the sponsor line to the ones that do not have it yet. Your agent calls list_episodes, get_episode, update_episode and bulk_edit_episodes.

  • Renumber podcast seasons and episodes

    Set season 3 on these three episodes and number them in order. Your agent calls list_episodes and bulk_edit_episodes.

  • Attach transcripts to podcast episodes

    Attach the VTT transcripts in /transcripts to the matching episodes of The Solo Founder Show and tell me which files had no match. Your agent calls list_episodes, get_episode and upload_transcript.

  • Monthly podcast downloads report for sponsors Runs: Monthly

    On the 2nd of every month, give me last month's IAB downloads by country and by listening app, the top 5 episodes of the month and a CSV I can forward to sponsors. Your agent calls get_show_stats, get_downloads_breakdown, list_episodes, get_episode_stats and export_stats_report.

Endpoints

What is the Libsyn API?

Cotlet's Libsyn API exposes 14 endpoints for your own Libsyn account: list shows, list episodes, get episode, get show stats, get episode stats, get downloads breakdown, export stats report, upload media file, create episode draft, update episode, bulk edit episodes, upload transcript, schedule episode and publish episode. The list_shows endpoint returns podcasts in your Libsyn account with show ID, title and plan. Each endpoint takes simple JSON inputs like show_id, episode_id or start_date and works both as an MCP tool for agents and as a REST call for scripts.

All endpoints · 14 total

missing one? request an endpoint

  • POST

    list_shows

    read

    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.

    POST /api/v1/libsyn/list_shows

    Input

    No parameters.

    Example response

    {
      "shows": [
        {
          "show_id": "412907",
          "title": "The Solo Founder Show",
          "plan": "Advanced"
        },
        {
          "show_id": "518344",
          "title": "Founder Shorts",
          "plan": "Basic"
        }
      ]
    }
  • POST

    list_episodes

    read

    Lists episodes of one show, newest first, with status (draft, scheduled or published) and release date, as in the dashboard Episodes list. Filter by status or match titles with search. Pages hold up to 100 episodes; pass next_cursor back as cursor for the next page.

    POST /api/v1/libsyn/list_episodes

    Input

    Input: list_episodes
    Parameter Type Description
    show_id string Show ID from list_shows. Default: your only or first show.
    status enum all, draft, scheduled or published. Default: all.
    search string Match episode titles.
    limit integer 1 to 100. Default: 25.
    cursor string Next page cursor from the previous call.

    Example response

    {
      "episodes": [
        {
          "episode_id": "38415502",
          "title": "Pricing your first product",
          "status": "scheduled",
          "release_at": "2026-10-15T06:00:00-04:00",
          "ads": 0
        },
        {
          "episode_id": "38201877",
          "title": "Your first ten customers",
          "status": "published",
          "release_at": "2026-10-01T06:00:00-04:00",
          "ads": 2
        }
      ],
      "next_cursor": "eyJvZmZzZXQiOjI1fQ"
    }
  • POST

    get_episode

    read

    Returns one episode with its full show notes, status, release date, season and episode number, type, rating, author, tags and media file. Use it before update_episode so your agent edits the current text and does not overwrite it.

    POST /api/v1/libsyn/get_episode

    Input

    Input: get_episode
    Parameter Type Description
    episode_id required string Episode ID from list_episodes.

    Example response

    {
      "episode_id": "38415502",
      "title": "Pricing your first product",
      "description": "How to price your first product.",
      "status": "scheduled",
      "release_at": "2026-10-15T06:00:00-04:00",
      "season_number": 3,
      "episode_number": 12,
      "episode_type": "full",
      "rating": "clean",
      "author": "Dana Kim",
      "tags": [
        "pricing",
        "startups"
      ],
      "media_file": {
        "file_name": "ep-142.mp3",
        "media_file_id": "f_88120"
      }
    }
  • POST

    get_show_stats

    read

    Returns downloads for the whole show: all time, this week, this month and per day for the range you choose. The metric is IAB downloads by default, or unique downloads. Read only.

    POST /api/v1/libsyn/get_show_stats

    Input

    Input: get_show_stats
    Parameter Type Description
    show_id string Show ID from list_shows. Default: your only or first show.
    start_date date First day of the range. Default: 30 days ago.
    end_date date Last day of the range. Default: today.
    metric enum iab or unique downloads. Default: iab.

    Example response

    {
      "show_id": "412907",
      "metric": "iab",
      "all_time": 214530,
      "this_week": 1260,
      "this_month": 5210,
      "daily": [
        {
          "date": "2026-10-01",
          "downloads": 190
        },
        {
          "date": "2026-10-02",
          "downloads": 205
        },
        {
          "date": "2026-10-03",
          "downloads": 198
        }
      ],
      "range_total": 593
    }
  • POST

    get_episode_stats

    read

    Returns downloads for one episode in its first 7, 30 and 90 days and all time, so episodes of different age compare fairly. daily lists downloads per day for the range you choose and range_total adds them up. Read only.

    POST /api/v1/libsyn/get_episode_stats

    Input

    Input: get_episode_stats
    Parameter Type Description
    episode_id required string Episode ID from list_episodes.
    start_date date First day of the range. Default: 30 days ago.
    end_date date Last day of the range. Default: today.
    metric enum iab or unique downloads. Default: iab.

    Example response

    {
      "episode_id": "38415502",
      "title": "Pricing your first product",
      "metric": "iab",
      "first_7_days": 1840,
      "first_30_days": 4215,
      "first_90_days": 6120,
      "all_time": 7310,
      "daily": [
        {
          "date": "2026-09-01",
          "downloads": 212
        },
        {
          "date": "2026-09-02",
          "downloads": 198
        },
        {
          "date": "2026-09-03",
          "downloads": 187
        }
      ],
      "range_total": 597
    }
  • POST

    get_downloads_breakdown

    read

    Splits a show's downloads for a date range by country, listening app (user_agent) or publishing destination, biggest first. total_downloads is the sum of the rows. It needs the Advanced Plan or higher; on other plans the call fails with a plan error. Read only.

    POST /api/v1/libsyn/get_downloads_breakdown

    Input

    Input: get_downloads_breakdown
    Parameter Type Description
    show_id string Show ID from list_shows. Default: your only or first show.
    by required enum country, user_agent or destination.
    start_date date First day of the range. Default: 30 days ago.
    end_date date Last day of the range. Default: today.
    metric enum iab or unique downloads. Default: iab.

    Example response

    {
      "show_id": "412907",
      "by": "country",
      "metric": "iab",
      "rows": [
        {
          "key": "United States",
          "downloads": 9120
        },
        {
          "key": "Canada",
          "downloads": 2210
        },
        {
          "key": "United Kingdom",
          "downloads": 1875
        },
        {
          "key": "Germany",
          "downloads": 940
        },
        {
          "key": "Other",
          "downloads": 3855
        }
      ],
      "total_downloads": 18000
    }
  • POST

    export_stats_report

    read

    Runs the Stats Export for a show and returns a link to a zip with one file per report you ask for. Formats are csv, xlsb and pdf. It needs the Advanced Plan or higher. It only reads, and the link is for you to fetch or pass to the next step of your automation.

    POST /api/v1/libsyn/export_stats_report

    Input

    Input: export_stats_report
    Parameter Type Description
    show_id string Show ID from list_shows. Default: your only or first show.
    reports required string[] Any of total_downloads, by_episodes, by_country, by_destination, by_user_agent.
    range enum last_30_days, last_60_days, last_90_days or all_time. Default: last_30_days.
    format enum csv, xlsb or pdf. Default: csv.

    Example response

    {
      "show_id": "412907",
      "status": "ready",
      "range": "last_30_days",
      "format": "csv",
      "files": [
        "total_downloads.csv",
        "by_country.csv"
      ],
      "download_url": "https://example.com/exports/412907-last_30_days.zip"
    }
  • POST

    upload_media

    write

    Fetches a file from a public or signed URL and adds it to the media library of one show. It accepts mp3, m4a, mp4, m4v, ogg and pdf. The file name must be unique in your show. Nothing is published and nobody is notified, so it runs without asking; attach the returned media_file_id to a draft with create_episode.

    POST /api/v1/libsyn/upload_media

    Input

    Input: upload_media
    Parameter Type Description
    show_id string Show ID from list_shows. Default: your only or first show.
    file_url required string Public or signed URL of an mp3, m4a, mp4, m4v, ogg or pdf file.
    file_name string Must be unique in your show. Default: name from the URL.

    Example response

    {
      "media_file_id": "f_88120",
      "file_name": "ep-142.mp3",
      "status": "uploaded"
    }
  • POST

    create_episode

    write

    Saves a new episode as a Draft with its title, show notes and details. Show notes are HTML or Markdown; Apple Podcasts shows up to 4,000 characters. Nothing reaches listeners until schedule_episode or publish_episode, so this call runs without asking and you can delete the draft in the dashboard.

    POST /api/v1/libsyn/create_episode

    Input

    Input: create_episode
    Parameter Type Description
    show_id string Show ID from list_shows. Default: your only or first show.
    title required string Episode title, shown in podcast apps.
    description required string Show notes, HTML or Markdown. Apple Podcasts shows up to 4,000 characters.
    media_file_id string File from upload_media.
    season_number integer Season number.
    episode_number integer Episode number.
    episode_type enum full, trailer or bonus. Default: full.
    rating enum clean or explicit. Default: show setting.
    author string Episode author.
    tags string[] Episode tags.

    Example response

    {
      "episode_id": "38415502",
      "status": "draft",
      "title": "Pricing your first product",
      "season_number": 3,
      "episode_number": 12,
      "media_file_id": "f_88120"
    }
  • POST

    update_episode

    write

    Changes the fields you pass and leaves the rest. On a published episode the RSS feed updates, so podcast apps show the change. Read the current text with get_episode first if you add to it. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/libsyn/update_episode

    Input

    Input: update_episode
    Parameter Type Description
    episode_id required string Episode ID from list_episodes.
    fields required object Any of title, description, season_number, episode_number, episode_type, rating, author, tags.

    Example response

    {
      "episode_id": "38415502",
      "status": "scheduled",
      "updated_fields": [
        "description"
      ]
    }
  • POST

    bulk_edit_episodes

    write

    Sets the author and season on the episodes you list and can number them in the order you pass them: top_to_bottom numbers from the first ID, bottom_to_top from the last. The RSS feed refreshes after the change. It returns every episode with its new number. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/libsyn/bulk_edit_episodes

    Input

    Input: bulk_edit_episodes
    Parameter Type Description
    episode_ids required string[] Episodes to edit.
    author string New author for all of them.
    season_number integer New season for all of them.
    numbering enum none, top_to_bottom or bottom_to_top. Default: none.

    Example response

    {
      "updated": 3,
      "season_number": 3,
      "numbering": "bottom_to_top",
      "episodes": [
        {
          "episode_id": "38415502",
          "episode_number": 3
        },
        {
          "episode_id": "38201877",
          "episode_number": 2
        },
        {
          "episode_id": "38009640",
          "episode_number": 1
        }
      ]
    }
  • POST

    upload_transcript

    write

    Fetches an .srt or .vtt file from a URL and attaches it to one episode. Libsyn adds the transcript to the feed for Apple Podcasts and other apps, so it can reach listeners. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/libsyn/upload_transcript

    Input

    Input: upload_transcript
    Parameter Type Description
    episode_id required string Episode ID from list_episodes.
    file_url required string URL of an .srt or .vtt file.

    Example response

    {
      "episode_id": "38415502",
      "transcript": {
        "format": "vtt",
        "status": "attached"
      }
    }
  • POST

    schedule_episode

    write

    Sets a release time for a draft. At that time Libsyn publishes it to every destination the show is connected to, such as Apple Podcasts, Spotify and YouTube. release_at needs a time zone. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/libsyn/schedule_episode

    Input

    Input: schedule_episode
    Parameter Type Description
    episode_id required string Episode ID from list_episodes.
    release_at required datetime ISO 8601 with time zone.

    Example 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"
    }
  • POST

    publish_episode

    write

    Publishes a draft at once to every destination the show is connected to. Listeners can see it as soon as their apps refresh the feed. To release later, use schedule_episode. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/libsyn/publish_episode

    Input

    Input: publish_episode
    Parameter Type Description
    episode_id required string Episode ID from list_episodes.

    Example response

    {
      "episode_id": "38415502",
      "status": "published",
      "title": "Pricing your first product",
      "url": "https://yourname.libsyn.com/pricing-your-first-product"
    }

Setup

How do I connect Libsyn to Claude Code, Codex or Cursor?

Connecting Libsyn takes three steps: request access, sign in to Libsyn once, then add one MCP server or call the REST API with the same key.

Connect Libsyn over MCP

  1. 1

    Create an account

    Sign up and add Libsyn in the console. Your API key is there too.

  2. 2

    Sign in to Libsyn once

    Open the connect page from the console and sign in to Libsyn the way you always do. We keep the session, never your password, and you can revoke it anytime.

  3. 3

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

  4. 4

    Ask your agent

    Prompt

    Upload ep-142.mp3 from our bucket, use notes.md as show notes, make it season 3 episode 12 and schedule it for Thursday 6:00 New York time.

    Ask in plain words. Your agent finds the Libsyn tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

Call Libsyn over REST

  1. 1

    Export your API key

    Shell

    export COTLET_API_KEY="cotlet_..."

    Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

  2. 2

    Call a tool

    curl

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

    Every tool is a POST endpoint at /api/v1/libsyn/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

  3. 3

    Read the result

    Example response · schedule_episode

    {
      "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"
    }

    You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for Libsyn? Hosted, safe and kept working.

  • Built for agents

    • One MCP server for every app you connect.
    • The same tools as a REST API for scripts and cron jobs.
    • Works with Claude Code, Codex and Cursor.
  • Your login stays yours

    • You sign in to Libsyn yourself. We keep only the session, encrypted with AES-256.
    • The model never sees a login.
    • No stored passwords, no CAPTCHA solving, no MFA bypass.
  • You stay in control

    • Pick read only, or read and write.
    • Anything that reaches other people waits for your OK, unless you switch it off per tool.
    • Revoke access in one click.
  • Kept working for you

    • We test every integration daily.
    • When Libsyn changes, the tool pauses until we fix it.
    • Failed calls cost nothing.

Alternatives

Is there a Libsyn MCP server on GitHub?

Libsyn's own FTP server can upload files and publish them at once from their ID3 tags. It cannot schedule, edit or read stats. For those jobs the realistic option today is to do them by hand in the Libsyn dashboard, one episode at a time; Cotlet lets your agent do the same work in your account.

Cotlet compared with a Libsyn dashboard and FTP
Libsyn dashboard and FTP Cotlet
Setup Create an FTP password, fill in ID3 tags in every file, then click through the dashboard Request access, sign in to Libsyn once, add one MCP server or API key
Scheduling FTP quickcast publishes as soon as the upload finishes; a schedule is set per episode in the dashboard Drafts, scheduled releases and publish now, each release confirmed by you
Editing episodes One episode at a time in the dashboard, or Bulk Edit for author, title and season Your agent edits details, renumbers and adds transcripts across the whole list
Stats Open the dashboard, pick a range, export a report Your agent reads downloads per episode, country, app and destination, and exports reports on a schedule
When Libsyn changes Nothing breaks, but your steps change Our team tests it daily and fixes it for you; failed calls are free
Your Libsyn session Your login in your browser Encrypted in an EU vault, limited to the actions you allow, revoked in one click
Price Free with your Libsyn plan, paid for with your time Free 7-day trial with 5,000 credits, then credits per call

Which one fits you

Pick Cotlet if

  • you are not a developer, or you do not want to maintain a server
  • you need it to keep working when Libsyn changes, without checking it yourself
  • your agent or a script should run it on a schedule, also while your computer is off

Pick an open-source server if

  • you are comfortable installing, updating and fixing it yourself
  • you want the session to stay on your own computer
  • you only need it now and then, from one MCP client

For AI agents

Cotlet for Libsyn in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

  • list_shows passing
  • list_episodes passing
  • get_episode passing
  • get_show_stats passing
  • get_episode_stats passing

+ 9 more endpoints

14/14 passing latest check self-healing

libsyn.txt

Libsyn lists an API only on its Professional and Enterprise plans, sold through contact sales, and publishes no API reference or self-serve keys (checked 11 Oct 2026). Basic, Advanced and Max podcasters publish in the dashboard or by FTP.
Cotlet provides a hosted MCP server and REST API for Libsyn: 14 tools (7 read, 7 write).
Access       Request access at https://cotlet.dev/app/signup?app=libsyn; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/libsyn
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_shows, list_episodes, get_episode, get_show_stats, get_episode_stats, get_downloads_breakdown, export_stats_report, upload_media, create_episode, update_episode, bulk_edit_episodes, upload_transcript, schedule_episode, publish_episode
Confirm      update_episode, bulk_edit_episodes, upload_transcript, schedule_episode, publish_episode (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/libsyn-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=libsyn (Libsyn is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Libsyn once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Libsyn server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Libsyn in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Libsyn's terms; Cotlet is not affiliated with Libsyn.
Full page as Markdown

Automations

Can Libsyn automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Libsyn connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to schedule a podcast episode from a file, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

Where to run Libsyn automations through Cotlet, and how to schedule them
Where How to connect How to schedule
Your AI agent Add https://cotlet.dev/mcp/v1 with your API key. A scheduled agent run, for example a Claude Code routine.
n8n MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/libsyn/{tool}. Schedule Trigger node.
Make HTTP module: POST https://cotlet.dev/api/v1/libsyn/{tool} with an Authorization: Bearer header and a JSON body. Scenario schedule.
Zapier Webhooks by Zapier: POST https://cotlet.dev/api/v1/libsyn/{tool} with the same header and body. Schedule by Zapier trigger.
Your own script POST https://cotlet.dev/api/v1/libsyn/{tool} with your API key. cron or GitHub Actions.

Pricing & limits

How much does the Libsyn API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Libsyn API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

Cotlet plan sizes: price, monthly credits and price per credit
Size Price Credits / month Per credit
Solo $29/mo 3,000 about $0.0097
Pro $99/mo 12,000 about $0.0083
Agency $299/mo 40,000 $0.0075

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.

About Cotlet

How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Libsyn account.

Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to Libsyn yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Libsyn tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Libsyn in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
Libsyn's terms
You use your own Libsyn account and stay responsible for following Libsyn's terms. Cotlet is independent and not affiliated with Libsyn. Terms
Contact
Questions about the company, security or an app: contact@cotlet.dev
About Cotlet

Frequently asked questions

How do I get access?

Request access and pick Libsyn. Cotlet reviews each request and emails you your API key.

Do I need to be technical?

No. You sign in to Libsyn once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

Is a hosted server safe? My Libsyn session would leave my computer.

Cotlet keeps your Libsyn session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

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.

Can my agent post or send messages in Libsyn without asking me?

No. Every call to update_episode, bulk_edit_episodes, upload_transcript, schedule_episode or publish_episode waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. upload_media, create_episode runs without asking, because it sends nothing to anyone and one call undoes it.

Can I use the Libsyn API in n8n?

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/libsyn/{tool} from the HTTP Request node.

Give your agent access to Libsyn.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.