Enovari Integration Partnerships & Ecosystem Opportunities

6. Partnership Outreach Strategy

6.1 Partnership Tiers

Tier 1: Strategic Partners (Deep Integration)

• Target: Anthropic, OpenAI, Microsoft, Google
• Goal: Official ecosystem listing, co-marketing, API integration
• Approach: Formal partnership application, executive outreach
• Timeline: 3-6 months for partnership establishment
• Reality Check: These companies get thousands of partnership requests. Focus on making Enovari work perfectly with their products first, then apply to partner programs with usage data.

Tier 2: Technology Partners (Integration Partners)

• Target: AI agent frameworks, IDE makers, automation platforms
• Goal: Native integration, co-developed features
• Approach: Developer relations outreach, open-source contributions
• Timeline: 1-3 months per integration
• Best Approach: Build the integration first, then tell them about it. A working integration is 10x more persuasive than a proposal.

Tier 3: Community Partners (Cross-Promotion)

• Target: Other MCP server makers, AI tool creators, content creators
• Goal: Mutual promotion, joint content, shared communities
• Approach: Direct DM/email, GitHub engagement, community presence
• Timeline: 2-4 weeks per relationship
• Best Approach: Start by genuinely using and promoting their product. Then reach out with a specific cross-promotion idea.

6.2 Outreach Templates

Template A: MCP Directory Submission

Subject: Submit Enovari Memory Server to [Directory Name]
Hi [Directory Team],
I'd like to submit Enovari (https://enovari.ai) to your MCP server directory.
Enovari is an AI memory platform that provides persistent, portable, structured
memory for AI assistants across all platforms. It's an MCP server that works with
Claude, ChatGPT, Cursor, and any MCP-compatible client.
Key capabilities:
Persistent cross-session memory for AI
140+ built-in API integrations
Persona system for customized AI behavior
Hybrid BM25+vector memory search
Works with every major MCP client
Server details:
Name: ai.enovari/memory
Transport: [stdio/SSE/Streamable HTTP]
Package: @enovari/mcp-server on npm
Website: https://enovari.ai
GitHub: [link]
Would love to be listed. Happy to provide any additional information needed.
Best,
[Name]
Silicon Harbor / Enovari

Template B: Integration Partnership Proposal

Subject: Integration Partnership: Enovari Memory + [Partner Product]
Hi [Partner Name],
I'm reaching out from Enovari (https://enovari.ai) - we build persistent memory
for AI assistants via the Model Context Protocol (MCP).
I noticed that [Partner Product] is [specific observation about their product's
memory gap or potential benefit]. Enovari could complement your offering by
providing:
Persistent Memory: AI assistants using [Partner Product] would remember
   context across sessions automatically
Cross-Platform Portability: Memory from [Partner Product] carries over to
   any MCP-compatible client
Structured Knowledge: Not just raw chat history - organized, searchable,
   tagged memories
What an integration could look like:
[Specific technical integration point]
[User benefit example]
[Joint value proposition]
We currently support 140+ API integrations and work with Claude, ChatGPT, Cursor,
and every major MCP client.
Would you be open to a 20-minute call to explore a potential integration?
Best,
[Name]
Silicon Harbor / Enovari

Template C: Cross-Promotion with MCP Server Makers

Subject: Cross-promotion idea: Enovari Memory + [Their Server]
Hey [Name],
Love what you've built with [Their MCP Server]. We're building Enovari
(https://enovari.ai) - persistent memory for AI via MCP.
Our servers are super complementary: [Their server] does [X] and Enovari
remembers everything, so the AI can build on past interactions.
Some cross-promotion ideas:
Mention each other in our "Works great with" sections
Joint tutorial showing both servers working together
Share each other's content with our communities
Interested?
[Name]

Template D: Open-Source Contribution Introduction

Subject: [PR/Issue] Add Enovari as memory provider for [Framework]
Hi [Maintainer],
I've built an integration that adds Enovari (https://enovari.ai) as a
memory provider for [Framework]. Here's what it does:
Persistent cross-session memory via MCP
Drop-in replacement for [existing memory solution]
Hybrid BM25+vector search for fast, relevant recall
Works across platforms (memory in [Framework] is accessible from
  Claude, ChatGPT, Cursor, etc.)
I've submitted a PR at [link] with the integration code, tests, and
documentation.
Happy to iterate based on feedback. Let me know if you have any questions.
Best,
[Name]

6.3 Co-Marketing Proposals

6.4 Revenue Sharing Models

---

7. Solo Founder Partnership Playbook

7.1 Reality Check: Partnering Without Money or a Team

As a solo founder, traditional partnership approaches (business development teams, co-marketing budgets, enterprise sales cycles) are not available. Here is what actually works:

Your Biggest Assets:

• Speed: You can build integrations fast without corporate approval chains
• Authenticity: Founders talking to founders is more genuine than BD teams
• Technical depth: You understand the product better than anyone
• Flexibility: You can customize integrations quickly for partners

What to Offer When You Have No Money:

• Build the integration first. Don't ask for permission. Build a working integration with their product, then show it to them. This is 100x more effective than a partnership proposal email.
• Free cross-promotion. Offer to mention them in your docs, tutorials, and social media. This costs nothing and creates goodwill.
• Free tier access. Offer their team/users free access to Enovari. Usage data is more valuable than revenue at this stage.
• Joint content creation. Offer to write the blog post, create the tutorial, or record the video. Most companies want content but don't have time to create it.
• Open-source contributions. Contribute code to their repo. This builds trust and gives them something tangible.
• Bug reports and feedback. Genuinely use their product, report bugs, suggest improvements. Become a power user before asking for partnership.
• Community participation. Be active in their Discord/GitHub/forums. Help other users. Build reputation before asking for anything.

7.2 The Solo Founder Partnership Sequence

Follow this order for each target partner:

• Week 1-2: Use their product. Actually use it. Understand it deeply. Note pain points where memory would help.
• Week 2-3: Build the integration. Create a working demo of Enovari + their product. Document it.
• Week 3: Share publicly. Post the integration on Twitter, Dev.to, their community forum. Tag them but don't ask for anything.
• Week 4: Direct outreach. Send a short email/DM: "Hey, I built this integration. Here's a demo. Would love to get it listed in your docs/marketplace."
• Ongoing: Maintain and support. Keep the integration working. Respond to user issues. This builds trust for deeper partnership later.

7.3 Partnership Red Flags

Watch out for these warning signs when evaluating potential partnerships:

7.4 High-ROI Partnership Activities (Solo Founder Edition)

Rank by effort-to-impact ratio:

7.5 Solo Founder Time Management for Partnerships

With limited time, batch partnership work into focused sprints:

Sprint 1: Directory Blitz (1-2 days) Submit to every directory in one focused session. Prepare a standard description, logo, and screenshots beforehand. Copy-paste across all directories. Track in a spreadsheet with columns: Directory, URL, Submission Date, Status, Notes.

Sprint 2: GitHub PR Sprint (half day) Prepare PRs for both awesome-mcp-servers repos in one sitting. Write the one-line description once, format for both repo styles.

Sprint 3: Deeplink & Install Link Sprint (half day) Generate LM Studio deeplink, Replit install link, and any other one-click install URLs. Add "Add to [Client]" buttons to enovari.ai.

Sprint 4: Outreach Sprint (1-2 days) Send all partnership emails in one batch. Use the templates from Section 6.2. Personalize each one (takes 10-15 min per email). Send 5-10 emails per sprint. Do NOT follow up more than once -- if they are interested, they will reply.

Ongoing: 30-Minute Daily Ritual Spend 30 minutes per day on one of: (a) responding to partnership inquiries, (b) participating in MCP community forums, (c) helping users in partner product communities, (d) writing a short tutorial or social post.

7.6 Free Tools for Solo Founder Partnership Tracking

You do not need a CRM. Use these free tools:

7.7 What to Do When a Big Company Says Yes

If a Tier 1 or Tier 2 partner shows interest, here is how to not fumble it:

• Respond within 24 hours. Speed signals seriousness.
• Have a one-pager ready. A single page covering: what Enovari does, how the integration works, what is needed from them, timeline. Not a pitch deck -- a technical one-pager.
• Propose a specific next step. Not "let's chat sometime" but "Can we do a 20-minute call Thursday at 2pm? I'll show a working demo."
• Build a working prototype before the call. Even if rough, showing something working is 10x more persuasive than slides.
• Ask for one small thing. Not "make us your official memory partner." Instead: "Can we get listed in your docs/marketplace?" or "Can we do a joint tutorial?" Small wins compound.
• Get it in writing. Even informal agreements should be in an email thread. "Just to confirm, you'll add us to your extensions directory and we'll write the setup tutorial. Sound right?"
• Do not hire a lawyer for a cross-promotion. Save legal costs for actual revenue-sharing agreements. Most early partnerships are informal and do not need contracts.

---

8. Priority Action Items

Phase 1: Foundation (Weeks 1-4)

Phase 2: Expand Presence (Weeks 5-8)

Phase 3: Partnerships (Weeks 9-16)

Phase 4: Scale (Weeks 17+)

---

Appendix A: Complete MCP Client List (Verified Compatibility Targets)

Every client listed below supports MCP and is therefore a platform where Enovari should work. This list is sourced from the official MCP documentation at modelcontextprotocol.io/clients. Verified count: 108 clients (as of April 2026).

Note: The official page states: "This list is maintained by the community. If you notice any inaccuracies or would like to add or update information about MCP support in your application, please submit a pull request." The list grows regularly. To add a client, submit a PR at https://github.com/modelcontextprotocol/modelcontextprotocol/pulls.

Verification note (April 2026): The official modelcontextprotocol.io/clients page lists exactly 108 unique McpClient entries. This was verified by counting every component on the page source. All 108 entries in this table correspond 1:1 with the official listing. The count may increase over time as new clients are added regularly via pull requests to the modelcontextprotocol GitHub repo. The MCP features supported by each client were also verified against the official page during this fact-check.

---

Appendix B: MCP Registry Publishing Checklist

Pre-Publish:
[ ] Enovari MCP server code packaged for npm/PyPI
[ ] Package includes mcpName field (npm) or mcp-name comment (PyPI)
[ ] server.json created with mcp-publisher init
[ ] server.json reviewed and edited for accuracy
   - name: "ai.enovari/memory"
   - description: compelling, accurate
   - version: matches package version
   - packages: correct registry type, identifier, transport
   - environmentVariables: all required env vars documented
[ ] DNS TXT record or HTTP .well-known file set up at enovari.ai
   - Format: v=MCPv1; k=ed25519; p=
   - For DNS: enovari.ai. IN TXT "v=MCPv1; k=ed25519; p="
   - For HTTP: file at https://enovari.ai/.well-known/mcp-registry-auth
[ ] mcp-publisher CLI installed (brew install mcp-publisher or binary download)
[ ] Ed25519 (recommended) or ECDSA P-384 key pair generated
Publish Steps:
[ ] Package published to npm/PyPI (MCP Registry only hosts metadata, not code)
[ ] mcp-publisher login dns --domain "enovari.ai" --private-key ""
   (or: mcp-publisher login http --domain "enovari.ai" --private-key "")
   (or: mcp-publisher login github for io.github.enovari/* namespace)
[ ] mcp-publisher publish
[ ] Verified via: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.enovari/memory"
[ ] GitHub Actions set up for automated future publishes
   (see https://modelcontextprotocol.io/registry/github-actions)
Post-Publish:
[ ] Verify listing appears in registry API search results
[ ] Check downstream aggregators pick up listing (Glama, PulseMCP, etc.)
[ ] Monitor for any issues or moderation flags
[ ] Update server.json for each new version release
[ ] Monitor registry for competitor memory servers

---

Appendix C: Key URLs Reference

---

Appendix D: MCP Feature Glossary

Understanding what each MCP feature means helps prioritize which clients to target:

Activity	Description	Target Partners
Joint Blog Post	"Building AI Agents with Memory: [Partner] + Enovari"	Agent frameworks, IDEs
Tutorial Video	"How to add persistent memory to [Partner Product]"	IDEs, chat clients
Webinar	"The future of AI memory in [domain]"	Enterprise platforms
Case Study	"How [Customer] uses [Partner] + Enovari together"	All partners
Open Source Template	Starter project featuring both products	Frameworks, tools
Social Media Cross-Post	Share each other's launches and content	All partners
Conference Co-Presentation	Present together at AI/dev conferences	Strategic partners
Newsletter Feature	Feature in each other's newsletters	All partners
Model	Description	Best For
Affiliate/Referral	Partner earns % of signups they refer (15-25% of first year)	Content creators, community partners
Revenue Share	Split revenue on joint customers (20-30% to referrer)	Technology partners with large user bases
Bundling	Enovari included in partner's plan at wholesale rate	Enterprise platforms, IDE makers
White-Label	Partner resells Enovari under their brand	Large platforms wanting memory feature
Free Tier Integration	Enovari free tier for partner's users, premium upsell	High-volume partners for user acquisition
API Credits	Partner's users get Enovari API credits	Developer platforms
Red Flag	What It Means	What to Do
"Send us a detailed proposal and we'll review it"	They're not interested enough to have a conversation. Your proposal will go into a queue and die.	Send a 3-sentence email with a demo link instead. If they're interested, they'll respond.
"We need exclusivity"	They want to lock you in. Exclusivity with one partner limits all future options.	Never agree to exclusivity at this stage. Your value is that memory works everywhere.
"We'll promote you to our user base if you build X for free"	They want free development work with a vague promise of promotion.	Only build things that benefit your own users too. Ask for specific promotion commitments (newsletter mention on date X, blog post by date Y).
"Our legal team needs to review this"	Partnership will take 6+ months and you'll lose momentum. Normal for enterprises, red flag for startups.	Focus on partnerships that can happen informally first. Formalize later when there's real traction.
"Can you white-label this for us?"	They want your product without your brand. Can be lucrative long-term but kills brand building short-term.	Only consider if they have significant distribution and will drive real revenue. Otherwise, insist on co-branding.
Partner has no users / no traction	Partnership with a zero-user product gives zero distribution benefit.	Focus on partners who already have users. Even a small active user base (1,000+) is better than a large-sounding company with no traction.
They want you to pay to be listed	Some "partner programs" are just advertising schemes.	Legitimate marketplaces (Zapier, Make, etc.) are free to list on. Be skeptical of paid listings unless the platform has proven distribution.
They keep rescheduling or ghosting	They're not prioritizing this. You shouldn't either.	Send one follow-up. If still no response, move on. Come back when you have more traction.
Activity	Effort	Impact	Do First?
Submit to MCP Registry	Low (1-2 days)	Very High (feeds all aggregators)	YES
Submit PRs to awesome-mcp-servers repos	Low (1 hour each)	High (top search results)	YES
Submit to Smithery, Glama, MCP.so	Low (1-2 hours each)	Medium-High	YES
Create LM Studio deeplink	Low (30 min)	Medium	YES
Submit to goose extensions directory	Low (1-2 hours)	Medium-High	YES
Submit to Cursor Directory	Low (30 min)	High (large Cursor user base)	YES
Submit to all secondary directories (MCP Server Spot, mcpservers.com, etc.)	Low (2-3 hours total)	Low-Medium (SEO backlinks + discovery)	YES, batch it
Build n8n community node	Medium (2-3 days)	Medium-High (dev audience)	YES
Build Zapier integration	Medium-High (1-2 weeks)	High (6M+ users)	After launch
Contact Cline/Roo Code for recommendation	Low (1 email + demo)	Medium	After launch
Build LangChain memory provider	Medium (1 week)	High (massive dev audience)	After launch
Apply to Anthropic/OpenAI partner programs	Low (1 application)	Variable (may take months)	Send it, don't wait on it
Joint blog posts with MCP server makers	Medium (1-2 days per post)	Medium	After establishing relationships
Conference presentations	High (travel, prep, time)	Medium-Low for a solo founder	Skip for now
Tool	Purpose	Cost
GitHub Issues (private repo)	Track partnership status per target	Free
Google Sheets	Directory submission tracker, partnership pipeline	Free
Notion (free tier)	Partnership database with status, contact info, notes	Free
GitHub Projects	Kanban board for partnership phases	Free
Email labels/folders	Organize partnership correspondence	Free
#	Action	Owner	Priority	Status
1	Publish to Official MCP Registry -- Generate Ed25519 key pair, add DNS TXT record to enovari.ai, register ai.enovari namespace	Dev	CRITICAL	TODO
2	Publish @enovari/mcp-server npm package with mcpName: "ai.enovari/memory"	Dev	CRITICAL	TODO
3	Publish enovari PyPI package with in README	Dev	HIGH	TODO
4	Submit PR to punkpeye/awesome-mcp-servers	Marketing	HIGH	TODO
5	Submit PR to wong2/awesome-mcp-servers	Marketing	HIGH	TODO
6	Submit to Glama MCP Server Directory	Marketing	HIGH	TODO
7	Submit to Smithery registry	Marketing	HIGH	TODO
8	Submit to MCP.so	Marketing	HIGH	TODO
9	Submit to Cursor Directory	Marketing	HIGH	TODO
10	Create OpenAPI/Swagger spec for Enovari API	Dev	HIGH	TODO
11	Set up DNS TXT record for MCP Registry auth on enovari.ai (or HTTP auth at .well-known/mcp-registry-auth)	Dev	CRITICAL	TODO
#	Action	Owner	Priority	Status
12	Submit to MCPHub, MCPBundles, MCPGallery, PulseMCP, MCP Server Spot, mcpservers.com, MCP Server Finder, mcpservers.org, AI Agents List, MCP Market	Marketing	MEDIUM	TODO
13	Create Postman Collection and publish to API Network	Dev	HIGH	TODO
14	List on RapidAPI	Marketing	MEDIUM	TODO
15	Create setup guides for Cursor, Windsurf, VS Code Copilot, JetBrains	Docs	HIGH	TODO
16	Contact Chatbox, Simtheory, Kilo Code for marketplace listing	Marketing	HIGH	TODO
17	Contact goose extensions directory for listing	Marketing	HIGH	TODO
18	Contact Jenova for pre-integration	Marketing	HIGH	TODO
19	Apply to Anthropic partner program	BD	HIGH	TODO
20	Ensure Enovari works with ChatGPT MCP connections (OAuth/DCR)	Dev	HIGH	TODO
21	Launch on Product Hunt	Marketing	HIGH	TODO
22	Post Show HN on Hacker News	Marketing	HIGH	TODO
23	Create LM Studio deeplink for one-click install	Dev	MEDIUM	TODO
24	Submit to Vercel Marketplace for v0 integration	Marketing	MEDIUM	TODO
25	Test with MCPJam Inspector for ChatGPT app compatibility	Dev	MEDIUM	TODO
#	Action	Owner	Priority	Status
26	Build Zapier integration	Dev	HIGH	TODO
27	Build Make.com integration	Dev	HIGH	TODO
28	Build n8n community node (n8n-nodes-enovari)	Dev	MEDIUM	TODO
29	Contact CrewAI for integration partnership	BD	HIGH	TODO
30	Contact LangChain for memory provider listing	BD	HIGH	TODO
31	Build LangChain memory provider (EnovariMemory class)	Dev	HIGH	TODO
32	Contact BeeAI, Swarms, fast-agent frameworks	BD	MEDIUM	TODO
33	Contact Microsoft re: Copilot Studio integration	BD	MEDIUM	TODO
34	Create joint content with 3+ complementary MCP servers	Marketing	MEDIUM	TODO
35	Apply to OpenAI partner program	BD	MEDIUM	TODO
36	Build Pipedream integration	Dev	MEDIUM	TODO
#	Action	Owner	Priority	Status
37	Launch affiliate/referral program	BD	MEDIUM	TODO
38	Explore white-label opportunities with enterprise platforms	BD	MEDIUM	TODO
39	Build Power Automate custom connector	Dev	LOW	TODO
40	Create .NET and Rust client libraries	Dev	LOW	TODO
41	Establish presence at AI developer conferences	Marketing	MEDIUM	TODO
42	Launch developer ambassador program	Marketing	LOW	TODO
43	Build Semantic Kernel memory connector (NuGet)	Dev	LOW	TODO
44	Contact mobile MCP clients (Jenova, Joey, systemprompt) for featuring	Marketing	MEDIUM	TODO
45	Explore Salesforce AppExchange listing	BD	LOW	TODO
#	Client	Type	Key MCP Features
1	5ire	Desktop AI assistant	Tools
2	AgentAI	Rust AI agent library	Tools
3	AgenticFlow	No-code AI platform	Resources, Prompts, Tools, Discovery
4	AIQL TUUI	Desktop AI chat	Resources, Prompts, Tools, Discovery, Sampling, Elicitation
5	Amazon Q CLI	Terminal coding assistant	Prompts, Tools
6	Amazon Q IDE	IDE coding assistant	Tools
7	Amp (Sourcegraph)	Agentic coding tool (VS Code, JetBrains, Neovim, CLI)	Resources, Prompts, Tools, Sampling
8	Apidog	API testing platform	Resources, Prompts, Tools
9	Apify MCP Tester	MCP testing tool	Tools, Discovery
10	Apigene MCP Client	Multi-LLM AI interface	Tools, Resources, Discovery
11	Augment Code	AI coding platform (VS Code, JetBrains)	Tools
12	Avatar Shell	Electron-based MCP client	Resources, Tools
13	BeeAI Framework	Agent framework (IBM-backed)	Tools
14	BoltAI	Desktop AI client (Mac, iOS)	Tools
15	Call Chirp	Business call AI (Zoom, Google Meet)	Prompts, Tools
16	Chatbox	Desktop AI client (37K+ GitHub stars)	Tools
17	ChatFrame	Desktop chatbot (Mac, Windows)	Tools
18	ChatGPT	OpenAI assistant	Tools, Apps, DCR
19	ChatWise	Desktop AI client	Tools
20	Chorus	Mac AI app	Tools
21	Claude Code	Anthropic coding agent	Resources, Prompts, Tools, Roots, Elicitation, Instructions, Discovery, DCR
22	Claude Desktop App	Anthropic desktop	Resources, Prompts, Tools, Roots, Apps, DCR
23	Claude.ai	Anthropic web	Resources, Prompts, Tools, Apps, CIMD, DCR
24	Cline	VS Code coding agent (~50K GitHub stars)	Resources, Tools, Discovery
25	CodeGPT	IDE extension (VS Code, JetBrains)	Tools
26	Codex (OpenAI)	Terminal coding agent (also VS Code)	Resources, Tools, Elicitation
27	Continue	Open-source AI code assistant (VS Code, JetBrains)	Resources, Prompts, Tools, Apps
28	Copilot-MCP	AI coding via MCP	Resources, Tools
29	Cursor	AI code editor	Prompts, Tools, Roots, Elicitation, DCR
30	Daydreams	Onchain agent framework	Resources, Prompts, Tools
31	ECA (Editor Code Assistant)	Editor-agnostic AI coding	Resources, Prompts, Tools, Roots
32	Emacs Mcp	Emacs MCP client	Tools
33	fast-agent	Python agent framework	Resources, Prompts, Tools, Discovery, Sampling, Roots, Elicitation, Instructions
34	Firebender	IntelliJ plugin	Tools
35	FlowDown	Desktop AI client (privacy-focused)	Tools
36	FLUJO	Workflow builder + AI	Tools
37	Gemini CLI	Google terminal agent	Prompts, Tools, Instructions, DCR
38	GenAIScript (Microsoft)	JavaScript prompt toolbox	Resources, Tools
39	Genkit (Firebase)	GenAI SDK	Resources (partial), Prompts, Tools
40	GitHub Copilot coding agent	GitHub AI agent	Tools, DCR
41	Glama	AI workspace + MCP server/tool directory	Discovery, Elicitation, Instructions, Prompts, Resources, Sampling, Tasks, Tools
42	goose (Block)	Open-source AI agent	Apps, DCR, Discovery, Elicitation, Instructions, Prompts, Resources, Roots, Sampling, Tools
43	gptme	Terminal AI assistant	Tools
44	HyperAgent	AI-powered Playwright	Tools
45	Inspector	Visual code editor	Tools, Prompts, Resources, DCR
46	Jenova	Mobile MCP client (iOS, Android)	Tools, Discovery
47	JetBrains AI Assistant	JetBrains plugin	Tools
48	JetBrains Junie	JetBrains agent	Tools
49	Joey	Mobile MCP client (iOS, Android, macOS, Windows, Linux)	Prompts, Tools, Sampling, Elicitation, Apps
50	Kilo Code	VS Code AI dev team	Resources, Tools, Discovery
51	Klavis AI	Slack/Discord/Web MCP bridge	Resources, Tools
52	Langdock	Enterprise AI	Tools
53	Langflow	Visual AI builder	Tools
54	LibreChat	Open-source AI chat	Tools, Instructions, DCR
55	LM Studio	Local AI models	Tools
56	LM-Kit.NET	.NET AI SDK	Tools
57	Lutra	AI workflow agent	Resources, Prompts, Tools
58	MCP Bundler	MCP management app (macOS)	Resources, Prompts, Tools
59	MCPBundles	Browser MCP client + Studio	Resources, Prompts, Tools, Discovery
60	mcp-agent	Composable agent framework	Resources, Prompts, Tools, Sampling (partial), Roots, Elicitation
61	mcp-client-chatbot	Next.js chatbot	Tools
62	mcp-use	Python LLM-MCP connector	Resources, Prompts, Tools, Discovery, Sampling, Elicitation
63	mcpc	Universal CLI client (Apify)	Resources, Prompts, Tools, Discovery, Instructions
64	MCPHub (Neovim)	Neovim plugin	Resources, Prompts, Tools
65	MCPJam	Dev client for ChatGPT apps	Resources, Prompts, Tools, Elicitation, Instructions, Tasks, Apps, CIMD, DCR
66	MCPOmni-Connect	CLI MCP client	Resources, Prompts, Tools, Sampling
67	Memex	MCP client + server builder	Resources, Prompts, Tools
68	Memgraph Lab	Graph database tool	Resources, Prompts, Tools, Sampling, Elicitation, Instructions
69	Microsoft Copilot Studio	Enterprise AI builder	Resources, Tools, Discovery
70	MindPal	No-code AI agent builder	Tools
71	Mistral AI: Le Chat	Mistral assistant	Tools
72	modelcontextchat.com	Web MCP client	Tools
73	MooPoint	Web AI chat	Tools, Sampling
74	Msty Studio	AI productivity platform	Tools
75	Needle	RAG workflow platform	Resources, Prompts, Tools, Discovery
76	NVIDIA AIQ Toolkit	Enterprise agent toolkit	Tools
77	opencode	AI coding agent (terminal, desktop, IDE)	Resources, Prompts, Tools
78	OpenSumi	AI IDE framework	Tools
79	oterm	Terminal Ollama client	Prompts, Tools, Sampling
80	Postman	API platform (30M+ users)	Resources, Prompts, Tools, Discovery, Sampling, Elicitation, Apps
81	Proxyman	HTTP debugger (macOS)	Tools
82	RecurseChat	Desktop AI client	Tools
83	Replit Agent	AI development tool	Tools, DCR
84	Roo Code	AI coding assistant	Resources, Tools
85	rtrvr.ai	Chrome AI agent	Tools
86	Shortwave	AI email client	Tools
87	Simtheory	AI workspace	Resources, Prompts, Tools, Discovery
88	Slack MCP Client	Slack-MCP bridge	Tools
89	Smithery Playground	MCP testing tool	Resources, Prompts, Tools
90	SpinAI	TypeScript agent framework	Tools
91	Superinterface	In-app AI infrastructure	Tools
92	Superjoin	Google Sheets AI	Tools
93	Swarms	Multi-agent orchestration	Tools, Discovery
94	systemprompt	Mobile MCP app (iOS, Android)	Resources, Prompts, Tools, Sampling
95	Tambo	React chat platform	Prompts, Tools, Discovery, Sampling, Elicitation
96	Tencent CloudBase AI DevKit	Agent builder	Tools
97	TheiaAI / Theia IDE	Open IDE framework (Eclipse Foundation)	Tools
98	Tome	Desktop LLM client	Tools
99	TypingMind	LLM frontend	Tools
100	v0 (Vercel)	AI app builder	Tools
101	VS Code GitHub Copilot	Microsoft IDE	Resources, Prompts, Tools, Discovery, Sampling, Roots, Elicitation, Instructions, Apps, CIMD, DCR
102	VT Code	Terminal coding agent	Resources, Prompts, Tools, Discovery, Sampling (partial), Roots, Elicitation
103	Warp	Intelligent terminal	Resources, Tools, Discovery
104	WhatsMCP	WhatsApp MCP client	Tools
105	Windsurf Editor (Codeium)	Agentic IDE	Tools, Discovery
106	Witsy	Desktop AI assistant	Tools
107	Zed	Code editor	Prompts, Tools
108	Zencoder	VS Code/JetBrains agent	Tools
Resource	URL
Enovari	https://enovari.ai
MCP Official Site	https://modelcontextprotocol.io
MCP Clients List	https://modelcontextprotocol.io/clients
MCP Registry	https://registry.modelcontextprotocol.io
MCP Registry Docs	https://modelcontextprotocol.io/registry
MCP Registry Quickstart	https://modelcontextprotocol.io/registry/quickstart
MCP Registry Auth	https://modelcontextprotocol.io/registry/authentication
MCP Registry Package Types	https://modelcontextprotocol.io/registry/package-types
MCP Registry Aggregators	https://modelcontextprotocol.io/registry/registry-aggregators
MCP Registry Remote Servers	https://modelcontextprotocol.io/registry/remote-servers
MCP Registry GitHub Actions	https://modelcontextprotocol.io/registry/github-actions
MCP Registry Moderation Policy	https://modelcontextprotocol.io/registry/moderation-policy
MCP Registry OpenAPI Spec	https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/api/openapi.yaml
MCP Registry server.json Schema	https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/server-json/server.schema.json
MCP Publisher CLI Releases	https://github.com/modelcontextprotocol/registry/releases
MCP GitHub (submit client PRs)	https://github.com/modelcontextprotocol/modelcontextprotocol/pulls
MCP Python SDK	https://github.com/modelcontextprotocol/python-sdk
MCP TypeScript SDK	https://github.com/modelcontextprotocol/typescript-sdk
MCP Server Spot	https://www.mcpserverspot.com/servers
MCP Servers (mcpservers.com)	https://mcpservers.com
MCP Server Finder	https://www.mcpserverfinder.com
mcpservers.org	https://mcpservers.org
AI Agents List MCP Directory	https://aiagentslist.com/mcp-servers
MCP Market	https://mcpmarket.com
Cursor Directory Submission	https://cursor.directory/plugins/new
Smithery CLI Docs	https://smithery.ai/docs/build
Zapier Developer Platform	https://zapier.com/developer-platform/integrations
Make.com Partner Program	https://www.make.com/en/become-a-partner
Make Developer Hub	https://developers.make.com/custom-apps-documentation
n8n Community Nodes	https://docs.n8n.io/integrations/community-nodes/build-community-nodes/
n8n Submit Community Nodes	https://docs.n8n.io/integrations/creating-nodes/deploy/submit-community-nodes/
Pipedream Contributing	https://pipedream.com/docs/components/contributing
Pipedream Component Guidelines	https://pipedream.com/docs/components/guidelines
Activepieces GitHub	https://github.com/activepieces/activepieces
goose MCP Servers Discussion	https://github.com/block/goose/discussions/2075
LM Studio MCP Deeplinks	https://lmstudio.ai/docs/app/mcp/deeplink
Replit MCP Install Links	https://docs.replit.com/replitai/mcp/install-links
Feature	What It Means	Why It Matters for Enovari
Resources	Server-exposed data and content (like files, database entries)	Enovari can expose memories as browsable resources
Prompts	Pre-defined templates for LLM interactions	Enovari can provide prompt templates like "Recall context about [topic]"
Tools	Executable functions that LLMs can invoke	Core feature -- every client supports this. Enovari's write/read/search/update tools.
Discovery	Support for tools/prompts/resources changed notifications	Client auto-discovers new Enovari capabilities as they're added
Instructions	Server-provided guidance for LLMs	Enovari can instruct the LLM on how to use memory effectively
Sampling	Server-initiated LLM completions	Enovari could generate memory summaries using the LLM
Roots	Filesystem boundary definitions	Less relevant for Enovari (cloud-based memory)
Elicitation	User information requests (server asks user for input)	Enovari can ask "What domain should I store this under?"
CIMD	Client ID Metadata Document support	OAuth/auth standardization
DCR	Dynamic Client Registration support	Required for remote MCP servers connecting to ChatGPT, Claude.ai
Tasks	Long-running operation tracking	Useful for bulk memory operations
Apps	Interactive HTML interfaces	Enovari could render a memory dashboard as an MCP App

---

Appendix E: Smithery Publishing Checklist

Smithery is one of the largest MCP directories (6,000+ servers as of March 2026) and offers analytics, so it deserves its own checklist.

Pre-Publish:
[ ] Enovari MCP server deployed and accessible via Streamable HTTP
[ ] Smithery API key generated (sign up at smithery.ai)
[ ] Smithery CLI installed: npm install -g @smithery/cli
[ ] README is thorough (Smithery indexes it for the listing page)
Publish Steps:
[ ] Run: smithery mcp publish  -n enovari/memory
[ ] Verify listing appears at smithery.ai
[ ] Test server via Smithery Playground
[ ] Verify analytics are tracking (tool calls, usage patterns)
Post-Publish:
[ ] Monitor analytics in Smithery dashboard
[ ] Respond to any issues reported via Smithery
[ ] Update listing when server capabilities change
[ ] Note: Smithery auto-generates auth modals for servers requiring config/API keys

---

Appendix F: Quick Reference -- Where to Submit (Sorted by Effort)

For fast execution, here is every submission target sorted by effort level:

5 Minutes Each (just fill a form):

• MCP.so -- click Submit button on mcp.so
• MCP Server Spot -- Submit Server on mcpserverspot.com
• mcpservers.com -- submit on website
• MCP Server Finder -- submit on mcpserverfinder.com
• mcpservers.org -- submit on website
• AI Agents List -- submit on aiagentslist.com
• MCP Market -- submit on mcpmarket.com
• MCP Hub -- submit on mcphub.io
• MCP Gallery -- submit on mcpgallery.com

30 Minutes Each (structured submission):

• Cursor Directory -- submit at cursor.directory/plugins/new
• LM Studio deeplink -- generate at lmstudio.ai/docs/app/mcp/deeplink
• goose extensions -- post in github.com/block/goose/discussions/2075

1-2 Hours Each (GitHub PR or CLI publish):

• Awesome MCP Servers (punkpeye) -- PR to github.com/punkpeye/awesome-mcp-servers
• Awesome MCP Servers (wong2) -- PR to github.com/wong2/awesome-mcp-servers
• Smithery -- publish via CLI: smithery mcp publish -n enovari/memory
• Glama -- submit via site or wait for MCP Registry auto-pull

1-2 Days (requires package publishing + config):

• Official MCP Registry -- publish npm package, set up DNS auth, run mcp-publisher CLI

1-2 Weeks (requires building an integration):

• Zapier -- build via Platform CLI or Visual Builder
• Make.com -- build via Apps Editor, submit for review
• n8n -- scaffold via npm create @n8n/node, publish to npm
• Pipedream -- fork repo, create components, submit PR
• Activepieces -- build Piece in TypeScript, submit PR