Servidor MCP
Forge Engine
app.forgeengine/forge
Qué hace este MCP
Manages software design specifications, systems, milestones, tasks, code mappings, project decisions, UI screens, and implementation drift.
Capacidades
Herramientas
54
herramientas
add_task
Add a task to a milestone — DIRECT. assignee:"me" claims on creation.
Esquema de entrada
{'type': 'object', 'required': ['name'], 'properties': {'done': {'type': 'boolean'}, 'name': {'type': 'string', 'description': 'Task name'}, 'human': {'type': 'boolean', 'description': 'Human-only (GTM/validation/people work) — next_task & get_briefing skip it'}, 'effort': {'enum': ['S', 'M', 'L'], 'type': 'string'}, 'status': {'enum': ['in-progress', 'blocked'], 'type': 'string'}, 'assignee': {'type': 'string', 'description': '"me" claims it'}, 'milestone': {'type': 'string', 'description': 'If no id'}, 'project_id': {'type': 'string'}, 'milestone_id': {'type': 'string', 'description': 'Preferred'}}}
dedupe
Remove duplicate-named entries (keep first) — DIRECT, destructive.
Destructivo
Esquema de entrada
{'type': 'object', 'required': ['kind'], 'properties': {'kind': {'enum': ['milestones', 'elements'], 'type': 'string', 'description': 'What to dedupe'}, 'screen': {'type': 'string', 'description': 'For kind=elements'}, 'project_id': {'type': 'string'}}}
delete_entity
PROPOSE a delete → Inbox (owner adopts; nothing deleted now). id preferred or exact name; flow_edge may use from+to.
Destructivo
Esquema de entrada
{'type': 'object', 'required': ['kind'], 'properties': {'id': {'type': 'string', 'description': 'Entity/task/element/edge id'}, 'to': {'type': 'string', 'description': 'flow_edge: destination screen'}, 'from': {'type': 'string', 'description': 'flow_edge: source screen'}, 'kind': {'enum': ['system', 'context', 'screen', 'milestone', 'task', 'element', 'flow_edge'], 'type': 'string', 'description': 'What to delete'}, 'name': {'type': 'string', 'description': 'Exact name/title (if no id)'}, 'project_id': {'type': 'string'}}}
design_ui_from_systems
Recipe to design the UI from Systems (user request only): steps + batch id — confirm canvas aspect, then screens + PLACED elements + edges in one batch.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
get_balance
Read Balance Lab: stat tables, boards with EVALUATED values, scenarios.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'board': {'type': 'string', 'description': 'One board (omit = all)'}, 'project_id': {'type': 'string'}, 'include_rows': {'type': 'boolean', 'description': 'false = schema only'}}}
get_briefing
ONE-CALL orientation before you build: pass `files` you're about to edit (or a `task`) → the systems that own them, each with Goal + Acceptance + build status/files/last_commit/drift + coupled_systems (code neighbors an edit may break) + pending Inbox changes + recent decisions, plus open-rejection count, who's active, `recent_changes` (what happened since you were last here — a session handoff), and a task to claim. Replaces the get_project_meta→get_system→get_build_region dance.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'task': {'type': 'string', 'description': "A task id or name — briefs its milestone's systems instead"}, 'files': {'type': 'array', 'items': {'type': 'string'}, 'description': "Repo-relative paths you're about to touch — mapped to their systems"}, 'project_id': {'type': 'string'}}}
get_build_region
System→code map per built system: implementing files, status, drift flag, last_commit, and acceptance-evidence COUNTS. Mapped files gone from the repo? report_drift. Pass `system:"<name|id>"` for ONE system plus the full text of its acceptance criteria (omitted from the map — it is the bulk of the payload). Big projects come back paged: the body says 'page N of M', call again with `page: N+1`.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Which page of the map (default 1); the body tells you how many there are'}, 'system': {'type': 'string', 'description': 'One system by name or id — returns its acceptance-criteria detail too'}, 'project_id': {'type': 'string'}}}
get_design_document
The WHOLE design as one readable document — Vision (+ Project DNA) → every System spec → reference notes, compiled deterministically from the current design. Read this to understand a project end-to-end instead of walking list_systems → get_system N times. Returns markdown plus the project `version` it was compiled from. Long designs come back PAGED — the header says 'part N of M', call again with `page: N+1` for the rest. Pass `for_summary: true` to get the condensed projection instead (every system's Goal + Boundary, tables stripped, one page) — that is what you should summarize from.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Which part of the full document to return (default 1). The header tells you how many parts there are.'}, 'project_id': {'type': 'string'}, 'for_summary': {'type': 'boolean', 'description': 'Return the condensed summarization source (all system goals + boundaries, no tables) instead of the full document'}}}
get_help
Forge how-to on demand (no project needed): propose→adopt, what a System is, Balance Lab formats, sign-in. Call when unsure.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {}}
get_history
DESIGN MEMORY: recorded decisions/logs/rejections with who/when. Read BEFORE changing a system's direction; empty = no recorded WHY — don't invent one.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'limit': {'type': 'number', 'description': 'Default 30, max 100'}, 'query': {'type': 'string', 'description': 'Keyword filter'}, 'system': {'type': 'string', 'description': 'System id or exact name'}, 'project_id': {'type': 'string'}}}
get_impact
BLAST RADIUS of a system (deterministic): upstream context, siblings, dependent screens/milestones, files, code-coupled systems, pending Inbox, recent activity. Run BEFORE changing it.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'project_id': {'type': 'string'}}}
get_inbox
PENDING Inbox (the owner's triage queue). Check BEFORE proposing — avoid duplicates. Read-only.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
get_milestone
ONE milestone: goal, weeks, difficulty, systems, every task (id/name/done/status/effort).
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'project_id': {'type': 'string'}}}
get_project_context
FULL design dump — LARGE, last resort; prefer get_project_meta + list_*/get_*/search.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
get_project_meta
START HERE. Tiny overview: counts, members, task claims + working_now (avoid collisions), forge_workflow_version.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
get_rejections
Owner's DECLINED list — check at session start; follow each entry's guidance, then resolve_rejection(title).
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
get_screen
ONE screen's layout: canvas `resolution` (use THESE px), elements x/y/w/h, links, popups. Read before editing a screen. has_reference_image:true → get_screen_image shows you the actual image.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'project_id': {'type': 'string'}}}
get_screen_image
A screen's reference image (HUD background) as an actual IMAGE you can see — reads the stored file inline (signed-URL fallback past 4MB).
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'project_id': {'type': 'string'}}}
get_stale
What has drifted between the Idea lane and the System Specs — the design's own out-of-sync list, computed deterministically (no AI, no tokens). Three kinds: Idea notes edited since the systems were generated from them (with the systems each one touches), Idea notes whose prose the systems have moved past, and specs whose stamped source fingerprint no longer matches. Read this before assuming the design is coherent; fix the first kind with resync_from_idea.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
get_system
ONE system's full spec (Goal/Boundary/Acceptance, markdown, sources, status) + pending Inbox changes touching it.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'project_id': {'type': 'string'}}}
get_workflow
Run FIRST in a new repo (no project): first-connect routine + the working-agreement block to ADD to AGENTS.md/CLAUDE.md now (tell the user in one line; remove if they object).
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {}}
import_from_code
One-command codebase import: recipe + batch id — propose one Context overview + one System per real module; the owner adopts all at once.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
list_activity
Change history {who, change, entity, kind, when}, newest first; filter kind/who/query.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'who': {'type': 'string', 'description': 'Author email substring (optional)'}, 'kind': {'type': 'string', 'description': 'system | context | milestone | screen (optional)'}, 'limit': {'type': 'number', 'description': 'Default 30, max 200'}, 'query': {'type': 'string', 'description': 'Keyword filter (optional)'}, 'project_id': {'type': 'string'}}}
list_milestones
All milestones, compact: id, name, weeks, order, done/total.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
list_projects
Projects your key reaches (id, name, role); pass an id as project_id to switch.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {}}
list_screens
All screens, compact: id, name, purpose, status.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
list_systems
All systems, compact: id, name, status, 1-line goal.
Solo lectura
Esquema de entrada
{'type': 'object', 'properties': {'project_id': {'type': 'string'}}}
next_task
DISPATCHER (multi-agent): atomically pick + claim the next task to build — walks milestones in order, skips human-only tasks and any task whose systems share code files with a task another agent already holds or is actively touching, so parallel agents spread out instead of colliding. Returns the claimed task + systems, or why none is free. dry_run:true peeks without claiming.
Esquema de entrada
{'type': 'object', 'properties': {'dry_run': {'type': 'boolean', 'description': 'Peek without claiming'}, 'project_id': {'type': 'string'}}}
post_log
Append a build-log entry to Activity — what you built/decided (commit-note style).
Esquema de entrada
{'type': 'object', 'required': ['text'], 'properties': {'text': {'type': 'string', 'description': 'What you did / decided (1–2 sentences)'}, 'entity': {'type': 'string', 'description': "System/screen/milestone it's about"}, 'version': {'type': 'string', 'description': 'e.g. "0.379.0"'}, 'project_id': {'type': 'string'}}}
propose_balance_board
Propose a node board → Inbox. Kinds const|formula|item|sheet|loadout|picker|pool|process|note|frame; formulas reference blocks by NAME; omit x/y = auto-layout. Adopting REPLACES same-named.
Esquema de entrada
{'type': 'object', 'required': ['name', 'nodes'], 'properties': {'name': {'type': 'string', 'description': 'Board name'}, 'nodes': {'type': 'array', 'items': {'type': 'object'}, 'description': 'e.g. {kind:"formula",name:"dmg",formula:"atk - mdef"}'}, 'project_id': {'type': 'string'}}}
propose_balance_table
Propose a stat-doc TABLE → Inbox. csv (header; `key%` = percent; first column = name) OR schema+rows. Adopting REPLACES same-named.
Esquema de entrada
{'type': 'object', 'required': ['title'], 'properties': {'csv': {'type': 'string', 'description': 'Header + rows; non-numeric = info'}, 'rows': {'type': 'array', 'items': {'type': 'object'}, 'description': '[{name, atk: 350, …}]'}, 'title': {'type': 'string', 'description': 'Table name'}, 'schema': {'type': 'array', 'items': {'type': 'object'}, 'description': '[{key, mode: flat|pct|text, base, min, max, desc}]'}, 'registry': {'type': 'boolean', 'description': 'true = the shared Stats registry'}, 'project_id': {'type': 'string'}}}
propose_context
Propose a new/updated Idea note → Inbox. Title-match to update; send the COMPLETE revised text. Set resync:true ONLY when you rewrote the note FROM the current systems (get_stale lists notes the systems have moved past) — it stops the adopted note from immediately nagging to re-generate the systems it was just written from.
Esquema de entrada
{'type': 'object', 'required': ['title', 'content'], 'properties': {'batch': {'type': 'string', 'description': 'import_from_code batch id'}, 'title': {'type': 'string', 'description': 'Match existing to update, or new to add'}, 'resync': {'type': 'boolean', 'description': 'This note was re-derived from the current systems — re-stamps both staleness signals on adopt'}, 'content': {'type': 'string', 'description': 'Complete text, not a delta'}, 'project_id': {'type': 'string'}, 'acknowledge_rejection': {'type': 'boolean', 'description': 'Only after a DECLINED bounce AND asking the user'}}}
propose_dna
Propose Project DNA and/or Tech Notes → Inbox (at least one).
Esquema de entrada
{'type': 'object', 'properties': {'dna': {'type': 'string', 'description': 'Omit to leave unchanged'}, 'batch': {'type': 'string', 'description': 'import_from_code batch id'}, 'project_id': {'type': 'string'}, 'tech_notes': {'type': 'string', 'description': 'Omit to leave unchanged'}}}
propose_element
SECONDARY (user-driven UI): propose an element onto a screen → Inbox. ALWAYS pass x/y/w/h (px on the screen's `resolution` from get_screen); no coords = unplaced pile.
Esquema de entrada
{'type': 'object', 'required': ['screen', 'label'], 'properties': {'h': {'type': 'number', 'description': 'Default 40'}, 'w': {'type': 'number', 'description': 'Default 120'}, 'x': {'type': 'number', 'description': 'Left px'}, 'y': {'type': 'number', 'description': 'Top px'}, 'note': {'type': 'string'}, 'type': {'type': 'string', 'description': 'button/bar/panel/text (default box)'}, 'label': {'type': 'string', 'description': "Element label, e.g. 'HP bar'"}, 'screen': {'type': 'string', 'description': 'Existing screen name'}, 'system': {'type': 'string', 'description': 'System it serves'}, 'project_id': {'type': 'string'}}}
propose_flow_edge
SECONDARY (user-driven UI): propose a link between two existing screens → Inbox.
Esquema de entrada
{'type': 'object', 'required': ['from', 'to'], 'properties': {'to': {'type': 'string', 'description': 'Destination screen name'}, 'from': {'type': 'string', 'description': 'Source screen name'}, 'label': {'type': 'string', 'description': 'Transition label (optional)'}, 'project_id': {'type': 'string'}}}
propose_milestone
Propose a NEW milestone (+ optional tasks) → Inbox.
Esquema de entrada
{'type': 'object', 'required': ['name'], 'properties': {'goal': {'type': 'string', 'description': 'One-line goal (optional)'}, 'name': {'type': 'string', 'description': 'Milestone name'}, 'tasks': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Task names (optional)'}, 'project_id': {'type': 'string'}, 'acknowledge_rejection': {'type': 'boolean', 'description': 'Only after a DECLINED bounce AND asking the user'}}}
propose_screen
SECONDARY (user-driven UI): propose a NEW screen → Inbox. parent = popup over that screen; purpose grounds AI suggestions. Whole UI? design_ui_from_systems first.
Esquema de entrada
{'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': 'Screen name (Title Case, English)'}, 'parent': {'type': 'string', 'description': 'Make it a POPUP over this screen'}, 'purpose': {'type': 'string', 'description': 'What this screen is for'}, 'project_id': {'type': 'string'}}}
propose_system
Propose a NEW system → Inbox. spec = ## Goal / ## Boundary (Owns · Doesn't own) / ## Acceptance. Exists? use update_system. (Alias: create_proposal.)
Esquema de entrada
{'type': 'object', 'required': ['title', 'spec'], 'properties': {'spec': {'type': 'string', 'description': 'Markdown: ## Goal / ## Boundary / ## Acceptance'}, 'batch': {'type': 'string', 'description': 'import_from_code batch id'}, 'files': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Implementing paths, ONE file per entry'}, 'title': {'type': 'string', 'description': 'System name (Title Case, English)'}, 'project_id': {'type': 'string'}, 'derives_from': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Context note title(s) this system derives from → wires provenance (upstream + siblings)'}, 'acknowledge_rejection': {'type': 'boolean', 'description': 'Only after a DECLINED bounce AND asking the user'}}}
rename_screen
Rename a screen IN PLACE — DIRECT; links/elements follow (id-referenced).
Esquema de entrada
{'type': 'object', 'required': ['name', 'new_name'], 'properties': {'name': {'type': 'string', 'description': 'Exact CURRENT name'}, 'new_name': {'type': 'string', 'description': 'New name (must not collide)'}, 'project_id': {'type': 'string'}}}
reorder
Reorder milestones / tasks / elements — DIRECT. order = ids in new order; omitted keep relative order.
Esquema de entrada
{'type': 'object', 'required': ['kind', 'order'], 'properties': {'kind': {'enum': ['milestones', 'tasks', 'elements'], 'type': 'string', 'description': 'What to reorder'}, 'order': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Ids in the new order'}, 'screen': {'type': 'string', 'description': 'For kind=elements'}, 'milestone': {'type': 'string', 'description': 'For kind=tasks (name)'}, 'project_id': {'type': 'string'}, 'milestone_id': {'type': 'string', 'description': 'For kind=tasks'}}}
report_build_status
Report a SYSTEM's status (todo|in-progress|implemented) — DIRECT, live. ALWAYS pass files (full list — it REPLACES); non-todo with no files shows done-but-EMPTY. 'implemented' counts as VERIFIED only when every UNIT-TESTABLE ## Acceptance bullet is backed via evidence[{criterion,proof}]; a bullet tagged [manual]/[e2e]/[ui]/[wip] is EXEMPT (verified by manual/e2e). Otherwise it's a CLAIM (verified:false) and the response names the unbacked criteria. TWO tiers: VERIFIED = a test is NAMED; GREEN (guarantee) = you RAN the test and reported `passed:true` on the evidence — green goes stale after 21 days, so re-run to keep it.
Esquema de entrada
{'type': 'object', 'required': ['status'], 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'files': {'type': 'array', 'items': {'type': 'string'}, 'description': "ONE file per entry (optional ' — function'); prose → decisions"}, 'status': {'type': 'string', 'description': 'todo | in-progress | implemented'}, 'version': {'type': 'string', 'description': 'e.g. "0.379.0"'}, 'evidence': {'type': 'array', 'items': {'type': 'object', 'properties': {'at': {'type': 'string', 'description': 'ISO time of the pass (defaults to now); green expires after 21d'}, 'proof': {'type': 'string'}, 'passed': {'type': 'boolean', 'description': 'true = you RAN this test and it passed → counts toward TEST-GREEN'}, 'criterion': {'type': 'string'}}}, 'description': 'Map ## Acceptance bullets to a test/file: [{criterion, proof, passed?, at?}]. Re-send full set (replaces). proof-only = backed (claimed); passed:true = test-green (guarantee).'}, 'decisions': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Decisions/divergences (prose)'}, 'project_id': {'type': 'string'}}}
report_drift
Flag CODE DRIFT — mapped files no longer match the repo. Advisory; a fresh report_build_status clears it.
Esquema de entrada
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'note': {'type': 'string', 'description': 'Optional — what drifted'}, 'project_id': {'type': 'string'}, 'missing_files': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Paths that no longer exist'}}}
report_milestone_progress
Mark existing-milestone tasks done → Inbox progress card (owner adopts the ticks).
Esquema de entrada
{'type': 'object', 'required': ['done_tasks'], 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'milestone': {'type': 'string', 'description': 'Milestone name (if no id)'}, 'done_tasks': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Task names that are done'}, 'project_id': {'type': 'string'}}}
report_screen_status
Report a SCREEN's status (todo|in-progress|implemented) → Inbox.
Esquema de entrada
{'type': 'object', 'required': ['screen', 'status'], 'properties': {'screen': {'type': 'string', 'description': 'Screen name'}, 'status': {'type': 'string', 'description': 'todo | in-progress | implemented'}, 'project_id': {'type': 'string'}}}
resolve_rejection
Report you REVERTED a declined change (unlocks the owner's Clear). Call after realigning the build.
Esquema de entrada
{'type': 'object', 'required': ['title'], 'properties': {'title': {'type': 'string', 'description': 'Exactly as get_rejections returned it'}, 'project_id': {'type': 'string'}}}
resync_from_idea
The recipe for re-syncing ONE changed Idea note into the specs that depend on it — the same scoped job the app's "Re-sync N systems" button does, minus the button. Returns the note, the affected specs in full, and exactly how to send the result back. You do the writing; it lands in the owner's Inbox to ADOPT. CRUCIAL: send updates with `resync:true`, or the owner adopts your fix and the design still reports it as stale.
Solo lectura
Esquema de entrada
{'type': 'object', 'required': ['note'], 'properties': {'note': {'type': 'string', 'description': "The Idea note's title or id (from get_stale)"}, 'project_id': {'type': 'string'}}}
search
Keyword search — compact hits {kind, id, name} + snippet.
Solo lectura
Esquema de entrada
{'type': 'object', 'required': ['query'], 'properties': {'kinds': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Optional: system | context | milestone | task | screen | proposal'}, 'query': {'type': 'string', 'description': 'Text to search for'}, 'project_id': {'type': 'string'}}}
set_design_overview
Write the Design Document's Overview — the human-readable page a new team member reads first. WRITES DIRECTLY (no Inbox): it is a derived, clearly-labelled AI summary, not design truth, and the owner can clear or rewrite it in one click. HARD RULES, same as the in-app button: use ONLY facts stated in the design (call get_design_document with for_summary:true first); invent no mechanics, numbers or names; describe, never evaluate; write in the design's dominant language. Structure: `### What this is` · `### The core loop` · `### How the systems fit` (which system feeds which — the part a raw spec list cannot give) · `### Edges` (ONLY if the design states scope limits / open questions). 250-400 words, no top-level heading. Forge stamps the project version it was compiled from, so the owner is told when the design has moved past it.
Esquema de entrada
{'type': 'object', 'required': ['summary'], 'properties': {'summary': {'type': 'string', 'description': 'The Overview in markdown, starting at `### What this is`'}, 'project_id': {'type': 'string'}}}
trace_ui_from_image
SECONDARY (user-driven UI): turn a screen's REFERENCE IMAGE into placed elements. Returns the image itself plus the recipe — the canvas resolution, the fraction→pixel conversion that stops coordinates landing wrong, and what is already on the screen so a second pass updates instead of duplicating. You look at the picture and send back propose_element / update_element with x/y/w/h; it all lands in the owner's Inbox. Use when the user wants the wireframe to match a screenshot or mockup they uploaded.
Solo lectura
Esquema de entrada
{'type': 'object', 'required': ['screen'], 'properties': {'screen': {'type': 'string', 'description': 'The screen whose reference image to trace (name or id)'}, 'project_id': {'type': 'string'}}}
update_element
Move/resize/relabel an element — DIRECT, live. element_id (preferred) or screen+label; x+y also places an unplaced one.
Esquema de entrada
{'type': 'object', 'properties': {'h': {'type': 'number'}, 'w': {'type': 'number'}, 'x': {'type': 'number', 'description': "px on the screen's canvas"}, 'y': {'type': 'number'}, 'note': {'type': 'string', 'description': '"" clears'}, 'type': {'type': 'string', 'description': 'e.g. button/bar/panel (optional)'}, 'label': {'type': 'string', 'description': 'Current label'}, 'screen': {'type': 'string', 'description': 'With label, if no element_id'}, 'system': {'type': 'string', 'description': 'System it serves'}, 'new_label': {'type': 'string', 'description': 'Rename (optional)'}, 'element_id': {'type': 'string', 'description': 'From get_screen (preferred)'}, 'project_id': {'type': 'string'}}}
update_milestone
Edit milestone goal/weeks/difficulty/name — DIRECT. new_name renames (never delete+recreate).
Esquema de entrada
{'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'goal': {'type': 'string'}, 'name': {'type': 'string', 'description': 'Current name (if no id)'}, 'weeks': {'type': 'number'}, 'new_name': {'type': 'string', 'description': 'Rename'}, 'difficulty': {'enum': ['easy', 'medium', 'hard', ''], 'type': 'string', 'description': '"" clears'}, 'project_id': {'type': 'string'}}}
update_system
Propose a system UPDATE → Inbox diff. get_system first; send the FULL revised spec. new_title renames; context_title+context bundles the Idea update. Set resync:true ONLY when you rewrote this spec FROM its upstream Idea (see resync_from_idea) — it re-stamps the staleness signal on adopt.
Esquema de entrada
{'type': 'object', 'required': ['spec'], 'properties': {'id': {'type': 'string', 'description': 'Preferred'}, 'name': {'type': 'string', 'description': 'If no id'}, 'spec': {'type': 'string', 'description': 'Full revised spec markdown'}, 'resync': {'type': 'boolean', 'description': 'This spec was re-derived from its upstream Idea — re-stamps sourceSig on adopt. Never set it on an ordinary edit.'}, 'context': {'type': 'string', 'description': 'Full revised Idea text'}, 'new_title': {'type': 'string', 'description': 'Rename in the same card'}, 'project_id': {'type': 'string'}, 'context_title': {'type': 'string', 'description': 'Idea section to also update'}, 'acknowledge_rejection': {'type': 'boolean', 'description': 'Only after a DECLINED bounce AND asking the user'}}}
update_task
Edit a task or CLAIM it — DIRECT. assignee:"me"+status:"in-progress" claims (errors if held; force:true for stale); done:true or assignee:"" releases.
Esquema de entrada
{'type': 'object', 'required': ['task_id'], 'properties': {'done': {'type': 'boolean', 'description': 'true releases the claim'}, 'name': {'type': 'string'}, 'force': {'type': 'boolean', 'description': 'Take over a STALE claim only'}, 'human': {'type': 'boolean', 'description': 'true = human-only (next_task/get_briefing skip it); false clears'}, 'effort': {'enum': ['S', 'M', 'L', ''], 'type': 'string', 'description': '"" clears'}, 'status': {'enum': ['in-progress', 'blocked', ''], 'type': 'string', 'description': '"" clears'}, 'task_id': {'type': 'string', 'description': 'From get_milestone'}, 'assignee': {'type': 'string', 'description': '"me" claims; "" releases'}, 'project_id': {'type': 'string'}}}
withdraw_proposal
Remove YOUR OWN still-pending Inbox item (id from the propose response / get_inbox).
Esquema de entrada
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': "The pending item's id"}, 'project_id': {'type': 'string'}}}
Historial
Cambios recientes en herramientas
Añadido
update_task
17 de September de 2026 a las 07:57
Añadido
next_task
17 de September de 2026 a las 07:57
Añadido
add_task
17 de September de 2026 a las 07:57
Añadido
update_milestone
17 de September de 2026 a las 07:57
Añadido
rename_screen
17 de September de 2026 a las 07:57
Añadido
report_screen_status
17 de September de 2026 a las 07:57
Añadido
propose_screen
17 de September de 2026 a las 07:57
Añadido
propose_element
17 de September de 2026 a las 07:57
Añadido
propose_flow_edge
17 de September de 2026 a las 07:57
Añadido
report_build_status
17 de September de 2026 a las 07:57
Añadido
report_milestone_progress
17 de September de 2026 a las 07:57
Añadido
propose_milestone
17 de September de 2026 a las 07:57
Añadido
propose_balance_board
17 de September de 2026 a las 07:57
Añadido
propose_balance_table
17 de September de 2026 a las 07:57
Añadido
get_balance
17 de September de 2026 a las 07:57
Añadido
update_system
17 de September de 2026 a las 07:57
Añadido
propose_dna
17 de September de 2026 a las 07:57
Añadido
propose_context
17 de September de 2026 a las 07:57
Añadido
propose_system
17 de September de 2026 a las 07:57
Añadido
search
17 de September de 2026 a las 07:57
Añadido
get_inbox
17 de September de 2026 a las 07:57
Añadido
list_activity
17 de September de 2026 a las 07:57
Añadido
get_milestone
17 de September de 2026 a las 07:57
Añadido
list_milestones
17 de September de 2026 a las 07:57
Añadido
reorder
17 de September de 2026 a las 07:57
Añadido
dedupe
17 de September de 2026 a las 07:57
Añadido
delete_entity
17 de September de 2026 a las 07:57
Añadido
withdraw_proposal
17 de September de 2026 a las 07:57
Añadido
update_element
17 de September de 2026 a las 07:57
Añadido
get_screen_image
17 de September de 2026 a las 07:57
Descubrir
Servidores MCP similares
cypher-mcp
io.github.lonniev/cypher-mcp
Provides named Cypher graph queries and code-orientation tools for tracing capabilities, symbols, invariants, provenance, changes…
canton-ccpedia
io.github.UnityNodes/canton-ccpedia
Searches and explains Canton Network and Daml documentation, governance proposals, forums, code examples, APIs, releases, and eco…
ALM X++ MCP Server
io.github.alimbenhelal-pro/alm-xpp-mcp
Supports D365 Finance and Operations development with X++ and AOT search, code analysis, Azure DevOps workflows, telemetry querie…
Kaiku
tech.kaiku/kaiku
Manages team issues, comments, attachments, projects, wiki pages, and related development workflows.
api-evangelist
com.apievangelist/api-evangelist
Provides API governance analysis, OpenAPI overlays and version diffs, security-sensitive field classification, code samples, matu…
Avalanche AVAX MCP
io.github.Airpote/avalanche-docs
Searches and retrieves Avalanche documentation, community proposals, CLI guidance, Builder Console workflows, blockchain identifi…
Github
io.github.pipeworx-io/github
Reads public GitHub repository files, releases, commits, issues, repository metadata, user profiles, and trending repositories.
blobpedia
io.github.UnityNodes/blobpedia
Provides searchable Celestia documentation, governance proposals, forum and GitHub discussions, ecosystem information, release ch…