Since version 1.57 there is a XML based CLI support.

The based XML schema StateData.xsd is installed in the cuttermaran folder.

Here is a example parameter file (It MUST have the extension ".cpf"):

<?xml version="1.0" standalone="yes"?>
<StateData xmlns="http://cuttermaran.kickme.to/StateData.xsd">
  <usedVideoFiles FileID="0" FileName="D:\video\test.mpv" />
  <usedAudioFiles FileID="0" FileName="D:\video\test.mp2" />
  <usedAudioFiles FileID="1" FileName="D:\video\test.ac3" />
  <CutElements refVideoFile="0" StartPosition="35" EndPosition="155">
    <cutAudioFiles refAudioFile="0" />
    <cutAudioFiles refAudioFile="1" />
  </CutElements>
  <CurrentFiles refVideoFiles="0">
    <currentAudioFiles refAudioFiles="0" />
    <currentAudioFiles refAudioFiles="1" />
  </CurrentFiles>
  <CmdArgs OutFile="D:\video\xyz.mpv" cut="true" unattended="true" snapToCutPoints="true" closeApp="true" />
</StateData>

All used Video- and Audiofiles must enumerated in the <usedVideoFiles> and <usedAudioFiles> tags.
Every cut contains a refenceID to the used videofile and the framenumbers of the CutIn and CutOut points.
After that, it is possible to reference the pending audiofiles in the <cutAudioFiles> elements

With <CmdArgs> Element the following arguments are used:

OutFile Name of the result video file with extension.
cut Starts the cut immediately. Takes no effect if OutFile isn't used.
cutAudio Starts the cut audio immediately. Takes no effect if OutFile isn't used or 'cut' is set.
unattended At the end of cut process no message will appear.
closeApp At the end of cut process Cuttermaran will close automatically.
snapToCutPoints If the CutIn frames are no I-Frames or the CutOut frames are no P-Frames. Cuttermaran moves to the next I-Frame (or P-Frame) automatically.