How to Use the CaptionHub MCP in Cursor

Build video localization workflows in Cursor. Let Agent mode trigger transcriptions and pull live caption data while you write code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CaptionHub MCP to Cursor

Create your Vinkius account to connect CaptionHub to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup CaptionHub with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Wire up the CaptionHub MCP Server in Agent mode.

Hardcoding mock translation data wastes time. You can ask Cursor to pull real localization targets into your test suite. The agent runs `list_projects` and drops actual staging data right into your editor. Building custom dashboards goes much faster when your AI client knows the exact API shape. It uses `get_project_details` to read the live JSON response. Then it writes the frontend components to match those exact fields.

Script your transcription pipelines.

Writing automation logic requires knowing how the platform handles state changes. Cursor can test the flow by firing `create_project` and immediately calling `transcribe_video`. You watch the real-time interaction before committing any code. Once the base text finishes, you need to handle the output. The MCP tools let the AI use `export_captions` to grab the real download URLs. It then drafts the exact download functions your app needs to fetch those subtitle files.

Manage webhooks and system state.

Debugging failed callbacks is frustrating when you cannot see the active endpoints. Tell your editor to run `list_webhooks` to verify where the platform is sending events. The agent checks the list and spots configuration errors in your routing logic. Cleaning up test data shouldn't require opening a browser. Cursor just calls `archive_project` on your temporary builds. It also hits `get_account_info` to make sure your automated tests haven't burned through your API limits.

Setup guide

Set up CaptionHub MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the CaptionHub MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent CaptionHub transactions." If the MCP tools are loaded correctly, Cursor will call the CaptionHub tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "captionhub-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by CaptionHub. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect CaptionHub now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about CaptionHub MCP in Cursor

Create an mcp.json file in your project root directory. Add the Vinkius endpoint URL under the mcpServers array. Turn on Agent mode in the chat panel to activate the tools.

Yes, the agent understands the exact required payload. It uses the `approve_captions` tool to test the state change. Then it generates the corresponding Node or Python code for your application.

The AI might be trying to guess the endpoint structure instead of reading it. Force it to run `list_webhooks` explicitly. That guarantees it uses the real system state instead of hallucinated data.

Yes, you can commit the .cursor/mcp.json file to your repository. Anyone who pulls the repo will automatically get the same toolset. Just make sure you manage the Vinkius token securely via environment variables.

Requests route through a zero-trust V8 Isolate Sandbox on Vinkius. The MCP integration only transmits project IDs, webhook configurations, and caption text during the active tool call. Your proprietary translation data never sits in persistent storage.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript