PluginBench
MCP Server
Active
MIT

Lenny Rachitsky Podcast Transcripts MCP Server MCP Server

ai.com.mcp/lenny-rachitsky-podcast

Transform OpenAPI specs into MCP tools instantly—no rewrites, no parallel codebases.

RepositoryRegistry
How to choose

What this kind of tool is for

  • Let your agent search the web or a document set and cite what it found.
  • Pull structured facts out of pages instead of copy-pasting by hand.
  • Track changes on a topic over days without re-reading everything.

How to compare servers like this

Source coverage:
Check which engines, sites, or document types the tool can actually reach.
Citation behavior:
Prefer tools that return links you can open, not just summarized claims.
Terms of service:
Some sources forbid automated access; make sure the tool stays inside them.
Maintenance signal:
Scrapers break silently when pages change; recent commits are the best proxy.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the Lenny Rachitsky Podcast Transcripts MCP Server MCP server?

The Lenny Rachitsky Podcast Transcripts MCP Server provides structured access to Lenny Rachitsky podcast transcripts via the HAPI MCP framework. HAPI MCP automatically converts OpenAPI specifications into MCP tools, allowing AI agents to query and interact with podcast content without custom integration code. This server demonstrates how existing APIs can be lifted into MCP-compatible tools for content creators and researchers.

This MCP server exposes Lenny Rachitsky's podcast transcripts as queryable tools through the HAPI MCP framework. Rather than building custom integrations, HAPI transforms an OpenAPI specification into MCP-compatible tools, enabling AI agents and content creators to search, retrieve, and analyze podcast episodes and their transcripts programmatically. It's useful for researchers, content creators, and anyone building AI workflows that need structured access to podcast data.

How to install Lenny Rachitsky Podcast Transcripts MCP Server

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "lenny-rachitsky-podcast": {
      "url": "https://lenny-rachitsky.run.mcp.com.ai/mcp"
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • Podcast Transcript Query — Query and retrieve Lenny Rachitsky podcast transcripts via OpenAPI-backed MCP tools

Use cases

  • Search and retrieve specific podcast episodes by topic, guest, or date
  • Extract quotes and key insights from transcripts for content creation
  • Build AI-powered research tools that analyze podcast themes and trends
  • Integrate podcast data into knowledge bases or RAG systems
  • Automate content summarization and highlight generation from episodes

Lenny Rachitsky Podcast Transcripts MCP Server MCP server FAQ

What is the Lenny Rachitsky Podcast Transcripts MCP Server?

It's an MCP server that provides structured, queryable access to Lenny Rachitsky podcast transcripts. Built on HAPI MCP, it transforms an OpenAPI specification into MCP tools, allowing AI agents to search and retrieve podcast content without custom code.

Is this free to use?

The server is open-source (MIT licensed). Access to the actual podcast transcripts depends on Lenny Rachitsky's content licensing and availability.

How do I install this in Claude or Cursor?

Add the remote MCP endpoint `https://lenny-rachitsky.run.mcp.com.ai/mcp` to your MCP client configuration. Refer to your client's documentation for connecting remote MCP servers.

Do I need authentication?

Authentication requirements depend on the underlying podcast API. Check the server's configuration and the Lenny Rachitsky content provider's terms for any API keys or credentials needed.

What can I do with this server?

You can search transcripts, retrieve full episodes, extract quotes, analyze themes, and integrate podcast data into AI workflows, research tools, or content creation pipelines.

Is this built on a custom framework?

No—it uses HAPI MCP, a framework that automatically converts OpenAPI specifications into MCP tools, so the server inherits auth, rate limits, and governance from the underlying API.

README (reference)

Source of truth, from the repository.

HAPI MCP – Headless API for Model Context Protocol

Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.

HAPI MCP lifts your OpenAPI catalog into MCP tools automatically, keeping design (OAS/Arazzo) and runtime (agents/LLMs) cleanly separated. Your existing APIs become AI-ready tools—no new business logic, no sidecar servers, no rework.

Key Features

  • No rewrites: Reuse 100% of your API logic. OpenAPI in, MCP tools out. No parallel codebase or shadow services.
  • Faster time-to-value: Turn specs into agent-ready tools in minutes. Update the spec, ship new tools instantly.
  • Reduced risk: Permissions, auth, rate limits, auditability are inherited from your APIs—governance without bolt-ons.
  • Scales with you: runMCP delivers serverless-like elasticity with long-running when needed. Cold-start fast, stay warm for throughput.
  • Deterministic orchestration: OrcA plans and executes multi-tool tasks predictably—no brittle prompt chaining.
  • Vendor-neutral: Works with any MCP client: ChatGPT, Claude, QBot, chatMCP. OAS + MCP + Arazzo stay portable.

How It Works

  1. Pick your API spec

    • OpenAPI, Swagger, REST—HAPI CLI works with any API specification format.
    • Supports OpenAPI 3.0+, REST APIs, OAuth 2.0 Dynamic Client Registration.
  2. Run a single command

    • One simple CLI command transforms your API into a usable MCP Server.
    • No complex setup, zero configuration, works anywhere, cross-platform.
  3. Use instantly

    • Your API is now ready as a tool, AI agent, or testing interface.
    • MCP server ready, AI agent compatible, testing interface, developer experience friendly.

Visual Pipeline

API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients
[ OpenAPI / Swagger ]       [ HAPI CLI ]        [ MCP Server ]
       (Your API)         →   (Transform)   →   (Usable Tool)
                                                 ↑          ↑
                                                 |          |
                                          [ ChatGPT ]  [ runMCP ]
                                          [ Claude  ]  [ OrcA   ]
                                          [ QBot    ]  [ chatMCP]
                                          [ Agents  ]

Who Wins With HAPI

  • Executives: Ship AI initiatives without ballooning cost. Keep teams focused on outcomes, not rewrites and integration sprawl.
  • Architects & PMs: Design with OpenAPI/Arazzo, run with MCP. Clear contracts, policy inheritance, and versioned workflows keep risk low.
  • Engineers & Ops: Deploy once. HAPI Server + runMCP scale tools; QBot/chatMCP give fast feedback; OrcA keeps executions deterministic.

Your Stack, Already Wired

  • HAPI Server: Turns OpenAPI into MCP tools automatically—contracts stay in sync with your source of truth.
  • runMCP: Autoscaling execution and testing for MCP tools; cold-start fast, stay warm when workflows run long.
  • QBot: CLI TUI for power users to interact with MCP tools directly from terminal or scripts.
  • chatMCP: Conversational client that speaks MCP natively for support, ops, and internal assistants.
  • OrcA: Deterministic planning and orchestration for multi-tool tasks; no brittle prompt spaghetti.
  • Agents: Build agentic systems from standard APIs—no custom glue. Connect MCP clients across platforms.

Demos

Documentation

FAQ

  • Do we need to rewrite our services?
    No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.

  • Is this just another MCP server?
    It’s the Headless API model: your API becomes the runtime. HAPI Server reflects it as MCP; runMCP scales it; OrcA orchestrates it. No duplicate logic.

  • Which clients can consume the tools?
    Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.

  • How do we keep control and compliance?
    Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; no shadow logic.

  • What about security and privacy?
    Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.

  • How fast can we get started?
    You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.

Get Started

  1. Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases

  2. Transform your OpenAPI spec into an MCP server with a single command:

    hapi serve path/to/your/swagger.json --headless
    
  3. Start using your MCP tools with any compatible client!

  4. Explore the documentation for advanced usage and best practices.

Contributing

Contributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp

License

HAPI MCP is licensed under the MIT License. See LICENSE for details.

Related MCP servers

Turn LinkedIn's API into AI-ready MCP tools—retrieve profiles and publish content instantly.

9
HTML
MIT
View repository →

Transform OpenAPI specs into MCP tools instantly—no rewrites, no parallel codebases.

9
HTML
MIT
View repository →

Transform OpenAPI specs into MCP tools instantly—no rewrites, no sidecar servers.

9
HTML
MIT
View repository →

Official MCP Registry: publish and discover MCP servers like an app store for AI agents.

7.3k
Go
View repository →

Search and discover Agent Skills — reusable AI agent capability packages — from the skills.sh registry.

21k
Python
Apache-2.0
View repository →

Turn Strava APIs into AI-ready MCP tools instantly with HAPI—no rewrites, just OpenAPI specs.

9
HTML
MIT
View repository →