#260 Publish the MCP server in MCP directories and curated lists

[Anonymous]

Originally created by: Avazbek22

Summary

The MCP server ships with the app, but it is invisible in the places where people actually discover MCP servers. Agent users pick servers from directories and curated lists, not from app stores. This issue tracks getting DevProjex listed everywhere an MCP user might look, so the server competes on discovery, not only on features.

Directory listings

Submit DevProjex to the established MCP directories. Each listing should use the same short description, the devprojex mcp --root . quick start, and link to Docs/McpServer.md for the tool reference and security model:

• [ ] PulseMCP (pulsemcp.com)
• [ ] Glama MCP directory (glama.ai/mcp/servers)
• [ ] LobeHub MCP catalog (lobehub.com/mcp)
• [ ] mcpservers.org
• [ ] MCP Market (mcpmarket.com)
• [ ] Smithery, if a listing is possible for a locally-installed stdio server

Where a directory renders a README, the listing copy should lead with the workflow differentiators (exploration before packing, token metrics, detail: signatures, session packs with ranged reads) and the security model (always-on secret redaction with no off switch, untrusted-content markers, root jail, offline stdio-only design) — not just the tool list.

Curated lists

• [ ] Open a PR to punkpeye/awesome-mcp-servers (and mirror lists it links) adding DevProjex under the developer-tools / code-analysis section.
• [ ] Check other maintained "awesome" lists that cover codebase-context tooling and add the MCP server where it fits.

GitHub discoverability

• [ ] Add repository topics that MCP users actually search: mcp, mcp-server, model-context-protocol, alongside the existing product topics.
• [ ] Verify the repository description mentions the MCP server explicitly.

Supporting material

Listings convert better with proof. Before or shortly after submitting:

• [ ] A short comparison note in the docs measuring the same agent task through a pack-first workflow versus DevProjex exploration tools (tokens consumed, calls made), so listing descriptions can cite numbers instead of adjectives.
• [ ] A security summary page framed around the criteria MCP security reviews use (prompt injection resistance, secret leakage, permission scope), assembled from the existing Docs/McpServer.md security model.

Acceptance criteria

• DevProjex appears in at least the four major directories above with consistent copy.
• The awesome-mcp-servers PR is merged or actively under review.
• Repository topics and description updated.
• Listing copy reviewed against the actual v1 tool surface — no overclaims.