Coordination: CodeMode vs external context/routing strategies (contextweaver)

[dgenio]

Hats: I contribute to FastMCP and I maintain contextweaver (link below). Posting to avoid duplicated effort.

CodeMode targets the same core pain: large tool catalogs (token bloat + round-trip churn). My read is:

• CodeMode = execution/orchestration via discovery meta-tools + sandboxed chaining
• contextweaver = policy layer for routing/shortlisting + context compaction (“what to show the model”)

Question for maintainers: do you want tool-catalog scaling (routing/shortlisting/compaction) to live in FastMCP core/contrib, or stay an ecosystem of strategies plugged via CodeMode’s custom discovery tools?

If useful, I’m happy to contribute a neutral example (no hard dependency) showing a custom discovery tool that returns top-K tools + compact schemas/tags.

Links:

• CodeMode docs: https://gofastmcp.com/servers/transforms/code-mode
• contextweaver: https://github.com/dgenio/contextweaver