Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
作者提供的说明(英文原文)
Inspect local audio files — playback, metadata, loudness, spectrogram.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"audio-file-app": {
"command": "npx",
"args": [
"-y",
"@counterpoint-studio/audio-file-mcp-app"
]
}
}
}在终端中运行这条命令
claude mcp add audio-file-app -- npx -y @counterpoint-studio/audio-file-mcp-app粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"audio-file-app": {
"command": "npx",
"args": [
"-y",
"@counterpoint-studio/audio-file-mcp-app"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"audio-file-app": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@counterpoint-studio/audio-file-mcp-app"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 counterpoint-studio 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.1.1)于30天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Figma Context MCP, Claude Real Video, Figma MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
The Figma MCP server brings Figma design context directly into your AI workflow.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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Ü