Log inSubmit server
Fireside.fm (unofficial) logo

Fireside.fm (unofficial)

Manage Fireside.fm podcasts, episodes, analytics, media uploads, drafts, and publishing through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Fireside.fm (unofficial)

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "fireside-fm-unofficial": {
      "command": "npx",
      "args": [
        "-y",
        "firesidefm-mcp-server"
      ],
      "env": {
        "FIRESIDE_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Fireside.fm (unofficial) connects MCP hosts to the Fireside.fm podcast hosting API for podcast, episode, and download-statistics access. Read-only keys support account, catalog, episode, and analytics queries, while Read/Write keys add draft creation, editing, file uploads, publishing, scheduling, and unpublishing. Use it when an assistant needs to inspect a Fireside account or help maintain an episode workflow from an MCP-compatible client. The server runs through Node.js and can be configured with a default podcast and controlled upload directories.

Use cases

  • Inspect podcast and episode download analytics
  • Review drafts and scheduled episodes
  • Create and update episode drafts
  • Upload audio, artwork, and transcripts
  • Publish or unpublish Fireside episodes

Key features

  • Fireside podcast and episode browsing
  • Daily, monthly, and episode download metrics
  • Draft creation and episode metadata editing
  • Local media and transcript uploads
  • Immediate, scheduled, and backdated publishing
  • Read-only and read/write key modes

Tools13

What Fireside.fm (unofficial) lets your agent do. Expand a tool for its parameters.

Self-reported~316 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · firesidefm-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads23Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed13Callable tools this server registers over MCP.

How Fireside.fm (unofficial) works

What Fireside.fm (unofficial) does

Fireside.fm (unofficial) exposes Fireside.fm podcast-management operations as MCP tools. It can inspect the connected account, list podcasts, retrieve podcast details, and browse episodes by status, including private drafts and scheduled releases. Episode lookups include detailed fields such as show notes and preview links.

Analytics tools return all-time, monthly, and daily download information. Episode metrics include download checkpoints at 1, 7, 14, 30, and 90 days, along with Spotify and total figures. Daily results can cover a podcast or a specific episode and distinguish Spotify downloads.

With a Read/Write API key, the server can create private drafts, modify episode metadata and media, publish or schedule episodes, backdate releases, choose public or unlisted visibility, and move published episodes back to private drafts.

How it works

The server authenticates with a Fireside API key and selects its available tools when it starts. A Read Only key exposes read operations. A Read/Write key enables episode-changing operations unless read-only mode is explicitly forced through configuration. If the key is rejected, startup stops with an error; if validation fails because of a network or Fireside service problem, the server starts with read tools and reports the reason on stderr.

Podcasts and episodes can be addressed by token or slug. Episode slugs commonly follow the episode number, although a customized dashboard slug takes precedence. Audio uploads are processed by Fireside after transfer, so an episode may report processing before reaching ready or failed status.

Setup and configuration

Node.js 22 or later and a Fireside API key are required. The key is created in the Fireside account API-token area. The package can be launched with npx -y firesidefm-mcp-server.

Set FIRESIDE_API_TOKEN to the account key. FIRESIDE_PODCAST supplies a default podcast token or slug when a request does not specify one. Set FIRESIDE_READ_ONLY=true to expose only read tools, even when the key permits writes.

File uploads require both a Read/Write key and FIRESIDE_UPLOAD_DIRS. This variable contains absolute directories separated like PATH: colons on macOS and Linux, semicolons on Windows. Only files inside those directories can be selected for upload. Supported uploads are MP3 audio, JPG/PNG/GIF/WebP cover art, and plain-text transcripts.

Claude Code can add the server with claude mcp add, passing the API key and optional podcast slug as environment values. Claude Desktop uses an mcpServers configuration entry and must be restarted after changes. If Node was installed through a version manager, Claude Desktop may need the absolute path to npx.

Tools and capabilities

The read tools cover account identity and key mode, owned or collaborative podcasts, podcast details, episode listings, complete episode records, and download reporting. Daily-download requests return at most 90 days from the API per request; the server combines requests to support periods up to a year.

Write operations include:

  • Creating private draft episodes with optional audio, artwork, and transcripts.
  • Updating title, subtitle, slug, show notes, season, type, explicit status, audio, artwork, or transcript.
  • Uploading permitted local files for attachment or obtaining a file URL for create and update operations.
  • Publishing immediately, scheduling, backdating, or choosing public versus unlisted release visibility.
  • Returning an episode to a private draft with unpublish.

MP3 files are checked before upload. The server rejects files without MP3 audio and flags differences from the dashboard’s suggested mono, 64–96 kb/s, 44.1 kHz settings unless the upload explicitly accepts those differences.

Limitations and notes

Episodes cannot be deleted through the API, and podcast settings cannot be changed. Chapters cannot be uploaded, and publishing an episode without audio fails. Fireside plan limits apply to audio; cover art is limited to 1.91 MB and transcripts to 195 KB.

Publishing may also post to connected social accounts when that behavior is enabled in the Fireside dashboard. The API does not expose or modify that setting. API keys are limited to 120 requests per minute; short pauses are handled by the server, while longer rate limits are reported.

Large audio transfers can exceed an MCP host’s tool timeout. In Claude Code, MCP_TOOL_TIMEOUT can be increased in milliseconds. The project is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Fireside.fm (unofficial)

Fireside.fm (unofficial) is an MCP server that connects AI clients to the Fireside.fm podcast hosting API. Its main tools read podcasts, episodes, account details, and download metrics, or create, edit, upload, publish, schedule, unpublish, and manage episode drafts with a Read/Write key.

Install it by running it through `npx -y firesidefm-mcp-server` from an MCP client configuration. Node.js 22 or later and a Fireside API key are required. Claude Code supports `claude mcp add`, while Claude Desktop requires an `mcpServers` entry and restart.

Set `FIRESIDE_API_TOKEN` to a Fireside API key. Optional variables select a default podcast, force read-only tools, or allow uploads from approved directories. The server checks the key at startup and chooses write tools based on its permissions and configuration.

Set `FIRESIDE_UPLOAD_DIRS` to approved absolute directories and use a Read/Write key. The upload tool accepts MP3 files, supported image formats, and plain-text transcripts. MP3 headers are checked, and nonstandard audio settings require explicit acceptance before upload.

Yes, publishing requires a Read/Write key and is available through the publish tool. Episodes can be released immediately, scheduled, backdated, public, or unlisted. The server can also unpublish an episode back to a private draft, but it cannot delete episodes.

Related MCP servers

All in Podcasts All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFireside.fm (unofficial) AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/fireside-fm-unofficial?style=directory)](https://allmcps.com/mcp/fireside-fm-unofficial)
HTML Embed
<a href="https://allmcps.com/mcp/fireside-fm-unofficial"><img src="https://allmcps.com/api/badge/fireside-fm-unofficial?style=directory" alt="Fireside.fm (unofficial) on AllMCPs" /></a>