Add OMEGA Memory integration

[singularityjason]

Agent Information

Integration Name: OMEGA Memory
Category: integrations/omega-memory
Specialty: Persistent, semantically searchable memory for AI coding agents via MCP

Summary

• Adds integrations/omega-memory/ with README, setup script, and a drop-in memory section template for any agent
• OMEGA is an open-source (Apache-2.0) MCP memory server available on PyPI and GitHub
• Provides semantic search with local embeddings, typed memories (decisions, lessons, errors, preferences), memory decay/consolidation, contradiction detection, and cross-session checkpoints
• Complements the existing mcp-memory integration by offering a concrete, installable backend with richer capabilities

What's Included

• README.md: What OMEGA does, installation, MCP client config, tool reference table, usage examples, and links
• setup.sh: Detects Python 3.11+, installs omega-memory via pip, checks for existing MCP client configs
• memory-section-template.md: Ready-to-paste prompt section that works with any agent in The Agency

Motivation

The existing mcp-memory integration is server-agnostic — it describes the pattern but doesn't provide an installable backend. OMEGA fills that gap with a pip install and a single MCP config entry. Agents get semantic search, typed storage, checkpoints, and cross-session continuity out of the box.

Testing

• Installed via pip install omega-memory and verified MCP server starts with python3.11 -m omega.server.mcp_server
• Tested with Claude Code as the MCP client
• setup.sh tested on macOS (zsh) and Linux (bash)

Checklist

• Follows integration directory structure (matches mcp-memory layout)
• README covers setup, configuration, tool reference, and usage
• setup.sh is executable and handles missing Python gracefully
• Memory section template is generic and works with any agent
• No vendor lock-in — open-source (Apache-2.0), free, runs locally
• Factual tone, no marketing language

[msitarzewski]

Thanks for a well-written PR — the code quality is high and OMEGA looks like a solid project.

However, we already have integrations/mcp-memory/ which is intentionally server-agnostic. Adding a separate top-level directory for a specific implementation crosses into vendor coupling territory — the README comparison table, OMEGA-specific API calls in the template, and pip install omega-memory in setup.sh make this feel more like a product install guide than a generic integration.

That said, the existing mcp-memory integration is a bit of a placeholder — it describes the pattern but doesn't point users to anything concrete. There's a real gap there that OMEGA could fill.

What we'd love instead: a PR that adds OMEGA as a recommended implementation within the existing integrations/mcp-memory/ integration:

• Add a "Recommended Implementations" section to integrations/mcp-memory/README.md with OMEGA as a listed option (brief description, link, install command)
• Optionally add an OMEGA-specific setup example or template as a file within mcp-memory/ (e.g., mcp-memory/omega-example.md)
• Keep the generic pattern as the primary guidance, with OMEGA as a concrete "if you want something that works out of the box" option
• Drop the comparison table — let the project speak for itself

This keeps the integration layer vendor-neutral while giving OMEGA real representation, and leaves room for other MCP memory servers to be listed alongside it in the future.

Happy to review a revised PR along these lines!