next_task — Forge Engine MCP Tool
next_task
(next task) is one of 54 tools on the
Forge Engine
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call next_task from your client
- Claude Code Forge Engine next_task run in your project directory
- Claude Desktop Forge Engine next_task ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Forge Engine next_task ~/.cursor/mcp.json
- VS Code Forge Engine next_task .vscode/mcp.json
- Zed Forge Engine next_task ~/.config/zed/settings.json
- Windsurf Forge Engine next_task ~/.codeium/windsurf/mcp_config.json
- Cline Forge Engine next_task ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Forge Engine next_task ~/.gemini/settings.json
- Grok Forge Engine next_task .mcp.json (in your project root)
- ChatGPT Forge Engine next_task Settings → Connectors → Advanced → Developer mode
- Claude.ai Forge Engine next_task Settings → Connectors → Add custom connector
- LangChain Forge Engine next_task pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http forge https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcpOther tools on this server
- 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_screen
- update_milestone
- add_task
- update_task
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.