Skip to main content
Glama

marm-mcp

CONTRIBUTING.mdβ€’16.9 kB
# Join the MARM Community Welcome to MARM! If you're here, you've probably felt the frustration of AI that forgets your conversations, gives inconsistent responses, or just doesn't *get* what you're trying to build. You're not alone, and you're exactly who MARM was built for. MARM started as one person's solution to AI memory problems and has grown into a community of developers, researchers, and AI enthusiasts who believe we can build something better together. This isn't a corporate project with formal processes, it's a collaborative effort where every voice matters and every contribution counts. ## Table of Contents - [Why MARM Needs You](#-why-marm-needs-you) - [Ways to Get Involved](#-ways-to-get-involved) - [How We Work Together](#-how-we-work-together) - [Community Hall of Fame](#-community-hall-of-fame) - [Connect with the Creator](#-connect-with-the-creator) - [Ready to Join?](#-ready-to-join) - [Acknowledgments & Philosophy](#-acknowledgments--philosophy) - [Code of Conduct](#code-of-conduct) --- ## 🎯 Why MARM Needs You MARM is evolving from a memory protocol into the foundation of a larger AI ecosystem. We're building: - **Memory-augmented AI** that grows with users over time - **Professional testing infrastructure** for reliable AI development - **Modern glassmorphism interfaces** that feel like 2025, not 2010 - **Community-driven features** based on real user needs **Your perspective matters.** Whether you're debugging late-night coding sessions with ramen and coffee (like our hero image!) or building professional AI solutions, MARM grows stronger with every user who shares their experience. --- ## 🌟 Ways to Get Involved MARM is evolving from protocol to platform - here's where we need your help based on our strategic roadmap: ### **Protocol Testing & Validation** - **Cross-platform testing** - validate MARM across ChatGPT, Claude, Gemini, and other AI models - **Edge case discovery** - find where MARM breaks down and help us improve robustness - **Real-world workflows** - share how you're using `/log`, `/notebook`, and `/deep dive` in actual projects - **Performance benchmarking** - help us achieve sub-1-second response times ### **Advanced Protocol Development** - **MoreLogic Protocol** - contribute to our enhanced critical thinking & analysis framework - **HybridLogic Integration** - help build seamless switching between AI personalities - **Memory Architecture** - work on dual-RAG systems and self-updating knowledge bases - **Cross-protocol context** - ensure memory persists across different AI modes ### **Technical Infrastructure** - **Multi-AI provider support** - expand beyond Llama 4 to user choice across leading models - **n8n workflow integration** - automated session processing and memory updates - **MCP integration** - Model Context Protocol support for developer ecosystem - **Enterprise solutions** - team memory management and deployment options ### **Developer Ecosystem & Integrations** - **API development** - build SDKs and documentation for third-party applications - **Community tools** - VS Code extensions, browser tools, CLI utilities - **Integration examples** - boilerplate code and partnership opportunities - **Developer tutorials** - help others build with MARM's memory infrastructure ### **Platform & Community** - **Mobile development** - responsive design for all devices - **Community features** - collaborative spaces and knowledge sharing - **Content creation** - tutorials, videos, blog posts showcasing MARM capabilities - **"Used With MARM" showcase** - highlight community adaptations and integrations ### **Strategic Growth** - **Partnership opportunities** - connect MARM with complementary tools - **Enterprise user feedback** - help shape team and business use cases - **Community building** - grow us toward 1k+ GitHub stars - **Educational resources** - make MARM accessible to new users and developers --- ## 🀝 How We Work Together This project follows the philosophy: **"We need to work together, I am not a delegator, I'm here to work with you."** - **Direct communication** - no corporate speak, just honest feedback - **Ship first, optimize later** - we move fast and fix things as we go - **Surgical improvements** - targeted fixes over massive rewrites - **Community-driven** - real users solving real problems ### Forks, Spin-offs, and the Official MARM I welcome and encourage the community to fork this repository and experiment with the MARM protocol. Seeing new ideas and adaptations is one of the most exciting parts of open source. However, to avoid confusion and ensure users can always find the official source, I ask that you follow these simple guidelines: - **The MARM Name and Versioning:** The use of the **MARM name** and the official **version numbering** is reserved for releases from this repository. - **Derivative Works:** If you create a derivative work, please give it a new, unique name (like the excellent "MARMalade" project) and clearly state that it is an unofficial or experimental version of MARM. This approach allows the ecosystem to flourish while ensuring that the official MARM project remains a stable and reliable source of truth for the community. **Getting Started:** 1. **Star the repo** if MARM solves a problem for you 2. **Open an issue** with bugs, ideas, or questions 3. **Join discussions** - help other users and share your experience 4. **Submit PRs** - code improvements, docs, or new features **Communication:** - **GitHub Issues** - for bugs, features, and technical discussions - **GitHub Discussions** - for community questions and idea sharing - **Direct contact** - reach out to Lyell directly (links below) for collaboration ## πŸ† Community Hall of Fame **These amazing people helped shape MARM from the beginning.** Their feedback, ideas, and early support transformed MARM from a personal project into a community-driven AI memory framework. Every feature you see today was influenced by real user needs and suggestions. --- ### **Early Pioneers** #### u/CalamityThorazine & u/CrazyCrayfish **Community Champions** | [Reddit Thread – June 9, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/) Encouraged the move from temporary hosting (e.g., Google Drive) to GitHub, improving accessibility and trust. Their early interest helped validate public release and shaped the decision to publish the protocol in a permanent, versioned repository. **Impact:** Made MARM accessible to the wider community through proper GitHub hosting --- #### u/ophydian210 **Protocol Architect** | [GitHub: Ophy21](https://github.com/Ophy21) | [Reddit Thread – June 10, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/) Provided early-stage critique and refinement feedback on memory simulation, session labeling, and user experience logic. Influenced the removal of the confidence scoring system, the creation of the `/show reasoning` command, and improvements to session lifecycle documentation. **Impact:** Core protocol features like `/show reasoning` exist because of their feedback --- #### u/Deminimis_opsec **Technical Clarity Champion** | [Reddit Thread – June 10, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/) Provided critical technical feedback on MARM's limitations within non-API chat environments. Helped clarify the distinction between frontend prompt-layer protocols and backend memory architectures. Their input reinforced the importance of transparency around session scope, non-persistent memory, and the lack of backend execution in typical LLM interfaces. **Impact:** MARM's transparent limitations documentation exists because of their insight --- #### u/Angry_cactus **Cross-Platform Validator** | [Reddit Thread – June 11, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/) Tested MARM across models and validated its performance in Gemini Pro. Provided feedback on LLM pseudo-memory behaviors, reply weighting, and the trade-offs between short-form prompts and structured memory. Their observations reinforced the session-based design choice and influenced future patch direction focused on continuity fail safes and compression-aware prompting. **Impact:** Multi-model compatibility and session design principles shaped by their testing --- #### u/MykoJai168 **Vision Contributor** | Private DM – June 12, 2025 | (Referenced in [README.md](README.md)) Sparked the architectural concept behind MARM's "Session Relay Tools" patch by proposing a layered, context-managed memory model. Offered collaboration, stress-testing interest, and early insight into multi-agent recall, which helped validate MARM's patch direction. Credited for contributing to the prompt-layer vision and user-side continuity design. **Impact:** The foundation of MARM's memory architecture came from their collaborative vision --- ### u/LanaAugustine **Active Tester** | Private DM - August 29, 2025 This user has helped a lot even before MARM with actively testing and giving me feedback with the protocol that run MARM. Without active testers its harder to see the user side so thank you for your contribution to this project! **Impact** Valuable feedback that has helped shape the protocols I build --- ### **Core Contributors** #### Neurosyn Labs **Lightweight Memory Architect** | [GitHub: NeurosynLabs](https://github.com/NeurosynLabs) Created **MARMalade V-1.0** β€” A lightweight memory kernel for ChatGPT, built on MARM principles with structured persistence, sovereign reasoning, and token-efficient context retention. Their implementation demonstrates how MARM concepts can be adapted into focused, efficient memory solutions for specific AI platforms. **Impact:** Showed how MARM principles can be implemented as lightweight, specialized memory kernels --- #### Jefferson **Security, MCP & Desktop Platform Lead** | [GitHub: jeffersonwarrior](https://github.com/jeffersonwarrior) Rapidly built an extensive suite of additions including MCP, desktop version, OAuth wrapper, and comprehensive security infrastructure. Jefferson's contributions include: **Key Features:** - **API Key Management**: Secure /setupreplicate command system with localStorage storage and validation - **Security Hardening**: HTML injection prevention, XSS protection, URL validation with HTTPS enforcement - **Build & Testing**: Fixed critical Rust compilation errors, created comprehensive 89-test suite with 100% security coverage - **Desktop Application**: Full desktop integration with Tauri framework and security-first architecture **Security Impact:** - Prevents XSS attacks and HTML injection - Blocks cleartext HTTP and local file access attempts - Eliminates sensitive data exposure in console logging - Establishes regression testing for all security fixes **Impact:** Significantly enhanced MARM's security posture and expanded platform capabilities with desktop integration and comprehensive testing infrastructure --- #### u/sabhi12 **AI Memory Systems Analyst** | [Reddit: sabhi12](https://www.reddit.com/user/sabhi12) | Private DM - July 2025 Provided deep technical analysis of LLM memory limitations and validation of MARM's core architecture. Key contributions include identifying the distinction between real memory vs. simulated memory in current AI systems, strategic feedback on memory types (short-term, long-term, permanent), and advanced ChatGPT integration techniques. Their industry perspective helped validate MARM's market positioning and technical approach to solving enterprise-grade AI memory challenges. **Impact:** Strategic validation of MARM's memory architecture and identification of key market opportunities for AI memory intelligence --- ## πŸ“ž Connect with the Creator Ryan Lyell - MARM Creator & Lead Developer **Reach out for:** - Collaboration on MARM ecosystem expansion - Integration partnerships (MCP, mobile, enterprise) - Technical guidance and architectural discussions - Community building and growth initiatives **Contact:** - **Reddit:** [u/Alone-Biscotti6145](https://www.reddit.com/user/Alone-Biscotti6145) - **Professional Services:** [Fiverr Profile](https://www.fiverr.com/s/WEXLdBl) - **GitHub:** Direct messages welcome for project collaboration --- ## πŸš€ Ready to Join? Whether you're here to test, build, design, or just share ideas - **welcome to the MARM family!** Start by: 1. **Star the repo** to show your support 2. **Join GitHub Discussions** to connect with other users 3. **Open an issue** with any bugs, ideas, or questions 4. **Submit a PR** when you're ready to contribute code or docs ## πŸ’ Acknowledgments & Philosophy MARM was born from one person's frustration with AI memory problems but grew into something much bigger through community collaboration. Every feature, improvement, and design decision was shaped by real users sharing their experiences, testing edge cases, and believing that AI can be more reliable and transparent. **The MARM Way:** - **Community-driven development** - real users solving real problems - **Transparent about limitations** - no false promises or marketing fluff - **Ship first, optimize later** - move fast and fix things as we go - **"Surgical vs wide shot"** - precise improvements over massive rewrites - **AI-assisted development** - LLMs used extensively for drafting, testing, and learning Special thanks to the Reddit prompt engineering community for the early feedback, frustrations shared, and validation that MARM addresses real needs. The v2.0 testing infrastructure, glassmorphism UI, and 95% cost reduction through Llama 4 migration all happened because the community asked for better, faster, more reliable AI tools. --- ## Code of Conduct MARM is built on the principle of working together to solve real problems. Please follow these guidelines in all project interactions: - Be respectful and welcoming - Everyone was new to AI memory systems once - Stay collaborative - "We need to work together, I am not a delegator, I'm here to work with you" - Disagree constructively - When you disagree, help others understand your perspective - Embrace different viewpoints - Diverse experiences make MARM stronger for everyone This isn't a corporate project with formal processes - it's a community building better AI tools together. Every voice matters, every contribution counts. --- ## πŸ“ Project Documentation ### **Usage Guides** - **[MARM-HANDBOOK.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/MARM-HANDBOOK.md)** - Original MARM protocol handbook for chatbot usage - **[MCP-HANDBOOK.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/MCP-HANDBOOK.md)** - Complete MCP server usage guide with commands, workflows, and examples - **[PROTOCOL.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/PROTOCOL.md)** - Quick start commands and protocol reference - **[FAQ.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/FAQ.md)** - Answers to common questions about using MARM ### **MCP Server Installation** - **[INSTALL-DOCKER.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/INSTALL-DOCKER.md)** - Docker deployment (recommended) - **[INSTALL-WINDOWS.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/INSTALL-WINDOWS.md)** - Windows installation guide - **[INSTALL-LINUX.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/INSTALL-LINUX.md)** - Linux installation guide - **[INSTALL-PLATFORMS.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/INSTALL-PLATFORMS.md)** - Platfrom installtion guide ### **Chatbot Installation** - **[CHATBOT-SETUP.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/CHATBOT-SETUP.md)** - Web chatbot setup guide ### **Project Information** - **[README.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/README.md)** - This file - ecosystem overview and MCP server guide - **[CONTRIBUTING.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/CONTRIBUTING.md)** - How to contribute to MARM - **[DESCRIPTION.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/DESCRIPTION.md)** - Protocol purpose and vision overview - **[CHANGELOG.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/CHANGELOG.md)** - Version history and updates - **[ROADMAP.md](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/ROADMAP.md)** - Planned features and development roadmap - **[LICENSE](https://github.com/Lyellr88/MARM-Systems/blob/MARM-main/docs/LICENSE)** - MIT license terms

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lyellr88/marm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server