Skip to content

Submit to awesome-mcp directories for discovery #1

@zhiganov

Description

@zhiganov

What

Submit harmonica-mcp to community MCP directories so AI-agent users can discover it. Triggered by a 2026-05-04 conversation about distribution strategy across the workspace's MCP servers; sibling tracking issue at zhiganov/book-power#23 for the book-power family.

harmonica-mcp is uniquely positioned among our MCPs because it's already npm-published (v0.4.7) and is the only one with a real version trail — that's a credibility signal worth surfacing in directory entries.

Verified directories (all reachable as of 2026-05-04)

Repo / URL Notes
https://github.com/modelcontextprotocol/servers Official MCP project's servers/ repo, "Third-Party" section. Highest-credibility surface.
https://github.com/punkpeye/awesome-mcp-servers Most-starred community awesome-list.
https://github.com/wong2/awesome-mcp-servers Second large community list.
https://github.com/appcypher/awesome-mcp-servers Third community list.
https://mcp.directory Web directory site — claims "one-click install." Submission flow TBD.
https://mcpservers.org Web directory site listing official + community MCPs. Submission flow TBD.

Listing copy (draft)

harmonica-mcp — MCP server for Harmonica deliberation sessions. Create, query, and analyze sessions from any AI agent via npx harmonica-mcp or HTTP. Use cases: agentic facilitation workflows, post-session analysis, multi-step deliberation orchestration.

npm: https://www.npmjs.com/package/harmonica-mcp · GitHub: https://github.com/harmonicabot/harmonica-mcp

Categories likely apply: AI agents, collaboration, knowledge management, research, possibly government or civic depending on how each list segments.

Priority

  1. modelcontextprotocol/servers (Third-Party section) — official-repo signal
  2. punkpeye/awesome-mcp-servers — largest community awesome-list
  3. mcpservers.org and mcp.directory — directory sites
  4. The other awesome-list repos

Per-submission effort

  • Awesome-list PRs: ~5 min each (clone, add line under matching category in alphabetical order, PR with brief description). Typically merged within a day or two.
  • Directory sites: depends on submission flow.

After listings land

Add a "Listed in" or "Find us in" line to README pointing back at each accepted submission so future visitors can verify the listings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions