F
licenseA
qualityB
maintenanceEnables broad media and document format conversion (audio, video, images, Office, data, ebooks, PDF, subtitles) through an MCP server with smart routing, batch processing, and multiple conversion engines.
14
154
-
CutConvert
Server Details
Convert subtitles, transcripts, broadcast captions (SCC/MCC/STL), EDLs, and Premiere files.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
4 toolsconvert_fileConvert a post-production fileAInspect
Convert a subtitle, transcript, caption, EDL, FCPXML, or Premiere .prtranscript file. Pass text file contents in content; pass binary files (.prtranscript) as base64 in content_base64. The filename extension drives format detection. Use target from list_converters to pick the output, or leave it as "auto" to get the default output for the detected format. Returns the converted file content (text formats inline; DOCX/ZIP as base64).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | Conversion target id from list_converters, or "auto" for the default output. | |
| content | No | The file content for text formats (SRT, VTT, TXT, EDL, JSON, FCPXML, …). | |
| filename | Yes | Original file name including extension, e.g. "episode1.srt" — drives format detection. | |
| frame_rate | No | Frame rate for frame-based outputs such as ITT. Defaults to auto. | |
| content_base64 | No | Base64-encoded bytes for binary formats (.prtranscript). | |
| caption_language | No | BCP 47 caption language for ITT/TTML, e.g. en-US or ja. Defaults to the source language or undetermined. |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses behaviors beyond the annotations: filename extension drives format detection, 'auto' picks the default output for the detected format, and return values differ by format (text inline, DOCX/ZIP as base64). With no output schea, this return-format disclosure is valuable. Annotations (readOnly=false, destructive=false) aren't contradicted — conversion is neither read-only nor destructive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Four sentences, each earning its place: input formats, input-passing rules, format detection and target selection, and return behavior. Logically ordered from purpose to invocation, with no filler and no redundant restating of schema content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers the call-critical decisions: which parameter to populate (content vs content_base64), how detection works (filename extension), and what to expect back (text vs base64). frame_rate and caption_language are optional and fully documented in the schema (100% coverage), so their absence from the description is acceptable. Doesn't cover error behavior, but that's minor here.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schea coverage is 100%, so baseline is 3. The description adds real meaning: it maps content/content_base64 to text vs binary, identifies .prtranscript as the binary case, explains that filename drives detection, and clarifies that target defaults to 'auto'. That's genuine value beyond the schema fields.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Convert') plus an explicit resource: subtitle, transcript, caption, EDL, FCpXML, or Premiere .prtranscript file. The enumerated formats and the clear contrast with siblings (inspect_file, list_converters, timecode_calculate) make the tool's role unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives actionable guidance: text goes in `content`, binary (.prtranscript) goes base64 in `content_base64`, filename drives detection, and `target` values come from list_converters — naming the sibling directly. It doesn't state explicit when-not-to-use conditions, but the binary/text split and the 'auto' fallback are enough to route an agent correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
inspect_fileDetect a file’s formatARead-onlyInspect
Detect the format of a subtitle/transcript/EDL/FCPXML file and report what CutConvert would produce from it, without performing the conversion or using quota.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | No | File content (text formats). | |
| filename | Yes | Original file name including extension. | |
| content_base64 | No | Base64 bytes (binary formats like .prtranscript). |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already covers non-mutation, and the description adds that the tool does not use quota, which is valuable cost-related context. It also clarifies it only reports, not executes, the conversion. This goes beyond the annotation and provides useful behavioral detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the core purpose and immediately states key constraints (no conversion, no quota). It contains no unnecessary words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description informs the agent that the tool returns a report of what CutConvert would produce, which is essential for understanding the result. It also notes quota behavior. It doesn't specify edge cases (e.g., unknown formats), but for a detection tool this is adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully describes all three parameters (content, filename, content_base64) with clear meanings, giving 100% schema coverage. The description adds no extra information about parameters, so it stays at the baseline of 3 as the schema handles the semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action (detect format) and a specific resource (subtitle/transcript/EDL/FCPXML files), and explicitly distinguishes it from conversion by noting it does not perform conversion. This separates it cleanly from the sibling tools convert_file, list_converters, and timecode_calculate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description indicates when to use this tool ('without performing the conversion') and mentions it reports what CutConvert would produce, implying it's a pre-conversion inspection. It does not explicitly name alternatives, but the purpose is clear enough for an agent to infer that convert_file is for actual conversion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_convertersList supported convertersARead-onlyInspect
List every conversion CutConvert supports (source format, output format, and the target id to pass to convert_file).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint=true and openWorldHint=false, which already communicate that this is a safe, read-only operation with a closed world. The description adds value by specifying the exact contents of the list (source format, output format, target id) without contradicting the annotations. It does not mention pagination or ordering, but these are not critical for a zero-parameter list tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, front-loaded with the action ('List every conversion') and then provides essential detail about the returned fields. No redundant wording or repetition of the title or annotations. Easily parseable at a glance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, non-destructive list tool, the description is complete: it names the resource, specifies the output content, and even links to the downstream process (convert_file). With annotations covering the read-only nature, an agent has everything needed to call the tool correctly and interpret the result. No output schema exists, but the description effectively substitutes for it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description correctly does not attempt to explain parameters that don't exist. The schema coverage is 100% (trivially, since there are no properties), so nothing further is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('conversions CutConvert supports') and clearly states what it returns: source format, output format, and target id. This distinguishes it from siblings like convert_file (which performs conversion) and inspect_file (which inspects). No ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly mentions the target id 'to pass to convert_file', which signals the primary use case: retrieve supported conversions before calling convert_file. It implies usage context but does not explicitly state alternatives or exclusions. For a simple listing tool, this is clear enough; a fully explicit 'use this to discover available formats before converting' would push it to 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
timecode_calculateSMPTE timecode calculatorARead-onlyInspect
Parse an SMPTE timecode at a frame rate (including 29.97/59.94 drop-frame) and report its frame count and real elapsed seconds; optionally re-express it at another rate.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | When converting rates: "time" keeps the same real-world moment (conform, default); "frames" keeps the frame count (reinterpret). | |
| rate | Yes | Frame rate the timecode is expressed in. | |
| to_rate | No | Optional target frame rate to convert to. | |
| timecode | Yes | Timecode like "01:00:02:12" (use ";" before frames for drop-frame). |
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already disclose readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful output behavior (frame count and elapsed seconds) and mentions drop-frame support, but it does not describe edge cases, error handling, or the exact return structure, which are relevant since there is no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, tightly worded sentence that leads with the core parsing behavior, states the outputs, and then introduces the optional conversion. Every clause carries information with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a moderately complex calculator without an output schema, the description names the main outputs and the optional conversion target. The schema fully covers parameter semantics, including drop-frame notation and mode behavior. It falls slightly short only by not giving an example or explaining invalid-input behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema provides detailed descriptions for timecode, rate, to_rate, and mode, including enum values and the semantic difference between 'time' and 'frames'. The description itself adds little parameter-level meaning beyond framing the tool as a timecode calculator.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action (parse SMPTE timecode at a given frame rate) and explicit outputs (frame count, real elapsed seconds), plus an optional conversion behavior. This distinguishes it from sibling tools like convert_file and inspect_file, whose domains are file operations rather than timecode math.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is given about when to choose this tool over alternatives, nor are there exclusion conditions. The intended usage is only implied by the domain of the description; the siblings are not referenced or differentiated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "fcpxmlAaf", - "prprojRpp", - "sesxRpp", - "avbCsv", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtSbv", - "srtAss", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "fcpxmlXml", - "fcpxmlDrp", - "fcpxmlEdl", - "fcpxmlShotlist", - "drpXml", - "prprojCsv", - "prprojEdl", - "prprojFcpxml", - "drpFcpxml", - "aafFcpxml", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "srtItt", - "srtTtml", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonJson", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "fcpxmlAaf", + "prprojRpp", + "sesxRpp", + "avbCsv", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtSbv", + "srtAss", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "fcpxmlXml", + "fcpxmlDrp", + "fcpxmlEdl", + "fcpxmlShotlist", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "srtItt", + "srtTtml", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonJson", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt", + "aafRpp", + "fcpxmlRpp", + "drpRpp" +]
1 tool update
- Changed
convert_file3 fields changed- added
Input schema / properties / caption_languageAdded value: +{ + "description": "BCP 47 caption language for ITT/TTML, e.g. en-US or ja. Defaults to the source language or undetermined.", + "type": "string" +} - added
Input schema / properties / frame_rateAdded value: +{ + "description": "Frame rate for frame-based outputs such as ITT. Defaults to auto.", + "enum": [ + "auto", + "23.976", + "24", + "25", + "29.97", + "30", + "50", + "59.94", + "60" + ], + "type": "string" +} - changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "fcpxmlAaf", - "prprojRpp", - "sesxRpp", - "avbCsv", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtSbv", - "srtAss", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "fcpxmlXml", - "fcpxmlDrp", - "fcpxmlEdl", - "fcpxmlShotlist", - "drpXml", - "prprojCsv", - "prprojEdl", - "prprojFcpxml", - "drpFcpxml", - "aafFcpxml", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonJson", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "fcpxmlAaf", + "prprojRpp", + "sesxRpp", + "avbCsv", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtSbv", + "srtAss", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "fcpxmlXml", + "fcpxmlDrp", + "fcpxmlEdl", + "fcpxmlShotlist", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "srtItt", + "srtTtml", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonJson", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtSbv", - "srtAss", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "fcpxmlXml", - "fcpxmlDrp", - "fcpxmlEdl", - "fcpxmlShotlist", - "drpXml", - "prprojCsv", - "prprojEdl", - "prprojFcpxml", - "drpFcpxml", - "aafFcpxml", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonJson", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "fcpxmlAaf", + "prprojRpp", + "sesxRpp", + "avbCsv", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtSbv", + "srtAss", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "fcpxmlXml", + "fcpxmlDrp", + "fcpxmlEdl", + "fcpxmlShotlist", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonJson", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "fcpxmlXml", - "fcpxmlDrp", - "fcpxmlEdl", - "fcpxmlShotlist", - "drpXml", - "prprojCsv", - "prprojEdl", - "prprojFcpxml", - "drpFcpxml", - "aafFcpxml", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonJson", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtSbv", + "srtAss", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "fcpxmlXml", + "fcpxmlDrp", + "fcpxmlEdl", + "fcpxmlShotlist", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonJson", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "fcpxmlXml", - "fcpxmlDrp", - "drpXml", - "prprojCsv", - "prprojEdl", - "prprojFcpxml", - "drpFcpxml", - "aafFcpxml", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonJson", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "fcpxmlXml", + "fcpxmlDrp", + "fcpxmlEdl", + "fcpxmlShotlist", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonJson", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "fcpxmlXml", - "fcpxmlDrp", - "drpXml", - "prprojCsv", - "prprojEdl", - "prprojFcpxml", - "drpFcpxml", - "aafFcpxml", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "fcpxmlXml", + "fcpxmlDrp", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonJson", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "drpXml", - "prprojCsv", - "prprojEdl", - "prprojFcpxml", - "drpFcpxml", - "aafFcpxml", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "fcpxmlXml", + "fcpxmlDrp", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "drpXml", - "prprojCsv", - "prprojEdl", - "drpCsv", - "drpEdl", - "aafCsv", - "aafEdl", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "drpXml", + "prprojCsv", + "prprojEdl", + "prprojFcpxml", + "drpFcpxml", + "aafFcpxml", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
1 tool update
- Changed
convert_file1 field changed- changed
Input schema / properties / target / enumPrevious value: -[ - "auto", - "srtJson", - "srtAvidTxt", - "txtSrt", - "edlCsv", - "txtJson", - "wordJson", - "srtVtt", - "prtranscriptSrt", - "prtranscriptVtt", - "vttSrt", - "srtText", - "vttText", - "prprojXml", - "prprojDrp", - "aafXml", - "aafDrp", - "drpXml", - "prtranscriptDocx", - "prtranscriptCsv", - "capcutSrt", - "jsonVtt", - "jsonDocx", - "jsonText", - "sccCsv", - "mccCsv", - "stlCsv", - "fcpxmlDocx", - "fcpxmlCsv", - "prtranscriptText", - "sbvSrt", - "srtDocx", - "vttDocx", - "assSrt", - "jsonSrt", - "srtCsv", - "csvSrt", - "srtFcpxml", - "fcpxmlSrt", - "srtScc", - "sccSrt", - "srtMcc", - "mccSrt", - "srtStl", - "stlSrt" -]New value: +[ + "auto", + "srtJson", + "srtAvidTxt", + "txtSrt", + "edlCsv", + "txtJson", + "wordJson", + "srtVtt", + "prtranscriptSrt", + "prtranscriptVtt", + "vttSrt", + "srtText", + "vttText", + "prprojXml", + "prprojDrp", + "aafXml", + "aafDrp", + "drpXml", + "prprojCsv", + "prprojEdl", + "drpCsv", + "drpEdl", + "aafCsv", + "aafEdl", + "prtranscriptDocx", + "prtranscriptCsv", + "capcutSrt", + "jsonVtt", + "jsonDocx", + "jsonText", + "sccCsv", + "mccCsv", + "stlCsv", + "fcpxmlDocx", + "fcpxmlCsv", + "prtranscriptText", + "sbvSrt", + "srtDocx", + "vttDocx", + "assSrt", + "jsonSrt", + "srtCsv", + "csvSrt", + "srtFcpxml", + "fcpxmlSrt", + "srtScc", + "sccSrt", + "srtMcc", + "mccSrt", + "srtStl", + "stlSrt" +]
4 tool updates
- First observed
convert_file - First observed
inspect_file - First observed
list_converters - First observed
timecode_calculate
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Convert files between formats without quality loss. Speed up your workflow with fast, reliable con…
Convert between 200+ format pairs: JSON, CSV, XML, YAML, PDF, Excel, DOCX and more.
Convert files between 400+ image, video, audio, document, ebook, archive and font formats.
File conversion: PDF, DOCX, STT, TTS, watermarking
Related MCP Servers
- FlicenseAqualityDmaintenanceEnables processing and translating SRT subtitle files with intelligent conversation detection and context preservation. Supports parsing, validation, chunking of large files, and translation while maintaining precise timing and HTML formatting.6-
- AlicenseNot gradedqualityCmaintenanceFile conversion built for AI agents. CLI, REST API, and MCP server — all sharing one engine.141MIT
- AlicenseAqualityDmaintenanceEnables file conversion between 690+ formats (image, video, audio, document, data, font, ebook, archive) using an MCP server, with no API key or signup required.2185MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool has a clearly distinct role: conversion, format inspection, listing supported conversions, and timecode calculation. There is no meaningful overlap between them, and the descriptions reinforce their separate purposes.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern like convert_file, inspect_file, and list_converters. timecode_calculate breaks the pattern slightly by using noun_verb, but the style is otherwise consistent and readable.
Tool Count5/5
Four tools is a well-scoped set for a conversion-focused server. Each tool earns its place by covering conversion, discovery, inspection, and a supporting timecode utility without unnecessary redundancy.
Completeness5/5
The core conversion workflow is fully supported: users can discover formats, inspect files without consuming quota, and perform conversions. The additional timecode calculator fills a natural supporting need for media workflows.