RomanNum3ral
/
MicroFish
mirror of https://github.com/666ghj/MiroFish.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
MicroFish/docs/agent-usage/mcp.md

2.9 KiB
Raw Blame History

MiroFish MCP Server

The MCP server exposes MiroFish lifecycle tools, not a Graphiti proxy.

Start:

cd /Users/leaf/Documents/future/MiroFish/backend
uv run mirofish-mcp

Tools:

  • mirofish_create_run
  • mirofish_run
  • mirofish_resume_run
  • mirofish_get_status
  • mirofish_get_current_stage
  • mirofish_update_simulation_settings
  • mirofish_approve_stage
  • mirofish_reject_stage
  • mirofish_rerun_stage
  • mirofish_list_requests
  • mirofish_get_request
  • mirofish_submit_response
  • mirofish_validate_response
  • mirofish_build_graph
  • mirofish_search_graph
  • mirofish_export_graph
  • mirofish_start_simulation
  • mirofish_resume_simulation
  • mirofish_generate_report
  • mirofish_get_report
  • mirofish_ask_followup_question
  • mirofish_get_followup_answer
  • mirofish_list_artifacts
  • mirofish_doctor

Staged Mode

Use staged mode when a desktop agent should mirror the original MiroFish step-by-step UI flow. The simulation round count is a hard MCP field, not text hidden in the requirement.

Typical Qoder/Codex/Claude Code sequence:

  1. Call mirofish_doctor.
  2. Call mirofish_create_run with mode="staged", rounds=10, round_unit="year", and the seed/requirement/output path.
  3. Call mirofish_get_current_stage and show the user the stage summary.
  4. After user confirmation, call mirofish_approve_stage.
  5. Call mirofish_resume_run; staged mode advances only to the next pause point or need_agent_response.
  6. When need_agent_response appears, read request_file, write the response JSON, call mirofish_validate_response, then mirofish_submit_response.
  7. Repeat resume/approve until report.md, verdict.json, timeline.json, and graph_snapshot.json exist.
  8. Use mirofish_ask_followup_question for post-report questions.

Example mirofish_create_run arguments:

{
  "seed": "/Users/leaf/Documents/future/MiroFish/seeds/chip.md",
  "requirement": "预测未来10年全球芯片能力格局变化",
  "output": "/Users/leaf/Documents/future/MiroFish/runs/chip-2036",
  "mode": "staged",
  "rounds": 10,
  "round_unit": "year",
  "minutes_per_round": 525600,
  "pause_each_round": false,
  "agent_count": 5,
  "simulation_name": "chip-2036"
}

If the user changes hard parameters before approval, call mirofish_update_simulation_settings. The engine marks dependent stages stale/pending so old profile/config/simulation/report outputs are not silently reused.

Example MCP server config:

{
  "mcpServers": {
    "mirofish": {
      "command": "uv",
      "args": ["run", "mirofish-mcp"],
      "cwd": "/Users/leaf/Documents/future/MiroFish/backend",
      "env": {
        "MIROFISH_MODE": "agent",
        "MIROFISH_LLM_PROVIDER": "agent_queue",
        "MIROFISH_GRAPH_PROVIDER": "graphiti",
        "MIROFISH_RUNS_DIR": "./runs"
      }
    }
  }
}

Reference: https://modelcontextprotocol.github.io/python-sdk/server/