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)
Inspect local audio files — playback, metadata, loudness, spectrogram.
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": {
"audio-file-app": {
"command": "npx",
"args": [
"-y",
"@counterpoint-studio/audio-file-mcp-app"
]
}
}
}Run this in your terminal
claude mcp add audio-file-app -- npx -y @counterpoint-studio/audio-file-mcp-appPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"audio-file-app": {
"command": "npx",
"args": [
"-y",
"@counterpoint-studio/audio-file-mcp-app"
]
}
}
}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": {
"audio-file-app": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@counterpoint-studio/audio-file-mcp-app"
]
}
}
}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 8, 2026
The registry name was verified with the GitHub account counterpoint-studio, 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 (1.1.1) reached the registry 30 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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:↓ Downloads per weeki★ 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.
An MCP App for playing and inspecting local audio files in an MCP host.
Renders an in-conversation UI with playback, metadata, loudness, a spectrogram, and an optional annotation-lane timeline.
File metadata, loudness statistics, the current playhead position, any selected region, and the annotation lanes active at the playhead are also exposed back to the model, so follow-up tasks can refer to what the user is actually hearing and looking at.
The server runs locally over stdio. Every install path below configures the same command: npx -y @counterpoint-studio/audio-file-mcp-app.
Easiest: grab the latest .mcpb from the Releases page and double-click it. Claude Desktop has Node bundled, so no extra runtime is needed.
Or add the server by hand to claude_desktop_config.json:
{
"mcpServers": { "audio-file": { "command": "npx", "args": ["-y", "@counterpoint-studio/audio-file-mcp-app"] } } }
audiofile-mcp-appnpx-y and @counterpoint-studio/audio-file-mcp-appOr add to .vscode/mcp.json (workspace) or your user mcp.json:
{
"servers": { "audio-file": { "type": "stdio", "command": "npx", "args": ["-y", "@counterpoint-studio/audio-file-mcp-app"] } } }
Paste this deep link into your browser (Goose Desktop must be installed; the custom URI scheme can't be a real link in a GitHub README):
goose://extension?id=audio-file&name=Audio%20File%20MCP%20App&cmd=npx&arg=-y&arg=%40counterpoint-studio%2Faudio-file-mcp-app
Or run goose configure → Add Extension → Command-line Extension and enter npx -y @counterpoint-studio/audio-file-mcp-app.
npx @modelcontextprotocol/inspector npx -y @counterpoint-studio/audio-file-mcp-app
Ask the host to show you a local audio file by its absolute path. For example:
"Show me
/Users/me/Music/track.wav"
The host calls the display_audio_file tool, which renders the in-app UI with waveform, spectrogram, loudness metrics, and playback transport.
display_audio_file accepts an optional annotations object describing lanes to draw on the timeline (or an annotationsPath pointing at a JSON file with the same { "lanes": [...] } shape — handy for large payloads):
{
"annotations": { "lanes": [ { "label": "Delay tails", "color": "#e6007e", "spans": [{ "start": 8, "end": 24 }], "envelope": [ { "time": 8, "value": 0 }, { "time": 24, "value": 1 } ] } ] } }
Times are in seconds on the audio's own timeline. label, color, and envelope are optional; a lane with an envelope fades its span opacity along the envelope curve, and uncoloured lanes use a light-accent fill. Overlapping spans in a lane are truncated at the next span's start so rows never overlap. The model can author annotations to point out sections, mark events, or visualise an analysis it just ran.
display_audio_file opens any file path it is given, by design, but only accepts files recognised as audio.audiofile-range://…). It returns bytes only of files recognised as audio; anything else, including a path that doesn't exist, gets the same "Not a recognised audio file" error.annotationsPath reads a JSON file you name, and only uses it if it matches the annotation format.annotationsPath) is valid JSON in the annotation format. They never include the file's contents.To report a vulnerability, see SECURITY.md.
Tested and known to work in:
pnpm install
pnpm run build:dsp # emsdk required; see WASM-BUILD.md pnpm run serve # runs the server with tsx, no compile step pnpm test
pnpm run build:dist produces the publishable layout under dist/ (dist/mcp-app.html + dist/server/).
pnpm version <bump> # bumps every version string (package.json, server.json,
git push && git push --tags source /path/to/emsdk_env.sh # prepublishOnly rebuilds the DSP code with Emscripten pnpm publish --access public # publishes to npm gh workflow run publish-registry.yml -f tag=v # MCP Registry, once npm shows the version pnpm run build:mcpb # produces dist/audio-file-mcp-app- .mcpb gh release create v dist/*.mcpb # attaches the bundle to a GitHub release
npm can hold a new version in validating for up to an hour before it appears. The registry checks the npm package, so run the registry workflow only after npm view @counterpoint-studio/audio-file-mcp-app version shows the new version.
The MCP Registry is published from GitHub Actions (.github/workflows/publish-registry.yml) because the interactive mcp-publisher login github only grants a personal namespace, not io.github.counterpoint-studio/*.
ISC © Counterpoint Studio OÜ