ai.com.mcp/lenny-rachitsky-podcast

Official8 tools

by la-rebelion · HTML

Lenny Rachitsky Podcast Transcripts MCP Server

MCP server for structured access to Lenny Rachitsky podcast transcripts. For content creators.

Structured search and access to Lenny Rachitsky podcast episode transcripts.

Captured live from the server via tools/list.

getEpisodes

List episodes - Lists episodes with parsed frontmatter (guest, title, duration, youtube_url, etc.) and their canonical resource URIs.

Parameters (4)

limitinteger
cursorstring
Opaque pagination cursor
sortstring
x-hapi-auth-statestring

getEpisodesGuest

Get an episode card (metadata + key URIs)

Parameters (2)

gueststringrequired
x-hapi-auth-statestring

getEpisodesGuestMetadatajson

Get episode metadata as JSON (frontmatter)

Parameters (2)

gueststringrequired
x-hapi-auth-statestring

getEpisodesGuestTranscriptformat

Get transcript in a specific format - Returns the transcript in the requested format: - md: markdown (may include or exclude frontmatter based on include_frontmatter) - txt: clean text (best for LLM ingestion) - json: structured form (metadata + transcript text)

Parameters (4)

gueststringrequired
formatstringrequired
include_frontmatterboolean
x-hapi-auth-statestring

getEpisodesGuestChunks

List chunk descriptors for an episode - Returns chunk boundaries and URIs for chunk retrieval. Chunks may be computed on-demand using size/overlap parameters.

Parameters (4)

gueststringrequired
sizeinteger
overlapinteger
x-hapi-auth-statestring

getEpisodesGuestChunksChunkIdtxt

Get a specific transcript chunk as plain text

Parameters (3)

gueststringrequired
chunkIdintegerrequired
x-hapi-auth-statestring

getSearch

Search episodes and transcripts - Searches across metadata (D1) and transcript text (Vectorize). Returns matches as resources, including per-hit URIs pointing to episode cards and transcript chunks. Note: pagination cursor applies to metadata search only. Example (vector search with filters): GET /search?q=pricing&mode=vector&guest=Marty%20Cagan&keywords=pricing,monetization&top_k=5

Parameters (11)

qstringrequired
modestring
episode_slugstring
gueststring
titlestring
keywordsstring
namespacestring
top_kinteger
limitinteger
cursorstring
Opaque pagination cursor
x-hapi-auth-statestring

postSearch

Search episodes and transcripts (POST body) - Same search as GET /search, but parameters are provided in the request body. This is useful for longer filter payloads.

Parameters (2)

undefinedBodyobjectrequired
x-hapi-auth-statestring

README.md6 KBView on GitHub

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

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

code

API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients

code

[ 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

Playlist with demos
New HAPI MCP YT Channel with demos API-First and MCP

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

Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases
Transform your OpenAPI spec into an MCP server with a single command:
bash
```
hapi serve path/to/your/swagger.json --headless
```
Start using your MCP tools with any compatible client!
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.

Install

claude_desktop_config.json

{
  "mcpServers": {
    "lenny-rachitsky-podcast": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://lenny-rachitsky.run.mcp.com.ai/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.