Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Code graph context engine with 24 MCP tools. 170+ languages via tree-sitter.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"tempograph": {
"command": "uvx",
"args": [
"tempograph"
]
}
}
}在终端中运行这条命令
claude mcp add tempograph -- uvx tempograph粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"tempograph": {
"command": "uvx",
"args": [
"tempograph"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"tempograph": {
"type": "stdio",
"command": "uvx",
"args": [
"tempograph"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 Elmoaid 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.7.2)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, zanadir
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Find what a repository's CI is missing, and which security checks cannot fail the build.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
This is the frozen April-2026 Python line (PyPI
tempograph 0.7.4). The live engine is the all-Rusttempograph_rsinElmoaid/outpm(ruling D-1, 2026-08). The benchmark headline below (+18.6%, p=0.049) was re-analysed as p=0.055, not significant (ruling D-7); it is kept as the published record, not as a current claim. Banner added 2026-09-02.
Your AI agent finds the right files. Every time.
TempoGraph builds a dependency graph of your codebase and gives your AI coding agent exactly the files it needs before making changes. One tool call. No guessing.
AI coding agents guess which files to look at. They search by filename, grep for keywords, and hope for the best. In large codebases, they miss critical dependencies, break things downstream, and waste tokens reading irrelevant code.
pip install tempograph
Add to your MCP config (Claude Code, Cursor, Windsurf, or any MCP client):
{
"mcpServers": { "tempograph": { "command": "tempograph-server", "args": [] } } }
Your agent calls prepare_context with a task description. TempoGraph returns the exact files that matter — based on real dependency analysis, not text matching.
Tested on real PRs from django, flask, httpx, fastapi, requests, and pydantic. Task: predict which files need to change.
| Model | Without TempoGraph | With TempoGraph | Improvement |
|---|---|---|---|
| GPT-4o | 21.7% F1 | 27.5% F1 | +27% |
| GPT-4o-mini | 19.2% F1 | 24.5% F1 | +28% |
| qwen2.5-coder:32b | — | — | +18.6% (p=0.049) |
Consistent improvement across every model. 2-3x more tasks helped than hurt. No other code context tool publishes retrieval benchmarks with statistical significance.
your repo ──→ tree-sitter parse ──→ symbols + edges ──→ SQLite graph
│ AI agent calls prepare_context ─────────┘ │ ◄── KEY FILES + callers + callees + risk signals
Beyond prepare_context, TempoGraph exposes 24 MCP tools for deeper analysis when your agent needs it:
| Tool | When to use it |
|---|---|
blast_radius | "What breaks if I change this file?" |
focus | "Show me everything related to auth" |
hotspots | "Which files are riskiest to change?" |
dead_code | "What can I safely delete?" |
diff_context | "What's the impact of my current changes?" |
overview | "Orient me in this new codebase" |
All 24 tools
| Tool | What it does |
|---|---|
prepare_context | One-shot context for a task — the primary tool |
overview | Repository orientation: size, languages, entry points |
focus | Connected subgraph around a symbol — callers, callees |
blast_radius | What breaks if you change this file or symbol |
diff_context | Impact analysis of changed files |
hotspots | Ranked risk list — complexity x coupling x size |
dead_code | Unreferenced symbols — cleanup candidates |
lookup | "Where is X?", "What calls X?" |
dependencies | Circular imports, dependency layers |
architecture | Module-level dependency view |
symbols | Full symbol inventory |
file_map | File tree with top symbols per file |
search_semantic | Hybrid keyword + vector + structural search |
cochange_context | Files that historically change together |
suggest_next | Predicts the next useful tool call |
run_kit | Composable multi-tool workflows |
stats | Token budget estimates |
get_patterns | Codebase conventions and idioms |
report_feedback | Log whether output was useful |
learn_recommendation | Suggestions from feedback history |
index_repo | Build or rebuild the graph |
watch_repo / unwatch_repo | Live incremental updates |
embed_repo | Generate vector embeddings |
# Orient in a new repo
tempograph ./my-project --mode overview
tempograph ./my-project --mode focus --query "authentication"
tempograph ./my-project --mode blast --file src/lib/db.ts
tempograph ./my-project --mode dead
from tempograph import build_graph
graph = build_graph("./my-project") results = graph.search_symbols("handleLogin") importers = graph.importers_of("src/lib/db.ts") dead = graph.find_dead_code()
Python, TypeScript, JavaScript, Rust, Go, Java, C#, and Ruby get deep extraction (custom tree-sitter handlers). 170+ additional languages are supported via generic handler. pip install tempograph[full] for everything.
If TempoGraph saves you time, consider sponsoring the project. Sponsors get early access to new features.
TempoGraph is AGPL-3.0 — free to use, modify, and distribute. If you use TempoGraph in a network service (SaaS, hosted IDE, AI coding platform), AGPL requires you to open-source your service code. If that doesn't work for you, commercial licenses are available.
Contact eali@needspec.com for commercial licensing terms.
AGPL-3.0 — free to use. Network service use requires source disclosure, or a commercial license.