Skip to main content
Glama
DeathOVOGod

Agent Context Token Optimizer MCP Server

by DeathOVOGod

Related Servers

Alternatives to Agent Context Token Optimizer MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI memory persistence and secure credential management via vault tools for MCP-compatible clients like Claude Desktop, Cursor, and VS Code.
      12
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent, cross-tool memory layer for AI coding agents via MCP, enabling storage and retrieval of decisions, preferences, and context across different tools and models.
      1 npm
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      MCP-native persistent memory for AI agents. Stores and retrieves encrypted memories with Trust Quotient scoring, cross-agent handover protocol, and immutable audit trail. 13 tools. Remote endpoint available.
      13
      56 PyPI
      13
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to access a shared portable vault for memory, skills, and API credentials through MCP, so tools can store and retrieve memories, read versioned skill playbooks, and make server-side API calls without exposing secret keys.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent memory for AI agents via MCP, enabling agents to store and access notes, files, and session context across sessions and clients while under user control.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read, write, search, and manage persistent, decentralized context memory via a GCS-backed MCP server, with tools for document storage, retrieval, and STIM protocol nuggets.
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one stores text, the other reads a stored page. No overlap.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: store_tool_result and read_omitted_content.

    Tool Count3/5

    With only 2 tools, the server feels minimal but could be acceptable for a narrowly focused functionality. It is borderline.

    Completeness2/5

    Missing essential operations like deleting, updating, or listing stored content, which are needed for full lifecycle management.

    Maintenance

    ActivityStale
    ResponsivenessNo issues