What is the rate limit for the Transistor API?
API requests are rate-limited to 10 requests per 10 seconds as prescribed by the Transistor API reference.
@gxjansen
Basic information
Transistor MCP server implementation for use with your LLM
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"transistor": {
"command": "node",
"args": [
"path/to/Transistor-MCP/build/index.js"
],
"env": {
"TRANSISTOR_API_KEY": "your-api-key-here"
}
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
This MCP server provides tools to interact with the Transistor.fm API, allowing you to manage podcasts, episodes, and view analytics. It is designed for podcasters and content managers who want to automate podcast workflows via an MCP-compatible client.
Add the server to your MCP settings configuration file with your Transistor API key set in the TRANSISTOR_API_KEY environment variable. Then run it with node pointing to the built index.js. Use MCP tools such as list_shows, create_episode, and get_analytics to interact with your Transistor account.
API requests are rate-limited to 10 requests per 10 seconds as prescribed by the Transistor API reference.
Dates must be in "dd

Model Context Protocol Servers
A curated list of references for MLOps

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.

Request dedicated senior developers to work on your project, write job descriptions, and prep technical interviews — all without leaving your Claude chat. Just describe what you need, and Lemon.io MCP does the rest. 1–3

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
Comments