Skip to main content
Glama

Related Servers

Alternatives to FoundersOS

  • A
    license
    Not graded
    quality
    C
    maintenance
    Persistent memory with semantic search for Claude and MCP-compatible clients, storing context that survives conversations and can be retrieved intelligently.
    1
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    A self-hosted MCP server that provides any LLM with a graph-backed memory layer of your life—tasks, email, finance, contacts, calendar—plus autonomous agent offices that act on your behalf.
    1
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server that exposes an in-browser AI ERP (CRM, stock, invoices, HR) with role-aware agents, enabling natural language chat and confirm-before-write actions.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    A self-hosted server providing shared memory, RAG document search, project maps, and role-based prompts for all AI agents via MCP and REST, enabling persistent context across devices and tools.
    2
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Self-hosted MCP server giving AI agents persistent memory for personalization and context across conversations.
    279
    Apache 2.0
  • A
    license
    Not graded
    quality
    A
    maintenance
    A local-first MCP server that gives AI clients a shared, user-owned memory and skills plane, enabling persistent memory across apps via the Model Context Protocol.
    MIT
  • F
    license
    B
    quality
    C
    maintenance
    A fully local, privacy-first MCP server that gives AI coding assistants deep repository intelligence with file-and-line-cited answers, persistent semantic memory, and agentic abilities like task planning and code review—all without any cloud API calls.
    23
    -

TDQS

B3.2/5.0

Scored across 102 tools

Disambiguation3/5

Most tools target distinct resources, but there is noticeable overlap among summary/orientation tools (get_session_start, get_dashboard, get_task_summary, get_financial_summary, get_feed_briefing) and between get_customer and get_entity_card. The detailed descriptions help an agent pick correctly, but with 102 tools the boundaries are not always obvious.

Naming Consistency3/5

The dominant verb_noun pattern (get_, list_, create_, update_, remove_) is readable, but creation verbs are split between add_ and create_ (add_customer vs create_task), and the memory_* group inverts the convention (memory_store, memory_recall). There are also standalone outliers like ping and checkpoint.

Tool Count1/5

102 tools is far beyond the typical MCP server surface and exceeds the 50+ extreme threshold, even for a six-domain OS. An agent must evaluate dozens of tools per session, making selection costly and error-prone; splitting into separate CRM, finance, feeds, and admin servers would be more appropriate.

Completeness4/5

The tool surface is remarkably comprehensive: full CRUD/lifecycle coverage across CRM, tasks, tags, playbooks, projects, members, feeds, and trash management, plus financial reporting and audit logs. Minor gaps exist such as no update_transaction/update_account/update_category and interactions being append-only, but most workflows can be completed or worked around.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive