Harmar MCP captions

Remote MCP: add a custom connector in Claude Settings → Connectors with https://api.harmar.ai/mcp, then complete Harmar sign-in and authorization. This route uses App minutes and saved styles. Check whether your Claude account currently offers custom connectors. Harmar connection steps.

Local MCP / CLI: Harmar documents the harmar-ai package with HARMAR_API_KEY. Obtain the secret from your own API account and keep it in local secret configuration, never in a shared prompt or repository. This route uses separate prepaid API credit. Developer setup and authentication.

Before submitting media, record which route you selected and its available allowance. A connected account is a useful setup check; it is not evidence that a caption job has finished.

The App free plan lists 5 minutes per month, videos up to 3 minutes, and a logo on exports. Check the current plan before choosing a delivery format; SRT/VTT and higher-resolution entitlements differ. App plans.

Do not assume App minutes refill an API balance. Confirm API pricing in your account before a job; we have not verified an authenticated price quote. Choose the route first, then evaluate its total cost.

For remote MCP, use a video already uploaded in the App or a Google Drive / Dropbox link shared for access. A phone filename alone is insufficient. Instagram, TikTok and YouTube page URLs are not supported inputs. Remote input requirements.

For API input, the documented upload limit is 5 GB / 60 minutes; URL fetching is limited to 2 GB. Supported uploads include MP4, MOV, WebM, M4A, MP3 and WAV. API input options.

Choose a short clip that you own or have permission to process. Check that any sharing permission is appropriate for its content. Use a unique video name so the assistant does not select a similarly named project.

An original request you can adapt

Use my Harmar video named [exact title]. First identify the video and my remaining allowance. I want [SRT, VTT, or captioned MP4] in [language]. Tell me if that output needs another charge. Ask before processing or exporting. When it finishes, return the job or video reference and the download location. Do not publish it anywhere.

Fill in every bracket before sending. Review the assistant's proposed input and action; a conversational promise to ask is not a technical spending limit. For translated subtitles, confirm the supported source/target pair in the developer reference instead of assuming arbitrary language combinations.

Download the caption handoff checklist to record your input, chosen output and acceptance checks.

SRT or VTT is a timed text track. Use it when a player or editor will handle presentation. Burned-in captions become visible pixels in the exported video. They are different deliverables: downloading a subtitle track does not produce a captioned MP4.

API burn-in requires keep_media: true, adds a render charge, and is documented up to 1080p, with one export per account at a time. API export contract. The same page's pricing example still marks rendered captions unavailable; confirm account availability before relying on that route. App advertising for 4K or alpha output does not establish API support.

Check the deliverable before handing it over

• Text: compare names, numbers and each language change with the audio. Correct errors rather than relying on an accuracy claim.
• Timing: review the beginning, middle and end, plus a fast exchange. Captions should appear with the corresponding speech.
• Track: make sure the requested source or translation track is present and opens in your target editor or player.
• Video: play the actual downloaded file; check readable text, cropping, duration, resolution and any logo. A completed status alone is insufficient.

Keep your original media and reviewed subtitle file separately from a temporary result link. This gives you something to edit or deliver even if you later change services.

When an API job is processing, poll its existing transcript ID. For a queued export, check the export status for that same ID; avoid repeated submissions. Completed export links last one hour; fetching the export status again can return a fresh link. API status and downloads.

• Connection fails: confirm the selected account and connector authorization. For the API route, check the key configuration without copying the secret into a support transcript.
• Input rejected: inspect the returned reason. Check sharing permission, file type and size before trying again; replace a social page URL with a supported file input.
• Insufficient allowance: stop and inspect the balance for the selected route. Changing the request wording will not add minutes.
• Queue or network interruption: retain the video/job ID and check its status before deciding whether a new attempt is necessary.
• Failed render or missing source: read the recorded error and inspect source availability before requesting a new render. Verify the balance record rather than assuming a refund has already arrived.

Download before the retention window closes

API source media is normally removed after transcription. With keep_media, media and renders last 24 hours after the last activity; transcripts last 30 days. API retention policy.

These API windows are not a promise about App project storage. Review the Harmar privacy policy for account data and deletion. Disconnecting the remote connector leaves the Harmar account and videos in place. Disconnect behavior.