distribution: ship a first-class MCP server and submit to the MCP registry + awesome-mcp-servers

[dgenio]

Why

ChainWeaver is MCP-native (chainweaver[mcp]), and the MCP ecosystem is the single best-trafficked discovery channel for this exact audience. Being listed in the official MCP registry and the popular awesome-mcp-servers lists is high-leverage passive reach — qualified users find you without a launch push.

Proposal

• Polish chainweaver.mcp into a documented, first-class "expose your flows as MCP tools" server with a one-command start and a minimal config example.
• Write a dedicated docs page: "Use ChainWeaver as an MCP server."
• Submit/PR to:
  • the official MCP servers registry,
  • punkpeye/awesome-mcp-servers (and other prominent awesome-mcp lists),
  • relevant awesome-ai-agents / awesome-llm-apps lists.
• Add the mcp / model-context-protocol topics (already present) + ensure the MCP server is discoverable from the README.

Acceptance criteria

• One documented command starts a ChainWeaver MCP server exposing registered flows as MCP tools.
• Docs page exists and is linked from the README.
• At least one accepted (or submitted) listing in the MCP registry and one awesome-list.

This is a distribution/listing issue distinct from the existing MCP adapter code.