Recapfy MCP server

Recapfy MCP

An MCP server that exposes Recapfy's paid endpoints as tools — ask anything about a YouTube video and fetch a video's full transcript — straight from an MCP-capable agent like Claude Desktop, Cursor, or Cline. It runs locally — there's no hosted Recapfy MCP endpoint; you launch your own copy.

Each call is paid in USDC on Solana (dynamic price, scales with maxOutputTokens), settled automatically via the x402 protocol. You bring your own wallet; you pay only for what you call.

📦 npm: recapfy-mcp

Prerequisites

— the API's facilitator sponsors the network fee.

• Node.js ≥ 20.
• A Solana wallet funded with USDC on mainnet. You do not need SOL for fees

"Export Private Key" gives you, or solana-keygen).

• That wallet's secret key, base58-encoded (the 64-byte form that Phantom's

⚠️ The key signs real payments. Use a dedicated low-balance wallet, never share

it, and never commit it.

Install

No clone or build needed. Add this to your MCP client config (Claude Desktop: claudedesktopconfig.json) and restart the client:

{
  "mcpServers": {
    "recapfy": {
      "command": "npx",
      "args": ["-y", "recapfy-mcp@latest"],
      "env": {
        "SVM_PRIVATE_KEY": "<your base58 Solana secret key>"
      }
    }
  }
}

Always use recapfy-mcp@latest. A bare npx -y recapfy-mcp reuses

whatever is in npx's cache and never re-checks the registry, so you can stay

pinned to an old build (and miss new tools) indefinitely. The @latest tag

forces npx to resolve the newest published version on every launch.

Updating

New versions (including new tools/endpoints) are picked up automatically when two things happen, because of two independent caches:

the newest published version each launch. Without @latest, npx serves the cached copy and you stay on an old build.

1. npx package cache — using recapfy-mcp@latest (as above) makes npx fetch

session. New tools only appear after you fully restart the MCP client** (Claude Desktop, Cursor, Cline, …) so it relaunches the server and re-reads the tools.

1. MCP client tool list — clients read the server's tool list **once per

So after a release: keep @latest and restart your client. If a brand-new tool still doesn't show up, force a clean fetch:

npx clear-npx-cache    # or: rm -rf "$(npm config get cache)/_npx"

then restart the client again.

Configuration

Tool: ask

Shortened. The full README is on GitHub.