Add Memanto MCP integration to catalog

Problem or Use Case

Memanto provides persistent semantic memory for agents over MCP (remember, recall, answer, etc.), but it is not listed in OpenHands/extensions, so Agent Canvas cannot show an install card on /mcp like Tavily or Kagi.

Official MCP documentation (source of truth for server name, env vars, and tools):
https://docs.memanto.ai/integrations/mcp

Desired Behavior

Add a catalog entry aligned with other stdio API-key MCP integrations (e.g. Tavily, Kagi):

• Package: memanto-mcp via uvx (per docs above)
• Required env: MOORCHEH_API_KEY
• Optional env: MEMANTO_DEFAULT_AGENT_ID
• docsUrl in catalog: https://docs.memanto.ai/integrations/mcp

Regenerate integrations/catalog-index.js with npm run build:integrations.

This is an opt-in MCP backend; it does not replace OpenHands built-in file memory.

Acceptance Criteria

• integrations/catalog/memanto.json validates against integrations/catalog.schema.json
• npm run build:integrations succeeds
• getIntegrationCatalogEntry("memanto") (JS) / get_integration_catalog_entry_model("memanto") (Python) returns the entry with stdio uvx + memanto-mcp and env fields from the Memanto MCP docs
• Memanto appears in MCP-filtered catalog listings (listIntegrationCatalog({ mcp: true }) / list_integration_catalog_models(mcp=True))

References

• Memanto MCP: https://docs.memanto.ai/integrations/mcp
• Memanto GitHub: https://github.com/moorcheh-ai/memanto

Review integrations/catalog.schema.json and nearby stdio API-key entries, then inspect the catalog lookup entry points named in the acceptance criteria. Add the Memanto catalog data from the linked MCP documentation and run npm run build:integrations. Done means the generated integrations/catalog-index.js builds and both JavaScript and Python catalog lookups include the entry in MCP-filtered results.