Lenny Rachitsky Podcast Transcripts MCP Server

ai.com.mcp由 mcp.com.ai 发布官方发布者v0.6.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行网页搜索与抓取知识与记忆

概览

AI 生成的概览

远程 MCP 服务器，让助手以结构化方式访问 Lenny Rachitsky 播客的节目元数据与文字稿，并支持搜索和分块检索。

可以做什么
列出节目及其解析后的元数据（嘉宾、标题、时长、视频链接等），以及节目卡片和 JSON 元数据记录的规范资源 URI。按 markdown、纯文本或结构化 JSON 获取完整文字稿，可选择是否包含 frontmatter。列出文字稿分块描述并逐块获取纯文本，分块大小与重叠可按需计算。在节目元数据和文字稿文本中搜索，以资源形式返回命中项及对应 URI；同一搜索也可通过请求体传参以支持较长的筛选条件。
适用场景
适合让助手基于 Lenny Rachitsky 播客内容回答问题、引用或总结某期节目，或查找某位嘉宾谈过的话题，而无需自行下载并建立索引。
运行要求
远程 streamable HTTP 端点；未声明需要安装包、环境变量、请求头或身份验证。助手需能通过网络访问该托管端点。
安装前请注意
搜索与检索读取的是托管在第三方的内容，查询内容和所请求的节目会发送到该远程服务。未声明需要凭据、付费或写入操作。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Lenny Rachitsky Podcast Transcripts MCP Server，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/ai.com.mcp%2Flenny-rachitsky-podcast/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "lenny-rachitsky-podcast-transcripts": {
      "type": "http",
      "url": "https://lenny-rachitsky.run.mcp.com.ai/mcp"
    }
  }
}

README

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:

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

来源：README.md，提交 1873ff7

工具

8

getEpisodes

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

输入参数sortlimitcursorx-hapi-auth-state

getEpisodesGuest

Get an episode card (metadata + key URIs)

输入参数guest必填x-hapi-auth-state

getEpisodesGuestMetadatajson

Get episode metadata as JSON (frontmatter)

输入参数guest必填x-hapi-auth-state

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)

输入参数guest必填format必填x-hapi-auth-stateinclude_frontmatter

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.

输入参数sizeguest必填overlapx-hapi-auth-state

getEpisodesGuestChunksChunkIdtxt

Get a specific transcript chunk as plain text

输入参数guest必填chunkId必填x-hapi-auth-state

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

输入参数q必填modeguestlimittitletop_kcursorkeywordsnamespaceepisode_slugx-hapi-auth-state

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.

输入参数undefinedBody必填x-hapi-auth-state

版本历史

1
  1. v0.6.0最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分