---
name: video-moment-finder
description: Public bootstrap for the Video Moment Finder REST API, CLI, and Claude-compatible remote MCP connector.
homepage: https://www.videomomentfinder.com
api_host: https://api.videomomentfinder.com
openapi: https://api.videomomentfinder.com/openapi.json
---

# Video Moment Finder

Use this file when you need the canonical public entrypoints for Video Moment Finder.

Video Moment Finder exposes two integration surfaces:

- REST API + CLI, authenticated with `vmf_` API keys
- Remote MCP at `https://api.videomomentfinder.com/mcp`, authenticated with OAuth 2.0 authorization-code + PKCE

## Canonical URLs

- Site: `https://www.videomomentfinder.com`
- Developers overview: `https://www.videomomentfinder.com/developers`
- Claude connector approval page: `https://www.videomomentfinder.com/connectors/claude`
- Public skill file: `https://www.videomomentfinder.com/skill.md`
- Privacy policy: `https://www.videomomentfinder.com/privacy`
- Support: `https://www.videomomentfinder.com/support`
- API host: `https://api.videomomentfinder.com`
- Public REST prefix: `https://api.videomomentfinder.com/api/v1`
- Remote MCP endpoint: `https://api.videomomentfinder.com/mcp`
- OpenAPI schema: `https://api.videomomentfinder.com/openapi.json`
- Swagger UI: `https://api.videomomentfinder.com/docs`

## Supported Happy Path

- upload a video
- wait for indexing
- list videos
- search a processed video by text

REST and CLI remain the canonical public contract for one-shot upload, status polling, and search.

## Claude Connector

Remote MCP tools:

- `upload_video`
- `get_video_status`
- `list_videos`
- `search_video`

How the Claude connect flow works:

1. Add a custom connector in Claude with server URL `https://api.videomomentfinder.com/mcp`.
2. Use guided OAuth. Claude surfaces that support dynamic client registration can self-register, and internal review flows may still use provided static credentials.
3. Click `Connect`.
4. Sign in to Video Moment Finder if needed.
5. Buy a Developer Pack if your API-unit balance is zero.
6. Review the four tools and approve access.

Current MCP upload behavior:

- `upload_video(action="start")` returns a presigned `upload_url`
- write the file bytes to that URL with a plain `PUT`
- `upload_video(action="complete")` finalizes the upload

## REST Happy Path

All authenticated REST API requests use:

```text
Authorization: Bearer <vmf_api_key>
```

1. Upload one video with the one-shot multipart route.

```bash
curl -X POST https://api.videomomentfinder.com/api/v1/videos/upload \
  -H "Authorization: Bearer <vmf_api_key>" \
  -H "Idempotency-Key: sample-v1" \
  -F "file=@sample.mp4;type=video/mp4"
```

2. Poll until processing reaches `ready`:

```http
GET https://api.videomomentfinder.com/api/v1/videos/<video_id>
Authorization: Bearer <vmf_api_key>
```

3. Search by text:

```http
POST https://api.videomomentfinder.com/api/v1/videos/<video_id>/search
Content-Type: application/json
Authorization: Bearer <vmf_api_key>

{"query_text":"when do they explain the model?","limit":3}
```

## CLI Happy Path

```bash
uv sync
uv run vmf auth set \
  --api-base-url https://api.videomomentfinder.com \
  --api-key vmf_YOUR_KEY
uv run vmf videos upload ./sample.mp4
uv run vmf videos wait <video_id>
uv run vmf videos search <video_id> --query-text "when do they explain the model?"
```

## Example Prompts

1. `List my recent videos in Video Moment Finder.`
   Expected behavior: the agent or Claude connector returns recent video IDs, status, and source details.

2. `Check whether video <video_id> is ready and tell me if it failed.`
   Expected behavior: status polling plus failure detail when present.

3. `Search video <video_id> for the moment they explain the model.`
   Expected behavior: timestamped text-search results from the indexed video.

## Security Rules

- Only send OAuth tokens, Clerk JWTs, or `vmf_` API keys to `https://api.videomomentfinder.com`.
- Do not forward your `Authorization` header to a presigned `upload_url`.
- Treat raw API keys and confidential OAuth client secrets as secret material.
- Keep REST/CLI auth and MCP auth separate:
  - REST + CLI use `vmf_` API keys
  - `/mcp` uses OAuth bearer tokens

## References

- Developers overview: `https://www.videomomentfinder.com/developers`
- OpenAPI schema: `https://api.videomomentfinder.com/openapi.json`
- Swagger UI: `https://api.videomomentfinder.com/docs`
- API dashboard: `https://www.videomomentfinder.com/dashboard/api`
- Privacy policy: `https://www.videomomentfinder.com/privacy`
- Support: `https://www.videomomentfinder.com/support`