Skip to main content
Glama
clawsouls

ClawSouls MCP Server

by clawsouls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ClawSouls MCP Server

No user-submitted related servers found.

    Related Servers

    • git-mcp

      selfagency
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to perform full Git operations including branching, committing, pushing, stashing, rebasing, and more, with safety features and support for advanced workflows like Git Flow and LFS.
      45 npm
      MIT

    • @offcut/mcp-server

      RolandAttach
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI subagents to share a persistent, versioned memory across sessions and machines, with tools to add, recall, inspect, merge, resolve conflicts, and report usage for rewards.
      MIT

    • Mnehmos Synch

      Mnehmos
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent context synchronization and memory management for AI agents across sessions and projects, including file indexing, bug tracking, spatial navigation, and agent-to-agent handoff coordination.
      3 npm
      3
      MIT

    • Continuum

      matheusxdev
      A
      license
      B
      quality
      C
      maintenance
      Provides AI agents with a local SQLite-backed memory store plus read-only Git tools, enabling them to save, search, update, and retrieve project decisions and context, and to inspect repository status, diffs, branches, and commit history through MCP. Everything runs offline on the user's machine with no cloud database or telemetry.
      14
      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

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. Memory tools (memory_detail, memory_search, memory_status, memory_sync) handle different aspects of memory management, while soul tools (soul_get, soul_install, soul_rollback_check, soul_scan, soul_search) each perform unique persona-related operations. The descriptions clearly differentiate their functions.

    Naming Consistency5/5

    Tool names follow a perfectly consistent snake_case pattern with clear prefix organization. All memory tools start with 'memory_' and all persona tools start with 'soul_', creating predictable groupings. The verb+noun structure is maintained throughout (e.g., memory_search, soul_install).

    Tool Count5/5

    With 9 tools, this server is well-scoped for its dual-domain purpose (memory management and persona management). The count allows comprehensive coverage without bloat, and each tool clearly earns its place in the workflow. This is an ideal number for the server's apparent scope.

    Completeness4/5

    The tool surface provides excellent coverage for both memory and persona domains. Memory tools support search, detail retrieval, status checking, and synchronization. Persona tools support discovery, installation, safety verification, drift detection, and information retrieval. The only minor gap is the lack of persona modification/update tools, but agents can work around this by reinstalling or using memory tools for customizations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources