B
bepuljang/umtri-mcp
MCP server for Umtri — give your AI coding agent a persistent map of your
更新 2026-11-06
在 GitHub 查看 ↗直链 · 无中转页
安装与配置
远端端点(Claude Desktop / Cursor / Windsurf 共用 mcpServers)
{
"mcpServers": {
"bepuljang-umtri-mcp": {
"url": "https://mcp.umtri.io"
}
}
}把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据,我们没有替你安装或托管它。 官方 Registry 记录:这个端点没有列出任何请求头。这不等于免密 —— 以项目文档为准。
VS Code(.vscode/mcp.json —— 键名是 servers,远程要 type: http)
{
"servers": {
"bepuljang-umtri-mcp": {
"type": "http",
"url": "https://mcp.umtri.io"
}
}
}VS Code 的配置文件和另外三家不同:顶层键是 <code>servers</code>,远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code(命令行)
claude mcp add --transport http bepuljang-umtri-mcp https://mcp.umtri.io
Claude Code 不收 JSON 文件,用这条命令直接加。
配置文件在:macOS
~/Library/Application Support/Claude/claude_desktop_config.json、Windows %APPDATA%\Claude\claude_desktop_config.json、Linux ~/.config/Claude/claude_desktop_config.json。配置项的键名以你的客户端为准:客户端与 CLI- ★ 数取值
- 0 ★ · bepuljang/umtri-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
bepuljang/umtri-mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# umtri-mcp
以下摘录自该仓库的 README(片段)
MCP server for Umtri — give your AI coding agent a persistent map of your
project's structure, dependencies, and bugs.
Your agent re-derives your codebase from scratch every session. Umtri stores the structure once and
hands it back through MCP: a tree of what the system is made of, the calls and dependencies between
its parts, and the bugs eroding it. Ask "what breaks if I change this?" and get an answer traced
through recorded connections rather than guessed from a grep.
## Quick start
The fastest path is the hosted endpoint at https://mcp.umtri.io — nothing to install. Generate a
token at app.umtri.io → Settings → API Tokens, then:
bash
claude mcp add --transport http umtri https://mcp.umtri.io \
--header "Authorization: Bearer umtri_pat_xxxxxxxxxxxxxxxx"
Any MCP client that takes a config object uses the same shape:
json
"mcpServers": {
"umtri": {
"type": "http",
"url": "https://mcp.umtri.io",
"headers": { "Authorization": "Bearer umtri_pat_xxxxxxxxxxxxxxxx" }
## Run it yourself (stdio)
Use this package when you want to pin a version or point at a self-hosted API:
bash
claude mcp add umtri \
-e UMTRI_API_TOKEN=umtri_pat_xxxxxxxxxxxxxxxx \
--transport stdio \
-- npx -y umtri-mcp
| Variable | Required | Default |
| UMTRI_API_TOKEN | yes | — |
| UMTRI_API_BASE | no | https://api.umtri.io |
The token is not validated at setup time, so a bad token connects but every call fails. If tools
appear and then error, re-check the token and its scope — read tokens cannot call any write tool.
## Tools
Read — get_graph, get_bug, get_impact, list_projects, list_bugs, list_seasons,
list_events, export_ground
Write — create_project, create_node, update_node, delete_node (a subtree only with
cascade: true), create_edge, delete_edge, create_api, update_api, delete_api,
create_bug, update_bug, delete_bug, create_season (acts only after the user confirms)
Plan loop — commit_plan, record_commit
Wiki — list_wiki, get_wiki, list_wiki_revisions, write_wiki, edit_wiki, delete_wiki. The ground's
encyclopedia: pages form a table of contents (parent, position) read from an overview down,
each has a kind, and every write comes back with warnings when a page strays from the skeleton.
Feedback — send_feedback files a suggestion or defect about Umtri itself.
get_graph returns a slice, not a dump: scope by subtree (rootId), by layer (maxType), by role,
or by season, and control description weight separately. A large tree stays cheap to read.
project's structure, dependencies, and bugs.
Your agent re-derives your codebase from scratch every session. Umtri stores the structure once and
hands it back through MCP: a tree of what the system is made of, the calls and dependencies between
its parts, and the bugs eroding it. Ask "what breaks if I change this?" and get an answer traced
through recorded connections rather than guessed from a grep.
## Quick start
The fastest path is the hosted endpoint at https://mcp.umtri.io — nothing to install. Generate a
token at app.umtri.io → Settings → API Tokens, then:
bash
claude mcp add --transport http umtri https://mcp.umtri.io \
--header "Authorization: Bearer umtri_pat_xxxxxxxxxxxxxxxx"
Any MCP client that takes a config object uses the same shape:
json
"mcpServers": {
"umtri": {
"type": "http",
"url": "https://mcp.umtri.io",
"headers": { "Authorization": "Bearer umtri_pat_xxxxxxxxxxxxxxxx" }
## Run it yourself (stdio)
Use this package when you want to pin a version or point at a self-hosted API:
bash
claude mcp add umtri \
-e UMTRI_API_TOKEN=umtri_pat_xxxxxxxxxxxxxxxx \
--transport stdio \
-- npx -y umtri-mcp
| Variable | Required | Default |
| UMTRI_API_TOKEN | yes | — |
| UMTRI_API_BASE | no | https://api.umtri.io |
The token is not validated at setup time, so a bad token connects but every call fails. If tools
appear and then error, re-check the token and its scope — read tokens cannot call any write tool.
## Tools
Read — get_graph, get_bug, get_impact, list_projects, list_bugs, list_seasons,
list_events, export_ground
Write — create_project, create_node, update_node, delete_node (a subtree only with
cascade: true), create_edge, delete_edge, create_api, update_api, delete_api,
create_bug, update_bug, delete_bug, create_season (acts only after the user confirms)
Plan loop — commit_plan, record_commit
Wiki — list_wiki, get_wiki, list_wiki_revisions, write_wiki, edit_wiki, delete_wiki. The ground's
encyclopedia: pages form a table of contents (parent, position) read from an overview down,
each has a kind, and every write comes back with warnings when a page strays from the skeleton.
Feedback — send_feedback files a suggestion or defect about Umtri itself.
get_graph returns a slice, not a dump: scope by subtree (rootId), by layer (maxType), by role,
or by season, and control description weight separately. A large tree stays cheap to read.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/bepuljang-umtri-mcp/)
- 来源
- awesome · https://github.com/bepuljang/umtri-mcp
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。