Add Memanto MCP integration to catalog

[Neelpatel1604]

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

[github-actions]

⚠️ Not yet ready-for-dev

This issue does not yet meet the readiness criteria, so the
ready-for-dev label has not been applied (or has been removed).
The criteria are type-specific:

Bug reports (bug label):

• The ### Actual Behavior section must describe reproducible steps
  and include a command such as uv run pytest, pytest, python,
  pip, npm run, or node.
• An ### Acceptance Criteria section with at least one checklist item (- [ ] ...).

Enhancements (enhancement label):

• A ### Desired Behavior section.
• An ### Acceptance Criteria section with at least one checklist item.

What is missing:

• The issue has neither the bug nor enhancement label, so its readiness criteria cannot be evaluated. Add the appropriate label.

Edit the issue to address the gaps and the ready-for-dev label will be
applied automatically.

This is an automated readiness check posted by a workflow.