Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Audio metadata, conversion, trimming, normalization, and transcription via ffmpeg.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"audioport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/audioport",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add audioport -- npx -y @reneturcios/audioport mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"audioport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/audioport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"audioport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/audioport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
audioport does everyday audio work on local files. It reads the facts ffprobe reports about a file — its format, duration, bit rate, sample rate, and channel count — converts between the common audio formats, cuts a segment out of a file starting at a chosen second, and normalizes loudness with ffmpeg's loudnorm filter. A fifth tool transcribes, but only through a transcription engine you configure yourself; audioport bundles no engine and invents no transcripts.
All processing runs through the ffmpeg and ffprobe binaries on the machine, invoked with argument arrays (never a shell), so those binaries must be installed for the processing tools to work. When they are missing, the binary's own error is returned instead of a made-up result.
Transcription is delegated to a local command named by the AUDIOPORT_TRANSCRIBER_COMMAND environment variable. The command is run with the audio file path as its last argument, and its stdout is the transcript. For example:
export AUDIOPORT_TRANSCRIBER_COMMAND="whisper-cli --model base"
When the variable is unset, transcribe and the transcribe_audio tool fail with an error naming AUDIOPORT_TRANSCRIBER_COMMAND. There is no API key, no hosted service, and no fallback that guesses at the words.
npx @reneturcios/audioport metadata song.mp3
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/audioport
The container defaults to the MCP server (see below) and bundles no ffmpeg/ffprobe; use a host install, or a derived image with ffmpeg installed, for the processing tools. Pass CLI arguments to use it as a CLI instead.
audioport metadata song.mp3
audioport convert song.wav song-out.mp3 mp3 --bitrate 192k audioport trim song.mp3 clip.mp3 5 --duration 10 audioport normalize song.wav song-normalized.wav audioport transcribe song.mp3 --language en
audioport --version
The convert command writes to the output path with its extension replaced by the target format when they differ (converting song-out.ogg to mp3 writes song-out.mp3). Supported formats: mp3, wav, ogg, flac, aac, m4a.
Each command prints its result as JSON. Exit codes: 0 on success, 1 when processing fails (including a missing transcription engine), 2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/audioport mcp
MCP client configuration:
{
"mcpServers": { "audioport": { "command": "npx", "args": ["-y", "@reneturcios/audioport", "mcp"], "env": { "AUDIOPORT_TRANSCRIBER_COMMAND": "whisper-cli --model base" } } } }
| Tool | Input | What it returns |
|---|---|---|
get_audio_metadata | input (required) | Format, duration in seconds, bit rate, sample rate, and channels; fields ffprobe did not provide are null. |
convert_audio | input, output, format (required), bitrate (optional) | The effective output path (extension follows the format), format, and bit rate. |
trim_audio | input, output, start (required), duration (optional) | The output path, start second, and duration. |
normalize_audio | input, output (required) | The input and output paths, after a loudnorm pass. |
transcribe_audio | input (required), language (optional) | The transcript from the configured engine, or an error naming AUDIOPORT_TRANSCRIBER_COMMAND when none is configured. |
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, fake executors only npm run dev # run the CLI from source via tsx
MIT — see LICENSE.