timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Local impact and table, column and Airflow lineage for SQL, dbt, Python and TypeScript repos.
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 16/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Brownfield Cartographer。按照 https://mcp.popnx.com/i/sanoy24-brownfield-cartographer.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Brownfield Cartographer,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "brownfield-cartographer": { "command": "uvx", "args": [ "brownfield-cartographer", "--repo" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Brownfield Cartographer 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"brownfield-cartographer": {
"command": "uvx",
"args": [
"brownfield-cartographer",
"--repo"
]
}
}
}用 Brownfield Cartographer 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Brownfield Cartographer,或回答中出现 Brownfield Cartographer 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Brownfield Cartographer
Brownfield Cartographer 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Brownfield Cartographer 的应用
B · 数据库与数据集 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Brownfield Cartographer,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user brownfield-cartographer -- uvx brownfield-cartographer --repo 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Brownfield Cartographer 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user brownfield-cartographer -- uvx brownfield-cartographer --repo应能看到 Brownfield Cartographer 在列表中并显示已连接
用 Brownfield Cartographer 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Brownfield Cartographer,或回答中出现 Brownfield Cartographer 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 没有一键按钮,需要粘贴设置并自行填写
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Brownfield Cartographer,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "brownfield-cartographer": { "command": "uvx", "args": [ "brownfield-cartographer", "--repo" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Brownfield Cartographer 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
~/.cursor/mcp.json
粘贴这些设置,填写空着的值并保存
{
"mcpServers": {
"brownfield-cartographer": {
"command": "uvx",
"args": [
"brownfield-cartographer",
"--repo"
]
}
}
}用 Brownfield Cartographer 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Brownfield Cartographer,或回答中出现 Brownfield Cartographer 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 没有一键按钮,需要粘贴设置并自行填写
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Brownfield Cartographer,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "brownfield-cartographer": { "type": "stdio", "command": "uvx", "args": [ "brownfield-cartographer", "--repo" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Brownfield Cartographer 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
MCP: Open User Configuration
粘贴这些设置,填写空着的值并保存
{
"servers": {
"brownfield-cartographer": {
"type": "stdio",
"command": "uvx",
"args": [
"brownfield-cartographer",
"--repo"
]
}
}
}用 Brownfield Cartographer 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Brownfield Cartographer,或回答中出现 Brownfield Cartographer 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user brownfield-cartographer -- uvx brownfield-cartographer --repoClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"brownfield-cartographer": {
"command": "uvx",
"args": [
"brownfield-cartographer",
"--repo"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"brownfield-cartographer": {
"command": "uvx",
"args": [
"brownfield-cartographer",
"--repo"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"brownfield-cartographer": {
"type": "stdio",
"command": "uvx",
"args": [
"brownfield-cartographer",
"--repo"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Sanoy24 验证,该账户拥有此仓库
代码最后更新于15天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 brownfield-cartographer@0.10.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/sanoy24-brownfield-cartographer)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于15天前,最新版本(0.10.0)于15天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:QueryWeaver, Supabase, Neon, DBCode, Keboola MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
Connect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...
| 本项 Brownfield Cartographer | QueryWeaver | Supabase | Neon | DBCode | Keboola MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 需要安装在电脑上 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 需要安装在电脑上 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 是 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 3/3 | 5/5 | 5/5 | 2/3 | 5/5 |
| 许可证 | Apache-2.0 | AGPL-3.0 | Apache-2.0 | MIT | NOASSERTION | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
What breaks if I change this? Cartographer finds the dependencies your language server can't see: a table written by a Python job, transformed in SQL, consumed by a dbt model. It maps them statically and locally, with file and line evidence, for you and your coding agent.
cartographer analyze .
cartographer impact models/staging/stg_orders.sql # what is downstream of this file? cartographer lineage customers --direction upstream # where does this table come from? cartographer lineage customers::first_order # which source columns feed this column?
Language servers and grep answer questions about code symbols. Cartographer answers questions that cross language boundaries through names in strings and configuration, starting with data lineage across Python, SQL and dbt. Every result carries source evidence and coverage, and unsupported cases are reported rather than guessed. It runs offline, needs no API key, and never executes repository code.
One query engine serves the CLI, a Python API, and a read-only MCP server for Claude Code, Codex and Cursor. The support table below lists current capabilities and known gaps.
With uv installed, run it on dbt's public example project. Nothing is installed permanently, and analysis took 3 seconds here:
git clone --depth 1 https://github.com/dbt-labs/jaffle_shop && cd jaffle_shop
uvx --from brownfield-cartographer cartographer analyze . uvx --from brownfield-cartographer cartographer impact models/staging/stg_payments.sql
analyze_impact | complete | snapshot eefa28cd4e13
┌───────────────┬──────────────┬──────────────────────────────────────┐ │ Symbol / node │ Relationship │ Evidence │ ├───────────────┼──────────────┼──────────────────────────────────────┤ │ stg_payments │ PRODUCES │ models/staging/stg_payments.sql:1-26 │ │ orders │ PRODUCES │ models/orders.sql:1-57 │ │ customers │ PRODUCES │ models/customers.sql:1-70 │ └───────────────┴──────────────┴──────────────────────────────────────┘
Column lineage follows renames through each model:
uvx --from brownfield-cartographer cartographer lineage customers::number_of_orders
trace_data_lineage | complete | snapshot eefa28cd4e13
┌──────────────────────┬──────────────┬────────────────────────────────────┐ │ Symbol / node │ Relationship │ Evidence │ ├──────────────────────┼──────────────┼────────────────────────────────────┤ │ stg_orders::order_id │ DERIVES │ models/customers.sql:1-70 │ │ raw_orders::id │ DERIVES │ models/staging/stg_orders.sql:1-24 │ └──────────────────────┴──────────────┴────────────────────────────────────┘
In Claude Code, the plugin lets you ask the same questions in plain language.
Requires Python 3.12+ and Git. Install the command-line tools from PyPI with uv or pipx:
uv tool install brownfield-cartographer
cartographer --version
cartographer analyze /path/to/repository
cartographer analyze /path/to/repository --full -o ./results
cartographer analyze /path/to/repository --dialect bigquery
cartographer analyze /path/to/dbt-project --dbt-manifest target/manifest.json
dbt docs generate for more column lineage.cartographer analyze /path/to/dbt-project --dbt-catalog target/catalog.json
To run from a source checkout instead, clone the repository, run uv sync --frozen, and prefix commands with uv run, as in the examples below.
An explicit GitHub URL input still downloads a checkout:
cartographer analyze https://github.com/owner/repository
Local analysis never uploads source and never calls a model.
For a local checkout, artifacts default to /.cartography/ /. With an explicit --output, local repositories use /.cartography/ -- / so same-named checkouts do not overwrite one another. The hash identifies the resolved checkout path; moving a checkout creates a separate index. The JSON analysis result includes artifact_directory, which can be passed to query commands as --index-dir. Existing custom-output indexes are left untouched; reanalyzing writes to the new directory. GitHub URL inputs use the current directory by default and an owner--repository folder name.
| Artifact | Purpose |
|---|---|
index.json | Complete versioned graph, source locations, metadata, coverage |
module_graph.json | Structural graph view, including functions |
lineage_graph.json | Dataset/transformation graph view |
analysis_summary.json | Complete/partial status, diagnostics and stage results |
CODEBASE.md | Static repository context |
onboarding_brief.md | Key modules, data entry/exit points and change hotspots |
cartography_trace.jsonl | Retained run history with run IDs |
state.json | Last successful snapshot's content fingerprint |
Explore interactively with cartographer query /path/to/repository. It accepts find, impact, deps, dependents, lineage, lineage-down, context, overview, help and quit, using the same engine as the commands below.
Or use individual commands with human-readable or JSON output:
uv run --no-sync cartographer overview /path/to/repository --json
uv run --no-sync cartographer find run --repo /path/to/repository --json uv run --no-sync cartographer impact producer.py --repo /path/to/repository uv run --no-sync cartographer lineage output --repo /path/to/repository --direction upstream --json
Use --index-dir for a custom output location. Python callers use brownfield_cartographer.query_api.QueryEngine.open(Path(repo)) and the same query methods. Responses carry snapshot identity, coverage, capped-output markers, and available source evidence. Ambiguous targets are rejected.
cartographer diff reports what a branch changes and what that can affect, for a PR comment or a quick check before pushing:
cartographer diff --base main # Markdown
cartographer diff --base main --json # for scripts
Changed lines since the merge base with --base (committed, uncommitted and untracked) are mapped to functions, modules, SQL statements, dbt models, schema YAML and Airflow tasks, and their downstream dependents are listed with evidence. The merge base is analyzed too, so removed code counts: deleting a module, function or model reports the importers, callers and models that still use it.
To comment on every pull request, add a workflow:
on: pull_request
permissions: contents: read pull-requests: write jobs: impact: runs-on: ubuntu-latest steps:
The action keeps one comment up to date and also writes the report to the job summary, which still works for pull requests from forks.
Claude Code plugin (needs uv; nothing else to install or configure):
/plugin marketplace add Sanoy24/the-brownfield-cartographer
/plugin install brownfield-cartographer@brownfield-cartographer
The plugin starts the MCP server for the current project and adds a data-impact skill. Ask questions such as "what breaks if I change stg_orders?". If the project has not been analyzed yet, the tools say so and the assistant runs cartographer analyze (offline; repository code is never executed) before answering.
Any MCP host:
cartographer analyze /absolute/path/to/repository
cartographer-mcp --repo /absolute/path/to/repository
The stdio server exposes get_architecture, find_symbol, trace_dependencies, analyze_impact, trace_data_lineage, and get_code_context. It reads a previously analyzed index inside a fixed repository scope and never calls a model. See MCP setup for Claude Code, Codex, and Cursor.
find is lexical matching. impact reports potential dependents, not a guarantee that every consumer will break. Read the persisted coverage and diagnostics before relying on results from an incomplete scan.
Analysis returns exit code 0 for complete/unchanged snapshots, 2 for partial coverage, and 1 for an input or fatal run error. A partial run does not advance the successful checkpoint. Changed working trees currently use full rebuilds; unchanged successful snapshots can reuse the complete index.
| Input | Current support |
|---|---|
| Python | Functions/classes, supported absolute/relative imports, and calls between repository functions (same-module names, imported names and modules, self/cls methods; calls on other objects and dynamic calls are not guessed); conservative literal I/O associations (pandas, Spark readers and writers). SQL passed to execute/executemany/executescript, .sql() and read_sql is parsed from literals and string constants (same module or imported from another repository module), including text() and DB-API placeholders. f-strings that interpolate only values (comparisons, IN, LIMIT, quoted literals) are resolved; SQL with interpolated table names or projections, concatenation or .format is reported as dynamic, not guessed |
| SQL | SELECT/UNION, CTAS, INSERT, UPDATE, DELETE and MERGE; statement spans and table dependencies. DDL and transaction statements without table lineage are skipped; other statements, such as COPY, are reported individually without dropping the rest of the file. Each file is parsed with the best-fitting dialect (DuckDB, BigQuery, Snowflake, Postgres, MySQL, Spark, T-SQL, Trino), recorded as sql: in evidence; --dialect pins one |
| dbt | Explicit manifest v12 ingestion for models, seeds, snapshots and sources; basic SQL/YAML fallback without a manifest. Projects are found anywhere in the repository, including several per repository |
| Columns | Column-level lineage for CREATE ... AS, INSERT ... SELECT (including column lists) in SQL files, SQL embedded in Python, Airflow inline SQL, dbt models from a compiled manifest (--dbt-manifest, after dbt compile), and dbt source models whose only Jinja is ref/source/config/comments and literal set lists with for loops over them, and calls to the project's own macros with literal arguments. Each edge is copy (the value passes through unchanged) or derived (the column influences the value, including through CASE conditions, window PARTITION BY/ORDER BY keys and aggregates). SELECT * and unqualified columns in joins are resolved against the columns each table is known to have: from CREATE TABLE definitions and fully resolved CREATE ... AS statements and dbt models in the repository, and optionally a dbt `