wuerthcs/flywheel-mcp-servers

Flywheel MCP Servers

Custom MCP servers used by the Flywheel Flutter team. These servers help Codex:

• follow project conventions and testing rules
• reuse a shared implementation plan template
• reduce hallucinations and enforce architecture patterns

Folder Structure

Each MCP server lives in its own top-level folder (no shared servers/ directory).

flywheel-mcp-servers/
├── README.md
├── package.json
├── node_modules/ (ignored)
└── flutter-codex-guard/
    ├── flutter-codex-guard.mjs
    └── docs/
        └── flutter_codex_guidelines.md

Current servers:

• flutter-codex-guard
  • guidelines://flutter-codex → flutter-codex-guard/docs/flutter_codex_guidelines.md
  • template://flutter-plan → built-in implementation plan template

Installation (run once)

1) Clone this repository

mkdir -p $PATH_TO_REPO
git clone https://github.com/<your-org>/flywheel-mcp-servers.git $PATH_TO_REPO/flywheel-mcp-servers

2) Install Node dependencies

cd $PATH_TO_REPO/flywheel-mcp-servers
npm install

Update your Codex configuration

Edit ~/.codex/config.toml and add:

model = "gpt-5.1-codex"
model_reasoning_effort = "high"

[mcp_servers.flutter-codex-guard]
command = "node"
args = ["$PATH_TO_REPO/flywheel-mcp-servers/flutter-codex-guard/flutter-codex-guard.mjs"]
startup_timeout_ms = 20000

✔️ Replace $PATH_TO_REPO with your local path.

Restart VS Code

Quit VS Code completely and reopen. The Codex extension will reload the MCP server automatically.

Verify the MCP server

In the Codex chat panel, try:

Read guidelines://flutter-codex and summarize it in 3 bullet points.

Expected: Codex summarizes flutter-codex-guard/docs/flutter_codex_guidelines.md.

You can also test the implementation plan template:

Read template://flutter-plan

If Codex reports “unknown MCP server,” check:

• the path in config.toml
• whether npm install was executed
• the repository path ($PATH_TO_REPO/flywheel-mcp-servers)

How to add a new MCP

1. Create a new folder at the repo root (e.g., my-new-server/).

2. Add the server entrypoint (e.g., my-new-server/my-new-server.mjs) and any supporting docs (e.g., my-new-server/docs/...).

3. Update ~/.codex/config.toml with a new block:

   [mcp_servers.my-new-server]
   command = "node"
   args = ["$PATH_TO_REPO/flywheel-mcp-servers/my-new-server/my-new-server.mjs"]
   startup_timeout_ms = 20000
   

4. Restart VS Code so the Codex extension reloads servers.

5. Verify by asking Codex to read one of the new resources (for example, a guidelines file or template you expose).

📄 License

Internal use only.