MCP MCP Server

FFmpeg MCP server. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

An MCP server that allows you to run Node.js scripts and npm commands, with permission prompts via node-notifier.

• Run Node.js scripts with arguments and standard input
• Execute npm scripts from package.json files with standard input
• Run JavaScript code directly with Node's eval and provide standard input
• Start Node.js servers that continue running in the background
• List running servers and view their status
• Stop running servers gracefully or forcefully when needed

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

• DISABLE_NOTIFICATIONS — Set DISABLE_NOTIFICATIONS=true to automatically approve all permission requests without showing notification prompts:
• EVAL_DIRECTORIES — Specify a colon-separated list of directories where JavaScript code can be evaluated using the run-node-eval tool:

Configuration

You will need 2 environment variables: DISABLE_NOTIFICATIONS, EVAL_DIRECTORIES. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 22.0.0

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

When to reach for it

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — DISABLE_NOTIFICATIONS, EVAL_DIRECTORIES — is a fair guide to whether it matches your workflow. It is maintained by oivoodoo; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.