# recapfy [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/pedrot95dev/recapfy.mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 176  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/recapfy

## Description
Ask anything about a YouTube video (or summarize it). Paid per call in USDC on Solana via x402.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "recapfy": {
    "command": "npx",
    "args": ["-y","recapfy-mcp"],
    "env": {
      "SVM_PRIVATE_KEY": ""
    }
  }
}
```

**Requires environment variables:** `SVM_PRIVATE_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the recapfy MCP server does

The recapfy MCP server exposes two Recapfy API operations to MCP-compatible clients: `ask` and `get_transcript`. Both accept an absolute HTTP or HTTPS YouTube URL. The first sends a question about the video and returns an answer as text. The second returns the complete transcript with timestamps, along with the video's title, channel name, and duration.

This is a locally launched server rather than a hosted MCP endpoint. The npm package is started by the MCP client, so the client process communicates with a local instance while that instance calls Recapfy's API.

## Tools and capabilities

`ask` requires `videoUrl` and a non-empty `prompt`. It accepts an optional positive `maxOutputTokens` value, which defaults to 1024 and affects the quoted price. The response is returned after payment is settled.

`get_transcript` requires only `videoUrl`. Its readable output contains timestamped transcript segments. Structured output also includes a raw array whose entries contain `timestampInSeconds` and `text`.

The recapfy MCP server uses x402 payment handling for both operations. The API first responds with payment requirements, including the USDC amount. The client signs a gasless SPL-token transfer with the configured Solana wallet, retries the request, and receives the API response after verification and settlement. The facilitator sponsors the network fee, so the wallet does not need SOL, but it must hold USDC on Solana mainnet.

## Setup and configuration

Install without cloning or building by configuring the client to run `npx -y recapfy-mcp@latest`. Set `SVM_PRIVATE_KEY` to the wallet's base58-encoded 64-byte secret key. A dedicated, low-balance wallet is appropriate because every invoked tool makes a real payment.

`RECAPFY_API_BASE_URL` optionally replaces the default API URL, `https://api.recapfy.ai`, which is useful for local development. `RECAPFY_ALLOW_INSECURE_TLS=1` permits self-signed TLS certificates for local HTTPS development.

Use the `@latest` package tag so npx checks for the current published package. After an update, fully restart the MCP client because clients read the tool list once per session. If the package remains stale, clear the npx cache and restart again.

## Limitations and notes

Calls are not free: `ask` has a dynamic USDC price based on `maxOutputTokens`, while `get_transcript` has a flat USDC price. The amount is quoted by the API and paid before the result is returned. An unfunded wallet, an incorrect network, an invalid private key, or missing required input will prevent a call from succeeding.

The server requires Node.js 20 or newer. Use the MCP Inspector to browse the available tools without invoking them; running a tool with a funded wallet performs a real paid request. The project is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/recapfy/readme_