Skip to main content
Glama
toggle-workspace

toggle-brain MCP Server

by toggle-workspace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to toggle-brain MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-server-demo

      gandhips-Perry
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to connect to example tools, resources, and prompts over MCP, demonstrating integration with IDEs, chatbots, and agent frameworks.
      -

    • cerebro-mcp

      inematds
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a Markdown-based second brain as MCP tools, enabling MCP clients like Claude Code, Codex, Claude Desktop, n8n, and bots to read context, search notes, retrieve wiki pages, and optionally register decisions or sources.
      MIT

    • cortex

      Unchained-Labs
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted MCP server exposing a brain's tool registry (vault search, vault access, and connector tools) to MCP clients like Claude Code, scoped to the box owner.
      MIT

    • xtiandos

      bossayan9999
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to access xtiandOS's brain, memory, chat, message bus, shell, Docker, and artifact capabilities through tools, resources, prompts, roots, and sampling.
      -
    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

    D1.4/5.0

    Scored across 19 tools

    Disambiguation1/5

    Many tools have overlapping domains (e.g., multiple onboarding videos) and lack clear distinctions in descriptions. The path-like names and sparse descriptions make it impossible for an agent to reliably select the correct tool.

    Naming Consistency1/5

    Tool names follow no consistent pattern; they mix file paths, project prefixes, and arbitrary slugs. No verb_noun structure exists, and conventions vary wildly (e.g., clients_ vs tools_).

    Tool Count2/5

    19 tools is a moderate number, but the set is not scoped to a coherent domain. Many tools appear to be internal files (e.g., config files, video scripts) that do not form a purposeful tool surface.

    Completeness1/5

    The domain is entirely unclear, so completeness cannot be assessed meaningfully. The tools appear to be a random dump of files with no obvious operations, missing any semblance of CRUD or lifecycle coverage.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources