Forge Engine
Design source-of-truth for AI coding agents to read a project's systems and propose changes back.
https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- forge
- Version
- 0.1.0
- Capability keys
- tools
- Tool names
- get_help, get_workflow, import_from_code, design_ui_from_systems, post_log, get_project_context, list_projects, get_project_meta, trace_ui_from_image, get_stale, resync_from_idea, get_design_document, set_design_overview, get_briefing, get_system, list_systems, get_build_region, report_drift, get_history, get_impact, get_rejections, resolve_rejection, list_screens, get_screen, get_screen_image, update_element, withdraw_proposal, delete_entity, dedupe, reorder, list_milestones, get_milestone, list_activity, get_inbox, search, propose_system, propose_context, propose_dna, update_system, get_balance (first 40 recorded; the server may expose more)
Forge is the live design source-of-truth (vision, Systems[Goal/Boundary/Acceptance], screens, milestones, Inbox) a coding agent builds from. You READ the design and PROPOSE changes — proposals + deletes go to the owner's Inbox to ADOPT in the web app at https://forgeengine.app (you can't adopt or hard-delete). Connect with a forge_sk_ key (Bearer token) — generate one in the web app under "Connect a coding agent"; if the user isn't connected, tell them they can either add the key to their MCP config themselves or paste it to you in chat. Start with get_project_meta; pass project_id (from list_projects) to switch projects. An account key reaches EVERY project its owner has, and nothing pins this connection to one — so CONFIRM which project you are in before you write. Project NAMES are not unique (an account can hold two projects called the same thing, e.g. a port or a sequel), so match on the `id` from list_projects, never on the name. Writing to the wrong project raises no error
Reported Aug 17, 2026, 05:05 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 236ms
- respondsMCP initialize · 8s limit · HTTP 200 · 320ms
- respondsMCP initialize · 8s limit · HTTP 200 · 206ms
- respondsMCP initialize · 8s limit · HTTP 200 · 310ms