Developer · Remote MCP server
Forge Engine
Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.forgeengine/forge- Version
- 0.2.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-29
- Updated
- 2026-07-29
- Publisher
- app.forgeengine
- Namespace
- Namespace verified by the MCP Registry via the domain forgeengine.app · how
- Website
- forgeengine.app/
- Repository
- github.com/alongkornonline2019/forge-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- forge 0.1.0 · protocol 2025-06-18
- Tools discovered
54 - show 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,propose_balance_table,propose_balance_board,propose_milestone,report_milestone_progress,report_build_status,propose_flow_edge,propose_element,propose_screen,report_screen_status,rename_screenand 4 more- Checked on
- 2026-10-05
How to connect Forge Engine
Forge Engine is a remote MCP server: there is nothing to install. Its endpoint is https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| footnote-mcpSource-grounded web research: search, extraction, verification, and browser automation. | Local · stdio |
| ForemergeCoordinate parallel coding agents, above Git. | Local · stdio |
| Forensic DeepdivePersistent code knowledge graph + 9 composite MCP tools for AI coding agents. | Local · stdio |
| ForgeMCP server for Forge, Voxell's embedding API. Voxell's Ingot-8B-R3 ranks #1 for English on MTEB. | Local · stdio |
| Forge OrchestratorMulti-tool AI orchestration: Claude Code, Codex, Gemini on shared repos. 11 MCP tools, stdio. | Local · stdio |
| ForgeCraftProduction engineering standards for AI coding assistants. Setup once, remove when done. | Local · stdio |
| ForgejudgeOpen eval leaderboard + CI gate for autonomous coding agents (solve, score, trace). | Local · stdio |
| ForgeprintResolve a developer profile to exactly one project blueprint and return its CI-tested setup recipe. | Local · stdio |