Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Universal CPU profiler designed for humans and AI agents
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"uniprof": {
"command": "npx",
"args": [
"-y",
"uniprof",
"mcp",
"run"
]
}
}
}在终端中运行这条命令
claude mcp add uniprof -- npx -y uniprof mcp run粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"uniprof": {
"command": "npx",
"args": [
"-y",
"uniprof",
"mcp",
"run"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"uniprof": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"uniprof",
"mcp",
"run"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 indragiek 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.3.4)于14个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, NexusWindows
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
uniprofuniprof simplifies CPU profiling for humans and AI agents. Profile any application without code changes or added dependencies.
# Profile and analyze any app in one step
npx uniprof python script.py
uniprof implements a common interface over multiple profilers that specialize in different platforms and runtimes. It automatically detects which profiler to use based on the command being executed, runs the profiler, transforms the varying output formats into a single format, and runs statistical analysis on the data to identify hotspots.
| Platform | Profiler | Container | Host | Min Version |
|---|---|---|---|---|
| Python | py-spy | ✅ | ✅ | Python 3.7+ |
| Node.js | 0x | ✅ | ✅ | Node 14+ |
| Ruby | rbspy | ✅ | ✅ | Ruby 2.5+ |
| PHP | Excimer | ✅ | ✅ | PHP 7.2+ |
| JVM | async-profiler | ✅ | ✅ | Java 8+ |
| .NET | dotnet-trace | ✅ | ✅ | .NET 5+ |
| BEAM | perf | ✅ | ✅* | OTP 24+ |
| Native (macOS) | Instruments | ❌ | ✅ | Xcode 14.3+ |
| Native (Linux) | perf | ✅ | ✅ | Linux 2.6.31+ |
\* Linux only for host mode
tl;dr: macOS or Linux with Docker installed
uniprof is designed to run on macOS and Linux but has primarily been developed & tested on macOS. If you find any bugs when running on Linux, please report them. Running on a Windows host is currenly not supported, but you can run on Linux installed on Windows via WSL2. Note that when using uniprof via WSL2, profiling native Windows executables is not supported, but you can still use the profilers for the higher level language runtimes like Python and Node.js.
Profiling tools are often non-trivial to set up correctly and can require elevated privileges. To simplify set up and provide better isolation for the profiled code, uniprof defaults to using Docker containers for each runtime that are pre-configured to run specific profiling tools. uniprof mounts your workspace in the container and executes the program with the profiler attached. uniprof also supports profiling outside the container if the host system has the profiling tools installed by running with the --mode host flag. The only case where containerized execution is not supported is when profiling a native Mach-O binary on macOS, since Apple Instruments cannot run inside a container.
npm install -g uniprof
# Install uniprof MCP server automatically
uniprof mcp install claudecode uniprof mcp install cursor uniprof mcp install vscode
Supported clients for auto-installation: amp, claudecode, codex, cursor, gemini, vscode, zed
If auto-installation is not supported for your client, add an MCP server using the stdio transport with the command npx -y uniprof mcp run.
For detailed MCP documentation see docs/mcp.md.
Profile and analyze in one step:
# Profile most languages and get immediate analysis
uniprof python app.py uniprof node server.js uniprof ruby script.rb uniprof java -jar myapp.jar uniprof dotnet MyApp.dll uniprof ./my-native-app
uniprof --visualize python app.py
Save profiles to analyze and visualize later:
# 1. Check environment (optional)
uniprof bootstrap
uniprof record -o profile.json -- python app.py uniprof record -o profile.json -- node server.js uniprof record -o profile.json -- ruby script.rb uniprof record -o profile.json -- php script.php uniprof record -o profile.json -- java -jar myapp.jar uniprof record -o profile.json -- ./gradlew run uniprof record -o profile.json -- ./mvnw spring-boot:run uniprof record -o profile.json -- dotnet MyApp.dll uniprof record -o profile.json -- elixir script.exs uniprof record -o profile.json -- mix run uniprof record -o profile.json -- ./my-native-app uniprof record -o profile.json -- /Applications/MyApp.app
uniprof analyze profile.json
uniprof visualize profile.json
For detailed command line options documentation see docs/cli.md.
Use the --mode option to control how profiling runs:
# Auto mode (default)
uniprof record -o profile.json -- python script.py
uniprof record --mode host -o profile.json -- python script.py
uniprof record --mode container -o profile.json -- ./my-linux-app
Native profiling requires debug information for meaningful results. Debug symbols enable the profiler to map memory addresses to function names, providing readable output instead of just hexadecimal addresses. Additionally, frame pointers improve call stack accuracy, especially for optimized code.
| Compiler | DWARF Debug Info | Frame Pointers | Notes |
|---|---|---|---|
| gcc | gcc -g -o myapp main.c | gcc -fno-omit-frame-pointer -o myapp main.c | Use -g3 for maximum debug info, -ggdb for GDB-specific extensions |
| clang | clang -g -o myapp main.cpp | clang -fno-omit-frame-pointer -o myapp main.cpp | Use -gfull on macOS for complete debug info |
| swift | swiftc -g main.swift | swiftc -Xcc -fno-omit-frame-pointer main.swift | Debug builds include symbols by default with swift build |
| cargo | cargo build (debug mode) cargo build --release + [profile.release] debug = true | RUSTFLAGS="-C force-frame-pointers=yes" cargo build | Debug builds include DWARF by default; for release builds, add debug = true to Cargo.toml | | go | go build -gcflags=all="-N -l" | Built-in, always enabled | Go includes debug info by default; -gcflags disables optimizations for better debugging | | zig | zig build-exe -O Debug main.zig | zig build-exe -fno-omit-frame-pointer main.zig | Use -O ReleaseSafe with debug info for optimized builds with symbols | | ghc | ghc -g -rtsopts main.hs | ghc -fno-omit-frame-pointer main.hs | Use -prof for profiling builds; -rtsopts enables runtime profiling options |
All uniprof source code in this repository is licensed under the MIT License. See LICENSE.
uniprof downloads and runs Docker images that bundle third-party software. The Dockerfiles used to build these images can be found in containers/. These images and their contents are not covered by the MIT license and are governed by their own licenses. uniprof does not grant rights to those components and does not relicense them.