SMPTE Timecode Calculator MCP for AI. Calculate frame-accurate video math with absolute precision.

Q: How does addtimecodes handle drop-frame video formats?

The addtimecodes tool automatically accounts for NTSC 29.97 or 59.94 drop-frame logic when performing additions. You just provide the timecode strings and the framerate, and it handles the complex math.

Q: Should I use addtimecodes or subtracttimecodes for finding duration?

You should use subtracttimecodes. This tool is designed to calculate the difference between two marks, giving you a precise measurement of time elapsed. While addition could work in some cases, subtraction is the intended function for measuring segments.

Q: How do I convert raw frames to an SMPTE timecode using this server?

Use framestotimecode. You pass the total absolute frame count and the correct framerate (e.g., 24 or 30). It converts that number into a fully formatted, readable timecode string.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

SMPTE Timecode Calculator. This tool handles complex base-60 math for video professionals. You add, subtract, and convert SMPTE timecodes using native drop-frame logic (like 29.97 or 59.94).

It fixes the common problem where LLMs hallucinate when dealing with frame-accurate calculations.

What your AI can do

Add timecodes

Adds two SMPTE timecodes together, supporting drop-frame logic and specific framerates.

Frames to timecode

Converts a total absolute frame count into an official SMPTE formatted timecode string.

Subtract timecodes

Calculates the difference between two SMPTE timecodes, useful for measuring segment lengths.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

SMPTE Timecode Calculator: 3 Tools for Media Ops

These three tools let you perform complex base-60 arithmetic on video timecodes. Use them to calculate offsets, measure segments, or convert raw frames into accurate SMPTE strings.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using SMPTE Timecode Calculator on Vinkius

Add Timecodes

Adds two SMPTE timecodes together, supporting drop-frame logic and specific framerates.

Frames To Timecode

Converts a total absolute frame count into an official SMPTE formatted timecode...

Subtract Timecodes

Calculates the difference between two SMPTE timecodes, useful for measuring segment...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The SMPTE Timecode Calculator integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "smpte-timecode-calculator": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the SMPTE Timecode Calculator tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"smpte-timecode-calculator": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with SMPTE Timecode Calculator, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

SMPTE Timecode Calculator MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by smpte-timecode. 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.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Manually calculating timecode offsets shouldn't require a math degree.

Right now, if you need to calculate an offset—say, finding out what timecode starts exactly 30 seconds after your current marker—you’re wrestling with spreadsheets and complex formulas. You have to manually account for the framerate (24fps vs 25fps), worry about day rollovers, and constantly check if you've remembered drop-frame logic. It’s tedious, error-prone, and eats up time.

With this MCP server, you skip all that manual math. You just tell your agent the two marks and the framerate. The tool runs `add_timecodes` or `subtract_timecodes`, giving you a single, verified timecode string—no guesswork involved.

The SMPTE Timecode Calculator MCP Server: Calculate video math from chat.

You used to stop work to look up broadcast timing guides or run scripts just to verify simple offsets. You'd copy-paste timecodes into a utility, hoping the tool handled the drop-frame logic correctly every time.

Now, you let your agent handle it. Whether you need `add_timecodes` for offset calculation or `frames_to_timecode` for conversion, the math is done natively and flawlessly, letting you keep moving through the pipeline.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

When you're working with video timing, general-purpose AI models fail. They choke on base-60 math; they can’t handle drop-frame logic accurately. This tool fixes that mess. It’s built for media pipelines that require frame-accurate arithmetic. You give it the start and end points—the server runs the complex math natively, guaranteeing your timecodes are mathematically sound.

add_timecodes calculates the exact offset when you add two SMPTE timecodes together, handling every necessary frame rollover. If you're dealing with drop-frame standards or specific framerates, this tool manages that complexity for you. You can figure out the absolute end point if you know the starting marker and the duration needed.

It doesn't just sum numbers; it understands how video time actually moves.

Need to measure a segment? Use subtract_timecodes to calculate the precise difference between any two SMPTE timecodes. This function lets you determine exact segment lengths or figure out what the start point needs to be relative to an endpoint. You simply feed it the pair of markers, and it spits out the accurate duration without any math errors.

If your data exists as raw numbers—a total absolute frame count—you'll use frames_to_timecode. This tool takes that raw frame number and converts it into a proper SMPTE formatted timecode string. You specify the total frame count alongside the framerate, and you get an official, usable timecode. It’s your conversion utility for turning pure counts into industry-standard markers.

When you're calculating offsets, add_timecodes works with specific framerates to ensure the addition accounts for drop-frame logic at every step of the calculation. You're not just adding hours and minutes; you’re adding time in a way that video editors expect. For instance, if you know a segment is 30 frames long, using subtract_timecodes lets you pinpoint where it starts by subtracting that duration from your final timestamp.

The system handles the arithmetic for both addition and subtraction, so whether you're measuring elapsed time or finding a future marker point, the math holds up. If you only have raw data—say, '150,000 frames' at 30 fps—you don’t have to guess how that translates into SMPTE format; frames_to_timecode handles the structure conversion automatically.

It turns a simple count into usable time for your NLE or archival system.

You can use these tools together in sequence. For example, you might first convert a raw frame count using frames_to_timecode, then take that resulting marker and add a calculated duration to it using add_timecodes. This chaining capability means the whole process stays within mathematically verifiable video time parameters. You're eliminating guesswork from your post-production math.

Remember, these tools don’t just perform arithmetic; they enforce industry standards for base-60 calculations that general AI models simply can’t replicate. It's reliable timing math built directly into the server.

Built · Hosted · Managed by Vinkius SMPTE Timecode Calculator - Video Frame Math

Server ID 019e3907-532f-720a-ab2f-061aaef95c4d

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is you get reliable, frame-accurate video timing calculations that standard LLMs can't touch.

Start by identifying the required mathematical operation: are you adding offsets, subtracting marks, or converting raw frames?

Pass the necessary inputs to one of the three tools—for example, providing two timecode strings and the target framerate (e.g., 29.97) if using add_timecodes.

The server executes the base-60 math natively and returns a single, mathematically verified SMPTE formatted string result.

Who is this actually for?

This tool is essential for anyone running professional video pipelines. If your job involves syncing multiple camera feeds, trimming archival footage, or setting up automated broadcast markers, you need this. It saves the post-production specialist from hours of manual spreadsheet debugging and prevents expensive sync errors.

Post-Production Editor

Uses add_timecodes to calculate segment offsets when syncing multiple camera angles or adding effects that require specific time markers.

Broadcast Engineer

Relies on the tool's drop-frame support to ensure accurate timing calculations for broadcast compliance (e.g., 29.97 fps math).

Media Asset Manager

Uses frames_to_timecode to quickly translate raw frame counts from metadata logs into usable timecode formats.

What Changes When You Connect

Accurate Offset Calculation: Use add_timecodes to find the exact time difference between two marks. It correctly handles complex base-60 rollovers and day transitions, something general LLMs struggle with.

Broadcast Compliance: The server supports NTSC drop-frame logic (like 29.97 fps). This means your timing calculations respect industry standards, preventing synchronization failures on air.

Instant Conversion: Need to map a frame count from metadata? frames_to_timecode takes an absolute number and instantly turns it into the correct HH:MM:SS:FF timecode string.

Precise Measurement: Use subtract_timecodes to measure segment lengths or find starting points relative to an endpoint. You get a mathematically verifiable duration, not just an approximation.

Reliable Workflow: By offloading this math to the dedicated server, you keep your video pipeline accurate and fast. No more manual spreadsheet checks needed.

See it in action

01 01

Syncing Multi-Camera Footage

A post editor has two camera takes that need to line up perfectly at the 3:05 mark. Instead of manually calculating the offset, they ask their agent to run add_timecodes, providing both start marks and the framerate. The tool returns a single, precise timecode for perfect synchronization.

02 02

Calculating Clip Duration from Logs

You receive a log file stating that a segment runs from frame 1500 to frame 3200 at 24fps. Instead of converting both numbers, you use frames_to_timecode and then run subtract_timecodes to get the exact duration in timecode format.

03 03

Finding a Start Point from an End Marker

The client wants to know what timecode starts exactly 1 minute before the final marker at 00:05:00:00. The agent runs subtract_timecodes, passing the end mark and a duration of one minute, getting the exact starting point instantly.

04 04

Testing Drop-Frame Markers

You are testing if your broadcast system correctly calculates offsets at 29.97 drop-frame. You run add_timecodes with two known marks and let the tool handle the complex math, guaranteeing the result is compliant.

The honest tradeoffs

Using generic LLMs for timing.

Anti-pattern

Asking a general AI model: 'What is 00:01:23:14 plus 00:02:45:21 at 29.97 drop-frame?' The result will be an educated guess, not the mathematically correct timecode.

The Fix

Use add_timecodes. This tool runs video math natively and handles complex base-60 arithmetic with proven accuracy.

Calculating duration in spreadsheets.

Anti-pattern

Manually calculating offsets or converting frame counts into timecode columns in Excel. You'll inevitably forget the specific framerate, leading to hours of manual cross-checking and inevitable errors.

The Fix

Use subtract_timecodes for measurement, or use frames_to_timecode if you only have raw frame numbers. It keeps your calculation within a dedicated, accurate environment.

Ignoring drop-frame logic.

Anti-pattern

Attempting to calculate time offsets using standard linear math when working with broadcast formats like 29.97 fps. The result will be off by several frames and unusable for final delivery.

The Fix

Always pass the correct framerate (e.g., 29.97) when calling add_timecodes. This ensures the tool uses drop-frame logic.

When It Fits, When It Doesn't

Use this server if your workflow requires frame-accurate temporal arithmetic in media production. Specifically, you need to calculate offsets or convert timecode marks while respecting base-60 mathematics and broadcast standards like drop-frame (e.g., 29.97 fps). If your only task is simple duration calculation within a single file, a basic math library might suffice. However, if the problem involves converting between raw frame counts and standard timecode formats, or calculating offsets across multiple markers, this toolset (add_timecodes, subtract_timecodes) is necessary. Do NOT use this if you just need to know how many seconds are in an hour—that's simple division. This tool handles the complexity of video timing.

Questions you might have

How does add_timecodes handle drop-frame video formats? +

The add_timecodes tool automatically accounts for NTSC 29.97 or 59.94 drop-frame logic when performing additions. You just provide the timecode strings and the framerate, and it handles the complex math.

Should I use add_timecodes or subtract_timecodes for finding duration? +

You should use subtract_timecodes. This tool is designed to calculate the difference between two marks, giving you a precise measurement of time elapsed. While addition could work in some cases, subtraction is the intended function for measuring segments.

How do I convert raw frames to an SMPTE timecode using this server? +

Use frames_to_timecode. You pass the total absolute frame count and the correct framerate (e.g., 24 or 30). It converts that number into a fully formatted, readable timecode string.

Does SMPTE Timecode Calculator support different framerates? +

Yes. All three tools require the specific framerate (e.g., 24, 25, 30) as an input parameter to ensure the base-60 math is applied correctly for that video standard.

What are the required inputs when I call the `add_timecodes` tool? +

The tool needs three specific parameters: two SMPTE timecode strings and the exact framerate. You must provide the framerate (e.g., 29.97 or 30) so it can correctly handle base-60 arithmetic.

If I use `subtract_timecodes` with non-standard timecode formats, what happens? +

The server requires two valid SMPTE formatted strings and a framerate. If the inputs don't match the expected structure or rates, it will return a validation error telling you exactly which parameter failed.

Can `frames_to_timecode` handle timecodes from international standards other than NTSC? +

Yes. The tool calculates based on the framerate you supply. As long as you specify the correct base-60 parameters for your video format (like 25fps/PAL), it manages the conversion accurately.

Are there any rate limits when running multiple calculations with `add_timecodes`? +

Vinkius handles connection management, but high-volume batch processing may hit standard API rate limits. If you need to calculate hundreds of times, check our service documentation for bulk usage advice.

Does it support drop-frame? +

Yes, pass the dropFrame boolean parameter for exact NTSC compliance.

What framerates are supported? +

All standard rates: 23.976, 24, 25, 29.97, 30, 50, 59.94, 60.

Can it convert frames to timecode? +

Yes, absolute frame counting to SMPTE string is supported.

Connect to your AI in seconds.

Add timecodes

Frames to timecode

Subtract timecodes

SMPTE Timecode Calculator: 3 Tools for Media Ops

Make your AI actually useful.

Add Timecodes

Frames To Timecode

Subtract Timecodes

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Manually calculating timecode offsets shouldn't require a math degree.

The SMPTE Timecode Calculator MCP Server: Calculate video math from chat.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

Syncing Multi-Camera Footage

Calculating Clip Duration from Logs

Finding a Start Point from an End Marker

Testing Drop-Frame Markers

The honest tradeoffs

Using generic LLMs for timing.

Calculating duration in spreadsheets.

Ignoring drop-frame logic.

When It Fits, When It Doesn't

Questions you might have