Skip to main content
Glama
cogniahq

@cogniahq/mcp

Official
by cogniahq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @cogniahq/mcp

No user-submitted related servers found.

    Related Servers

    • Cairn

      johnmontejano
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI tools to query a user's private, locally stored memories (notes, documents) with source citations, using the MCP protocol.
      10 npm
      MIT

    • Knowledge MCP

      chanthr
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes your Google Drive, Slack, GitHub, and Railway to MCP clients with semantic search, per-user permissions, and optional OAuth, allowing natural-language access to your private data and infrastructure.
      11 npm
      MIT

    • memory-bridge

      jiabaobei
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides MCP tools for AI assistants to add, search, and preload semantic memories that synchronize across devices via encrypted delta sync, enabling seamless cross-device continuity with privacy controls.
      90
      MIT

    • Menhir

      Archolith
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides coding agents with governed semantic memory and code-graph context via MCP, enabling code-linked recall, blast-radius impact analysis, and lifecycle-aware memory management.
      3
      Apache 2.0

    • jalipata-mcp-memory

      alfianyusufabdullah
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, multi-tenant knowledge graph memory for MCP-capable AI tools, allowing them to recall and store entities, observations, and relations across sessions with keyword search.
      10
      33 npm
      3
      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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: action planning vs execution, and memory retrieval via different methods (get by ID, list chronologically, search semantically). No overlap.

    Naming Consistency4/5

    All tools share the 'cognia_' prefix, but naming patterns vary: two use 'domain_verb' (action_execute, action_plan), two use 'verb_noun' (get_memory, list_memories), and one uses just a verb (cognia_search). Also singular/plural inconsistency (memory vs memories).

    Tool Count5/5

    With 5 tools covering two distinct domains (actions and memories), the count is well-scoped and not overwhelming or too sparse.

    Completeness3/5

    The actions domain covers plan and execute but lacks listing, updating, or canceling actions. The memory domain allows reading (get, list, search) but no create, update, or delete operations, leaving notable gaps for a full lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources