MetehanGZL Pokemcp vs Ue MCP

MetehanGZL Pokemcp tools

No tool names declared yet. Check the project README from the listing page.

Ue MCP tools 2

• toolsGateway to every ue-mcp category (micro context mode). Find actions with search, inspect parameters with describe, then invoke with call. Actions: - search: Find actions by keyword or intent; returns category.signature lines. Params: query, limit? (default 20) - list_categories: List every category with a one-line summary. - describe: A category's action signatures a page at a time, or one action's parameter schema. Params: category, method?, offset? - call: Invoke any action. Params: category, method (the action name), args (object of the action's params).
• flowRun pre-built named sequences for this project. ALWAYS check project(action="get_status") first - its 'flows' field lists what's available. If a flow matches the user's request, run it via flow(action="run", flowName="...") instead of composing the sequence by hand. Config reloads on every call - no restart needed. Actions: - run: Execute a named flow from ue-mcp.yml. Params: flowName, skip? (step names or numbers), params? (runtime options merged into every step's options, highest priority), rollback_on_failure? (invoke inverse tasks in reverse order when a later step fails). A step whose handler reports success:false FAILS the step and stops the run, and the inverses collected up to and including it are what rollback_on_failure unwinds. A step whose failure is EXPECTED says so itself, in the YAML, with ignore_failure: true - the run walks on, and the step is still recorded as failed with its error and its data, marked ignoredFailure. That is how stop, build, start survives an editor that was already stopped, instead of editor(stop_editor) reporting a success it did not achieve. The failing step's OWN inverse, which a few handlers attach after a partial write, is collected like every other: under rollback_on_failure it is replayed FIRST, ahead of the steps before it, so the partial write is undone before they unwind. It arrives verbatim on steps[i].partialWriteRollback, whose replayed flag says whether the runner ran it or it is yours to run, and in that step's error text. A nested flow's steps arrive on steps[i].nestedSteps, reported on the same terms. Returns a summary, every step's data, and the runId. - plan: Show a flow's execution plan without running a step of it. Params: flowName. Returns the ordered plan, and the flow as declared under definition: its description and each step's task or nested flow, options and conditions, with ${steps.N...} references left unresolved. - list: List the flows available to this project, merged from ue-mcp.yml, the user-global config and any loaded plugin. Params: none Step types supported in YAML flows: any MCP action (category.action), nested flows (flow:), and 'shell' for running shell/exec commands. Per-step options: options, when, retries, retryDelay, retryOn, and ignore_failure (record this step's failure and carry on). Example shell step: steps: 1: { task: shell, options: { command: "npm run up:build" } }