Get @archsmith/mcp-server listed in public MCP directories/registries #14

Problem

Someone who has a Claude Desktop / Cursor / Cline install and wants "a tool that renders architecture diagrams" has no path to find ArchSmith today unless they already know it exists. npm search doesn't cover MCP-specific intent, and the MCP ecosystem has developed its own directories that are the actual discovery surface for agent users.

Zero external directory listings today. Each listing is a separate one-time submission — worth tracking as a checklist so nothing slips.

Proposed shape

Meta-issue. Submit @archsmith/mcp-server to each of the following, in rough order of impact:

• modelcontextprotocol/servers — the community-curated list Anthropic maintains. Highest-signal directory.
• Smithery.ai — package-manager-style discovery for MCP servers; growing traction.
• mcp.so — community-run MCP directory + search.
• Cline marketplace — Cline's own MCP marketplace surface (in-editor discovery).
• Anthropic's official MCP registry — check state of play before submitting; the landscape moved a lot in 2025 (a first-party registry launched then was partly deprecated). May not be worth spending effort on today.

Each is a small, independent PR/form submission. None require code changes in this repo.

Update the README (probably a new "Where to find ArchSmith" section) to mention which directories ArchSmith is listed in, so a visitor browsing one directory can jump to the others.

Open questions

• Most directories require capability metadata (categories, tags, example prompts, screenshots). Worth stashing a canonical docs/mcp-directory-listing.md in the repo with the blurb + tags + example prompts so submissions stay consistent instead of drifting per-directory.
• MCP directory landscape is genuinely fluid — re-verify each listed directory is active and accepting submissions before starting. modelcontextprotocol/servers is definitely stable; the others should be re-checked.
• One-off submission vs. ongoing update. If we ship a new capability (e.g. HTTP/SSE transport from Add HTTP/SSE transport option for the MCP server #4), does each directory need re-notifying? Probably yes for the bigger ones; capture that as part of the release checklist.