Skip to main content
Glama
NORTHTEKDevs

GENOME MCP Server

by NORTHTEKDevs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to GENOME MCP Server

  • mem0-mcp by tensakulabs

    mem0-mcpofficial

    tensakulabs
    A
    license
    A
    quality
    C
    maintenance
    Self-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.
    6
    4
    MIT

Related Servers

  • Mnemo MCP by expandingideas-ai

    Mnemo MCPofficial

    expandingideas-ai
    A
    license
    Not graded
    quality
    B
    maintenance
    Persistent AI memory server with hybrid search and embedded sync. Enables AI agents to store, retrieve, and manage information across sessions with temporal knowledge graph support.
    MIT

  • Muninn

    wjohns989
    A
    license
    Not graded
    quality
    D
    maintenance
    A local-first persistent memory server that provides AI agents with deterministic, multimodal information retrieval across different sessions and projects. It enables long-term memory continuity using a 5-signal hybrid search engine and cognitive reasoning loops designed for complex development workflows.
    1
    Apache 2.0

  • MCP Memento

    x-hannibal
    A
    license
    A
    quality
    B
    maintenance
    A persistent long-term memory server for AI assistants that enables storing and recalling solutions, facts, and decisions with intelligent confidence tracking and relationship mapping. It allows developers to build a cross-platform knowledge base that integrates seamlessly with IDEs and CLI agents.
    17
    26 PyPI
    2
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool maps to a distinct memory operation: remember for storing, recall for searching, forget for deleting a single memory, and reset_memories for clearing an entire namespace. The overlap between forget and reset_memories is clearly scoped by singleness versus all-memories, so there is no real ambiguity.

Naming Consistency4/5

Three tools use simple lowercase verb forms (remember, recall, forget) and one uses verb_noun snake_case (reset_memories). The pattern is mostly consistent and intuitive, with only reset_memories deviating by including an object.

Tool Count5/5

Four tools is a well-scoped count for a memory server. Each tool covers a necessary operation without redundancy or bloat, making the set easy to navigate.

Completeness5/5

The core memory lifecycle is covered: store, read/search, delete one, and delete all. There is no explicit update operation, but for a semantic memory store treating memories as immutable facts this is not a meaningful gap.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources