Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
What changed in a Python library, in which release, and what replaces it. Answered locally.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
DEPTIME_OFFLINE, DEPTIME_HOMENecesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"deptime": {
"command": "uvx",
"args": [
"deptime",
"mcp"
],
"env": {
"DEPTIME_OFFLINE": "your-value",
"DEPTIME_HOME": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add deptime --env DEPTIME_OFFLINE=your-value --env DEPTIME_HOME=your-value -- uvx deptime mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"deptime": {
"command": "uvx",
"args": [
"deptime",
"mcp"
],
"env": {
"DEPTIME_OFFLINE": "your-value",
"DEPTIME_HOME": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"deptime": {
"type": "stdio",
"command": "uvx",
"args": [
"deptime",
"mcp"
],
"env": {
"DEPTIME_OFFLINE": "your-value",
"DEPTIME_HOME": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
DEPTIME_OFFLINE envDEPTIME_HOME envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub cschmertz, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.7) llegó al registro hoy.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Zendesk
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
An API time machine for Python libraries, built for coding agents.
When an agent hits ImportError, AttributeError or "unexpected keyword argument" in a fast-moving library, one call to DepTime says what changed, in which release, and what to use instead. Answers are computed from static diffs of every indexed release, not from docs or model memory.
Free, open source (MIT), and local: your code and errors never leave your machine.
Every night, GitHub Actions reads each new release's public API with griffe, which parses the source without running it, diffs it against the previous release, and publishes the result as one file, index.sqlite.xz, on this repo's Releases. On your machine, deptime mcp checks that file's sha256 and schema before swapping it in, then answers every question locally in milliseconds. The full design is in docs/04-architecture.md, and the decisions are in docs/adr/.
TypeError: Client.__init__() got an unexpected keyword argument 'proxies'
{
"symbol": "httpx.Client.init(proxies)", "issue": "param_removed", "installed_version": "0.28.1", "last_version_with": "0.27.2", "first_version_without": "0.28.0", "deprecated_in": "0.26.0", "replacements": [ {"target": "proxy", "confidence": 0.8, "source": "deprecation_message"}, {"target": "mounts", "confidence": 0.79, "source": "deprecation_message"} ], "pin_to_restore": "httpx<=0.27.2", "confidence": "high" }
That's the real explain_error answer from the published index, trimmed. The full answer also quotes the deprecation message DepTime found in httpx's own source, and adds a one-sentence explanation for your agent to pass on.
Status: alpha. The prebuilt index is rebuilt twice a day. Known gaps are tracked in BACKLOG.md.
Each check's right answers were written down before DepTime first ran on it (bench/). Judge DepTime by the first run: the fixes since then were designed from its misses, so the later numbers are flattering.
| Check | Cases | First run | Now |
|---|---|---|---|
| Right package, name and breaking release for a traceback from a GitHub issue | 32 collected 2026-11-05 | 68.8% | 96.9% |
| The same, on a holdout fixed in advance from TimeMachine-bench | 29 | 72.4% | 93.1% |
Error kind and package read from the traceback: scripts, pytest, chained exceptions, ExceptionGroup, IPython, Python 3.10–3.14 | 736, holdout fixed in advance | 93.8% | 93.8% |
| Replacement hints at confidence ≥ 0.75 that are right | hints for 50 documented migrations | 11 of 11 | 42 of 45 |
| Documented migrations that get a right hint at ≥ 0.75 | 50 | 11 | 42 (32 without hand-checked hints from migration guides) |
| Names that exist at runtime but read as absent | 2,428 sampled at runtime from 10 dynamic packages | 5.1% | 1.2% |
Across all 196 real tracebacks in the benchmark, including the ones fixes were designed from, DepTime names the right package, name and release for 98.0%, and a right replacement is among its first three for 68.1%. CI re-scores the 196 and the holdout on every code change and every published index, and fails on a drop of more than 2 points.
Requires uv.
# Claude Code. Cursor, Codex, VS Code and Claude Desktop take the same
claude mcp add deptime -- uvx deptime mcp
On first launch DepTime downloads its prebuilt index (one file from this repo's GitHub Releases) in the background, then checks for a newer one at most once a day. Set DEPTIME_OFFLINE=1 to never touch the network.
Claude Code users can also install the plugin in integrations/claude-code with /plugin marketplace add cschmertz/deptime, then /plugin install deptime@deptime. It adds a skill and a local hook that suggests DepTime when a Python version-change error appears in a command's output.
First launch timing out? uvx installs DepTime the first time a client starts it. On macOS with an x86_64 uv (an Intel Mac, or Intel Homebrew on Apple silicon), one dependency, cryptography, has no prebuilt wheel and is compiled, which can take longer than a client waits for a server to start. Run uvx deptime --help once beforehand.
Checked 2026-11-05 with deptime 0.1.4 (details):
| Client | Result |
|---|---|
| Claude Code 2.1.318 | ✅ |
| Codex CLI 0.166.0 | ✅ |
MCP Python SDK clients 1.0–1.30 and TypeScript SDK clients 1.0–1.32 (protocols 2024-11-05 to 2025-11-25), over stdio and against deptime serve | ✅ |
| Cursor, VS Code, Claude Desktop | not checked yet; they take the same uvx deptime mcp command |
| Tool | Use it when | |
|---|---|---|
explain_error(traceback, installed_versions?, pip_freeze?) | An import or call into a library just failed | |
symbol_history(package, path) | Before trusting an API you remember | |
check_symbols(package, version, symbols[{path, kwargs}]) | Pre-flight check of the symbols and kwargs you're about to use | |
| `diff_versions(package, from_version \ | date, to_version?, used_symbols?)` | Upgrading, or "what changed since my training cutoff?" |
coverage() | What's indexed (53 fast-moving packages: AI/agent stack + libraries with known breaking changes) |
Every answer carries evidence and a confidence level. If a package isn't covered, DepTime says so instead of guessing. The contracts are in docs/03-product-spec.md.
uvx deptime explain --installed httpx==0.28.1 < traceback.txt
uvx deptime history httpx Client.init uvx deptime check httpx 0.28.1 'httpx.Client:proxies,proxy' uvx deptime diff httpx 0.27.2 0.28.1 uvx deptime diff pydantic 2024-06-01 # everything since a date uvx deptime index status | pull
Local mode covers coding agents. For web clients that only accept a URL, run deptime serve (MCP at /mcp, JSON at /v1/*) on any container host. The repo includes a Dockerfile and fly.toml, and the server applies anonymous rate limits. See docs/05-self-hosting.md.
The most useful contributions are wrong-answer reports, which become benchmark cases. See CONTRIBUTING.md. Development setup:
uv sync && uv run pytest
uv run deptime ingest httpx --versions 0.27.2 0.28.1
Product spec · Architecture · Self-hosting · Risks & spikes · Privacy & security