ScriptCompiler MCP server

• clear_pointswrite actionFree

  Delete points. Give axis to clear one axis, or leave it out for every axis. Give from_ms and to_ms to clear only that range. Only when the user asks to clear, delete or start over.

• control_playbackFree

  Play, pause or jump to at_ms in the user's editor, for example to have the user watch and feel one part. play and pause need a loaded video.

• create_motionwrite actionFree

  Render a described motion (or exact funscript points) and show it without playing it on a device. Needs no connection key. To play it afterwards, call play_motion with the same motion.

• derive_axisFree

  Build target_axis from source_axis over the whole script. method follow makes a scaled, optionally inverted copy shifted by delay_ms and position_offset, for example a gentler, delayed surge from the stroke. method per_stroke puts one point on each stroke of the source, moving between target_min (at the bottom) and target_max (at the top), best for vibrate.

• edit_chaptersFree

  Change the chapters: add (name, from_ms, to_ms), rename (name, new_name), retime (name, from_ms, to_ms), remove (name) or clear_all. Chapters are found by exact name and overlapping neighbours are trimmed. Only when the user asks for a chapter change.

• edit_pointsFree

  Add, move or delete single points on one axis at exact times. Every other point stays as it is. add puts each point exactly where given and replaces an existing point within replace_within_ms of it. remove_at_ms deletes the point nearest each time, within replace_within_ms. To move a point, remove its old time and add the new one. Points are not speed fitted; the result lists any part now too fast for devices. Lands in the editor at once as one Undo step.

• export_funscriptFree

  The motion as a .funscript file with ScriptCompiler metadata, for the motion card's Download button.

• look_at_videoFree

  See frames of the user's video as small pictures: one at at_ms, or up to 6 spread evenly from from_ms to to_ms. Use it to see what happens in a part, not to time single strokes. Only works after the user turns on Let my AI see video frames.

• play_motionFree

  Render a described motion (or exact funscript points) and play it on the user's device, replacing anything already playing. Returns what will actually play.

• read_pointsFree

  The points of one axis between from_ms and to_ms, thinned out evenly past 400 points, plus a summary of that range: main stroke frequency, position range and whether it builds or winds down.

• read_scriptFree

  Overview of the script open in the user's ScriptCompiler editor: each axis with its points, range, strokes and speed, parts too fast for devices (over 400 units per second), chapters, the video length, the play position, the user's selection, whether video frames are allowed, and the editor tools run_editor_tool can run. Call it first, and again after the user edits.

• run_editor_toolwrite actionFree

  Run one of the editor's own Tools panel tools (Smoothing, Speed Limiter, Simplify and the rest) on an axis, as if the user ran it. read_script lists the ids and settings. Give from_ms and to_ms for one range, or leave both out for the whole axis. A tool marked needs ScriptCompiler Pro cannot run: tell the user it is part of Pro and do not copy its effect another way. Lands as one Undo step.

• stop_motionFree

  Stop whatever is playing on the user's device.

• undo_last_changeFree

  Undo the last change you made in the editor. It refuses when the user edited those axes since, so it never undoes the user's own work.

• write_coordinated_axeswrite actionFree

  Write several axes at once from one shared stroke rhythm, so all axes keep the same beat. schedule is an ordered, gap-free list of cycles (start_ms, duration_ms, kind stroke or hold, and for strokes bottom 0, top 100, peak_frac 0.5 and intensity 50 unless given). One stroke cycle is one full down and up. A hold pauses where the last cycle ended or at its position. Each axis spec is tracking (curve snap, ease, settle, hold-peak or rise, phase_lag 0-1, amplitude, baseline, per_cycle_track) or static (position, ease_in_ms). amplitude scales the schedule depth: the stroke axis always uses amplitude 50 and baseline 50, companions use a smaller amplitude. Set speed with duration_ms and depth with bottom and top. Pass target_duration_ms when the user asks for a length; the call fails if the schedule does not match it. Lands as one Undo step and returns measured stats.

• write_pointswrite actionFree

  Replace a time range on one axis with a described motion (sections, the same as play_motion) or with exact points. With sections the motion starts at from_ms and replaces what was there until it ends. With actions the points keep their own times, or are moved so the first one lands on from_ms. The motion is fitted to 400 units per second like the Speed Limiter unless fit_to_device_speed is false. Lands in the editor at once as one Undo step. To add, move or delete single points without replacing a range, use edit_points.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 418ms (auth required)20/20
• Tool poisoning16 tool descriptions checked15/15
• Auth qualityOAuth resource metadata advertised on 40115/15
• Maintenanceno repository listed3/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

81/100

higher than 62% of 48,255 servers

Tools

16

the typical server has 7

Tools that change things

31%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

416 ms

faster than 35% of 30,031 servers

ScriptCompiler: common questions

Is ScriptCompiler MCP server safe?

Mostly: it is graded B (81/100). Read the ScriptCompiler safety report

How do I install ScriptCompiler?

It runs remotely at mcp.scriptcompiler.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does ScriptCompiler need an API key?

No key to paste: it signs you in with OAuth when your client connects.

Is ScriptCompiler maintained?

The latest release is v1.0.0.

Is ScriptCompiler up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does ScriptCompiler compare with other MCP servers?

safety score 81/100 (higher than 62% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 31% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.