batteryshark Create a FastMCP Server
- Clarify the server boundary, consumers, transport, authentication owner, side effects, and whether the core logic must also serve a CLI or library.
- Read references/current-fastmcp.md and pin a tested FastMCP 3 minor range; do not silently copy version-sensitive APIs from memory.
- Run
bin/mcp-server-create NAME --target-dir PATHto generate a library-first project withfastmcp.json, tests, and explicit stdio defaults. - Replace the example operation with typed core functions. Keep FastMCP decorators, context, auth, and transport concerns in the thin server envelope.
- Add only the interaction layer the product needs: protocol elicitation for client-mediated input, Apps for embedded UI, or ordinary tool arguments for model-supplied data.
- Run the generated unit and in-memory protocol tests, inspect the component catalog, and exercise the real deployment transport only after local behavior is correct.
Use agents/server-reviewer.md for an independent boundary and safety review.