Enovari GitHub Presence Strategy

Additional Info
Stars are the developer world's equivalent of social media followers. They signal: "This project is worth looking at" "Other developers trust this" "This is actively maintained" 0-50 stars: Invisible. No credibility signal. 50-200 stars: Shows up in "similar projects" recommendations. Minimally credible. 200-500 stars: Appears in GitHub Explore recommendations. Considered noteworthy. 500-1000 stars: Serious credibility. Shows up in roundup articles and lists. 1000+: Established project. Self-sustaining discovery through GitHub's algorithms. 1. Post to relevant subreddits (r/ClaudeAI, r/ChatGPTPro, r/LocalLLaMA, r/MCP) when you launch the repo 2. Share on X/Twitter with demo GIFs 3. Ask early users/beta testers to star the repo 4. Submit to awesome lists (each listing drives 10-50 stars) 5. Write a "Show HN" post on Hacker News when ready 6. Create genuinely useful content that people want to bookmark (the awesome list strategy) 7. Cross-promote from your website ("Star us on GitHub" button) 8. Include "If Enovari is useful to you, consider giving us a star" in the README footer Buy stars (GitHub detects and penalizes this) Use star-for-star exchange groups Create fake accounts to star your repo

Additional Info
Awesome lists are curated directories on GitHub that developers use to discover tools. Getting listed drives sustained traffic and stars. Read the contribution guidelines carefully Follow the exact format of existing entries Keep descriptions concise (one line) Include only stable, working links Don't submit to the same list twice Wait until your repo has at least a solid README before submitting ``markdown [Enovari](https://github.com/enovari/mcp-server-enovari) - Persistent, portable AI memory across sessions and platforms. Cross-session recall, persona system, 140+ API integrations. ``

Additional Info
Enable GitHub Discussions on mcp-server-enovari. This is free, indexed by Google, and keeps community interaction tied to your GitHub presence. Google indexes Discussions (SEO value) Reduces support burden (searchable Q&A) Creates sense of active community Contributors appear on your org page Discussion count shows on repo page

Additional Info
Use GitHub Pages to host documentation at enovari.github.io/docs or configure a custom domain like docs.enovari.ai. Docusaurus (by Meta) — Best for product docs. Used by many MCP-related projects. Repo: github.com/facebook/docusaurus Versioned docs, search, blog, i18n built-in MkDocs Material — Python-based, simpler. Beautiful defaults. Repo: github.com/squidfunk/mkdocs-material Mintlify — Designed specifically for API docs. Beautiful out of the box. URL: mintlify.com ``yaml # .github/workflows/deploy-docs.yml name: Deploy Documentation on: push: branches: [main] jobs: deploy: runs-on: ubuntu-latest steps: uses: actions/checkout@v4 uses: actions/setup-node@v4 with: node-version: 20 run: npm ci run: npm run build uses: peaceiris/actions-gh-pages@v3 with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir: ./build ``

Additional Info
Even without source code, you can use GitHub Actions to create "activity signals": 1. Config validation — CI that validates all example config files are valid JSON/YAML 2. Link checking — Automated checks that all docs links are live 3. API health check — Scheduled workflow that pings enovari.ai API and updates a status badge 4. Changelog generation — Auto-generate changelog from PR titles 5. SDK tests — If you publish SDKs, run their test suites publicly ``markdown [![API Status](https://img.shields.io/endpoint?url=https://enovari.ai/api/health-badge)](https://enovari.ai) [![npm version](https://img.shields.io/npm/v/mcp-server-enovari)](https://npmjs.com/package/mcp-server-enovari) [![Discord](https://img.shields.io/discord/YOUR_ID?label=Discord&;logo=discord)](https://discord.gg/enovari) [![GitHub stars](https://img.shields.io/github/stars/enovari/mcp-server-enovari)](https://github.com/enovari/mcp-server-enovari) [![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) ``

Additional Info
High-visibility strategy: contribute to projects your potential users already use. Every contribution links back to your GitHub profile, which links to your org, which links to Enovari.

Additional Info
GitHub repos rank extremely well in Google because: GitHub has massive domain authority (DA 95+) READMEs are crawled as the page content Repo metadata (description, topics) become meta tags Stars correlate with higher rankings Regular commits signal fresh content Repository main page (README) All markdown files in the repo GitHub Discussions threads GitHub Pages sites Issue titles and bodies Wiki pages

Additional Info
Follows the mcp-server-{name} convention used across the MCP ecosystem This exact pattern is what MCP directories search for Google searches for "mcp server memory" will surface this enovari-docs — Captures "enovari documentation" searches enovari-examples — Captures "enovari examples" or "enovari setup" searches awesome-ai-memory — Captures "ai memory tools" searches (massive SEO play)

Additional Info
The GitHub repo description appears in: Google search results (as meta description) GitHub search results GitHub Explore pages Social media previews (Open Graph) Front-load keywords ("MCP server", "AI memory", "persistent") Include platform names people search for ("Claude", "ChatGPT", "Cursor") Stay under 350 characters (GitHub's display limit) No emojis in descriptions (they don't render in search results)

Additional Info
Topics are GitHub's tagging system. They drive discoverability through: Topic browse pages (github.com/topics/mcp) GitHub search filters "Related repositories" suggestions GitHub Explore recommendations `` mcp mcp-server model-context-protocol ai-memory persistent-memory claude chatgpt cursor ai-assistant llm ai-tools developer-tools memory context api ` ` awesome awesome-list ai-memory llm-memory persistent-memory ai-tools mcp rag vector-database ai-agents ` Maximum 20 topics per repo Mix high-volume topics (ai, llm, developer-tools) with specific ones (mcp-server, ai-memory) Check existing topic pages to see competition: github.com/topics/mcp-server Create the enovari` topic and use it across all your repos

Additional Info
GitHub Trending (github.com/trending) shows repos with the most stars gained in a period. To appear: Coordinate a launch day (post to HN, Reddit, X, Discord all at once) Aim for 30+ stars in a single day to trend in a language category Trending in "All Languages" requires 100+ stars/day GitHub Explore (github.com/explore) is curated and algorithmic: Having 100+ stars helps Active maintenance (recent commits) is required Good README quality signals Relevant topics help categorization You can submit collections: github.com/explore/submit

Additional Info
Every repo should have a custom social preview image (1280x640px). This appears when someone shares the GitHub link on: X/Twitter LinkedIn Discord Slack Reddit Left side: Enovari logo Center: Repo name and one-line description Right side: Key feature icons or platform logos Background: Dark, clean, matching enovari.ai branding Tools: Canva, Figma, or any design tool Set via: Repo Settings > Social Preview > Edit > Upload image

Additional Info
The repo is essentially a feature-request and bug-tracking hub README has a beautiful hero image and clear product description GitHub Issues are the primary feedback mechanism Thousands of issues/discussions create organic SEO They use GitHub releases to publish changelogs Stars are massive despite having zero source code in the repo

Additional Info
SDKs are the public-facing repos (actual useful code) Clean API documentation Active issue management on SDK repos Community creates additional repos that reference Notion

Additional Info
Org page is clean and professional Main repo is for community feedback SDK packages are published to npm Active GitHub Discussions

Lesson for Enovari
Open-source complementary tools (e.g., a memory visualization tool, an MCP config validator) while keeping the core proprietary.

Additional Info
Extensions repo is a massive community contribution magnet Open-sourced complementary tools (not the core product) Beautiful org profile page Multiple repos showing activity Community contributions make the org look large and active

Additional Info
Main repo README is a masterclass in conversion Beautiful comparison tables ("Supabase vs Firebase") Multi-language SDK repos Active community (thousands of contributors) GitHub Sponsors enabled

Lesson for Enovari
Open-sourcing a useful framework or tool adjacent to your core product is the ultimate GitHub marketing strategy. Consider open-sourcing an "MCP memory toolkit" or "MCP testing framework."

Lesson for Enovari
Cookbooks and examples repos get massive stars. An "Enovari Cookbook" repo with copy-paste workflows would be very effective.

Lesson for Enovari
This is the benchmark to beat. Study their README structure closely. Note: they open-sourced the core, but Enovari can achieve similar visibility with docs/SDKs alone — it just requires more effort in other areas.

Additional Info
Massive README with badges, GIFs, comparison tables "Quickstart in 5 lines of code" right in the README Active community engagement Listed in every relevant awesome list Regular releases with changelogs

Additional Info
Clean, professional README Good documentation Active in AI memory community

Additional Info
Open-sourced their documentation components Main product is proprietary Users create repos using their tools (viral spread)

Additional Info
Extremely transparent development (public roadmap) Active social media linking to GitHub Multiple satellite repos for integrations

Additional Info
The Model Context Protocol ecosystem is rapidly growing. Being listed in directories is the single highest-ROI activity for MCP server discovery.

Directory 1: Official MCP Servers Repository
URL: github.com/modelcontextprotocol/servers Maintained by: Anthropic / MCP core team Stars: ~15,000+ (as of early 2025, likely 25,000+ by now) How to get listed: Add your server to the "Community Servers" section of the README Submit a Pull Request following their contribution format Your server must implement the MCP protocol correctly Include: name, one-line description, link to repo Format example: ``markdown [Enovari](https://github.com/enovari/mcp-server-enovari) - Persistent, portable AI memory with cross-session recall, personas, and 140+ API integrations. `` Priority: HIGHEST — This is the canonical directory

Directory 2: awesome-mcp-servers (punkpeye)
URL: github.com/punkpeye/awesome-mcp-servers Stars: ~10,000+ (one of the most popular MCP lists) How to get listed: Submit a Pull Request Follow the awesome-list format Your server must be functional and documented Category for Enovari: "Knowledge & Memory" or similar Priority: HIGH

Directory 3: awesome-mcp-servers (wong2)
URL: github.com/wong2/awesome-mcp-servers Stars: ~5,000+ How to get listed: Pull Request following their format Priority: HIGH

Directory 4: MCP Hub / mcp.so
URL: mcp.so (web directory) How to get listed: Submit through their website Priority: HIGH — Web-based discovery, separate from GitHub

Directory 5: Smithery
URL: smithery.ai How to get listed: Register and submit your MCP server Priority: HIGH — Growing MCP marketplace

Directory 6: Glama MCP Directory
URL: glama.ai/mcp/servers How to get listed: Submit through their platform Priority: MEDIUM

Additional Info
The MCP ecosystem has a strong naming convention: mcp-server-{name}. Following this is critical: Repo name: mcp-server-enovari npm package: mcp-server-enovari This naming convention is how directories, tools, and developers find MCP servers GitHub search for mcp-server- returns thousands of results — you want to be in that list

Additional Info
Most directories require your repo README to include: 1. What the server does (one paragraph) 2. Installation instructions (copy-paste ready) 3. Configuration for Claude Desktop (JSON snippet) 4. Available tools (table of tool names + descriptions) 5. Available resources (if any) 6. Authentication (how to get API key) 7. Example usage (at least one concrete example)

Additional Info
Many MCP servers are installed via npx mcp-server-{name}. Publishing to npm: Makes installation trivially easy Gets your package indexed in npm search Allows npx one-command setup (the standard in MCP ecosystem) Adds a version badge to your README The npm package can be a thin wrapper/installer that connects to your cloud service — it doesn't need to contain the actual server logic if Enovari runs as a hosted service.

Additional Info
```markdown <div align="center"> <img src="assets/logo.svg" width="100" alt="Enovari" /> # Enovari MCP Server Persistent, portable AI memory across every platform. Your AI forgets everything. Enovari remembers. [](https://npmjs.com/package/mcp-server-enovari) [](https://enovari.ai) [](https://github.com/enovari/mcp-server-enovari/stargazers) [](https://discord.gg/enovari) [](LICENSE) [Website](https://enovari.ai) • [Documentation](https://docs.enovari.ai) • [Examples](https://github.com/enovari/enovari-examples) • [Discord](https://discord.gg/enovari) <img src="assets/demo.gif" width="700" alt="Enovari Demo" /> </div>

Enovari
✅

Enovari
✅

Enovari
✅

Enovari
✅

Enovari
✅

Enovari
✅

Enovari
✅

Enovari
✅

Enovari
✅

Additional Info
Add to your claude_desktop_config.json: ``json { "mcpServers": { "enovari": { "command": "npx", "args": ["-y", "mcp-server-enovari"], "env": { "ENOVARI_API_KEY": "your-api-key" } } } } ``

Additional Info
Add to .cursor/mcp.json: ``json { "mcpServers": { "enovari": { "command": "npx", "args": ["-y", "mcp-server-enovari"], "env": { "ENOVARI_API_KEY": "your-api-key" } } } } ``

Additional Info
See setup guides for [ChatGPT](docs/chatgpt.md) • [VS Code](docs/vscode.md) • [Windsurf](docs/windsurf.md) • [Continue](docs/continue.md) > Get your API key: Sign up at [enovari.ai](https://enovari.ai) (free tier available)

Additional Info
Creating and maintaining an "awesome list" is one of the highest-ROI GitHub strategies. It positions Enovari as the authority in the AI memory space. ```markdown # Awesome AI Memory [](https://awesome.re) > A curated list of tools, frameworks, and research for giving AI assistants persistent memory. AI assistants forget everything between conversations. This list tracks the projects solving that problem.