Skip to main content
Glama
basemouse

BaseMouse

by basemouse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to BaseMouse

No user-submitted related servers found.

    Related Servers

    • memmd-mcp

      matamong
      A
      license
      B
      quality
      D
      maintenance
      A shared memory layer for AI agents — one memory.md synced across Claude Desktop, Cursor, Claude Code, OpenAI Codex, and any MCP client.
      4
      2
      MIT

    • agents-memory

      Lolaplex
      A
      license
      Not graded
      quality
      A
      maintenance
      A local markdown memory and cross-agent context engine for AI coding assistants. It provides an MCP server with tools to search, add, retrieve, and distill persistent memory across tools like Claude Code, Cursor, and Zed.
      63 PyPI
      5
      MIT
    • threadctx-mcp by threadctx-dev

      threadctx-mcpofficial

      threadctx-dev
      A
      license
      A
      quality
      B
      maintenance
      Shared memory MCP server for AI coding agents, enabling context sharing across sessions with local SQLite or cloud-based semantic search, compatible with Claude Code and Cursor.
      2
      32 npm
      1
      MIT

    • auxly-memory-cli

      Tzamun-Arabia-IT-Co
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
      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

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: search for retrieval, get_context_pack for structured output, and upsert_document for writing. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun (snake_case) pattern: search, get_context_pack, upsert_document. Naming is predictable and clear.

    Tool Count4/5

    With 3 tools, the set is minimal but covers core operations. It feels slightly under-scoped, but still reasonable for a focused workspace assistant.

    Completeness2/5

    Missing obvious operations like delete, list, or direct get_document. The domain of document management requires these for full CRUD; agents would struggle without deletion or listing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources