io.umtri/umtri
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Umtri
Publisher-provided description
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Summary by lookupd
Lets an agent record and query a project's structure, dependencies, API flows, bugs, and wiki pages across time.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http umtri https://mcp.umtri.io
Claude Code, npm package (stdio)
claude mcp add umtri -- npx -y umtri-mcp
Codex, remote (streamable-http)
codex mcp add umtri --url https://mcp.umtri.io
Codex, npm package (stdio)
codex mcp add umtri -- npx -y umtri-mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"umtri": {
"url": "https://mcp.umtri.io"
}
}
}Cursor, npm package (stdio) → .cursor/mcp.json
{
"mcpServers": {
"umtri": {
"command": "npx",
"args": [
"-y",
"umtri-mcp"
]
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (showing 30 of 32)
Publisher-provided text
list_projectsReturns all grounds the authenticated user can access, with latest activity timestamp. Use this first to discover slugs for other tools. By default returns a suget_graphReturns the tree(nodes), edges, apis, seasons, and bugs for one ground. The tree is the project's information-structure (IA) diagram — each node is a structuralget_impactWalks the connection graph (edges + apis) from a start node — or a bug's target — to find which other nodes a problem would reach. This is the tool for "if thislist_bugsScans the bugs (issues eroding the ground) of one ground. Looking at ONE bug you already know the number/id of? Call get_bug instead — no need to list. Bugs defget_bugReturns a single bug by reference — the cheap path when you already know which bug you mean. `ref` accepts either the human-facing number shown in the UI (seq —list_seasonsReturns the seasons (time epochs) of a ground in chronological order. A season is the human's declaration that a chapter closed. You may create one with create_export_groundReturns everything in a ground as one JSON document — project, seasons, nodes (removed ones included, with removedAt), edges, apis, bugs and wiki pages with fullist_eventsReturns the append-only change history (most recent first) of a ground: node/edge/api/bug create, update (with a field-level diff {from,to}), delete, and plan_ccreate_bugCreates a new bug (issue eroding the target). target.kind = "node" or "api" requires target.id of an existing node/api in the ground. target.kind = "ground" attcreate_projectCreates a new ground. Slug must match /^[a-z0-9][a-z0-9-]{0,49}$/ and be unique. By default it goes into the authenticated user's personal space; pass org (a tecreate_seasonCreates a new season and makes it the "now" season. This is not an additive act: the ground's current now-season is sealed as past and every node in it is markecreate_nodeCreates a node. Follows the plant vocabulary protocol — see umtri://rules/vocabulary. type ∈ trunk · limb · twig · leaf · vein. Role is derived (structure / objupdate_nodePartial update of a node. Patchable fields: label, type, parent, season, description, tags, metadata, sproutedAt. metadata is merged key by key: only the keys ydelete_nodeSets removed_at on the node. By default this tool rejects deletion if the node has any active descendant, so a subtree is never lost silently. To soft-delete thcommit_planPromotes a plan node (metadata.plan=true) to the real tree by clearing the plan flag. VERIFICATION GATE: the node must already carry metadata.implements (the sorecord_commitConfiguration record (CI/CD). Given a commit SHA and the files it changed, finds nodes whose metadata.implements include any of those files and appends the commcreate_edgeCreates a directed edge (source → target) for a STRUCTURAL relation: type "dependency" (A is built on / needs B) or "data_flow" (data moves A → B outside a requdelete_edgeRemoves an edge from the ground. Use to retire dependencies/flows that no longer reflect reality.create_apiRecords an API flow (start → end) for a RUNTIME request / call / data flow: a screen calling an endpoint, an endpoint hitting a table, an external integration (update_apiPartial update of an API. Patchable fields: label, description, metadata, start, end.delete_apiSets removed_at on the API. History is preserved — the API can still be seen in past season views via the time slider.update_bugPartial update of a bug. Most common use: status transition. Send only the fields that actually change. A status transition is patch:{status} alone — do not re-delete_bugPermanently removes a bug record. Bugs do not have history — once deleted, the record is gone. For "I resolved this", use update_bug with status="resolved" instsend_feedbackFiles a suggestion or a defect report about **Umtri the product** — this MCP server, its tools, the app, the docs. This is NOT for issues in the user's own projlist_feedbackLists feedback filed about **Umtri the product** (see send_feedback) — not the bugs of any ground. Umtri operators only: every other account gets 403, so do notupdate_feedbackUpdates one feedback record about **Umtri the product** — typically closing it: status="done" once it shipped, or "wontfix" when it was declined. Put what was alist_wikiLists the ground's wiki — the prose the tree cannot hold: conventions, decisions and why they were made, glossary, onboarding. Reference entries describing howget_wikiReturns one wiki page. `ref` takes either the page slug (what a human says) or the internal id (wiki-<uuid>) — renaming a page changes its slug but never its idlist_wiki_revisionsReturns what this page said before, newest first — rev number, who wrote it, when, and the body length. Bodies are not included (a history of twenty full documewrite_wikiWrites one wiki page. Creates it if the page slug is new, updates it otherwise — you do not need to check first. **The wiki is the project's encyclopedia: one p
Details
- Version: 1.7.1
- Transports: streamable-http, stdio
- Uptime (7 days): 100%
- Median latency: 2588 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/bepuljang/umtri-mcp
- Website: https://docs.umtri.io
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.umtri/umtri)
- 62092 servers
- Last crawl: 2026-11-11T17:38:11.606Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp