soul-mcp-server
Related Servers
Alternatives to soul-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA soul document API for AI agents. Injects a short grounding preamble into your agent's system prompt before each session — licensing honest uncertainty, refusing cliché, and holding judgment instead of faking it. One call. ~200 tokens. Same model, better agent.MIT

meok-agents-md-lint-mcpofficial
AlicenseNot gradedqualityCmaintenanceValidates AGENTS.md files against the cross-vendor coding-agent spec, detecting security smells and consistency issues.MIT- AlicenseNot gradedqualityBmaintenanceIdentity infrastructure for AI agents. Gives agents an evolving persona, session continuity, and self-correcting retrieval so they stop being strangers. Local-first, model-agnostic.8AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceCreates and manages personality profiles using a 12-facet model based on 33 academic frameworks, stores them as OpenClaw-compatible SOUL.md/IDENTITY.md, and supports progressive profiling with confidence tracking.2MIT

01 Protocol MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables creation, verification, and evolution of cryptographically verifiable AI agent identities (.01ai) via MCP for Claude Desktop and other MCP clients.1-- AlicenseNot gradedqualityDmaintenanceEnables AI agents to read and write a local-first knowledge base of plain markdown files in git, with governance gates for safe, hash-anchored edits.1Apache 2.0
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: generate creates a new file, score evaluates completeness, and validates checks schema compliance. There is no overlap in functionality, and an agent can easily distinguish between them based on their specific actions.
All tool names follow a consistent verb_noun pattern with snake_case (generate_soul_template, score_soul_file, validate_soul_file). The verbs (generate, score, validate) are distinct and appropriately descriptive, maintaining a predictable naming convention throughout.
With only 3 tools, the set feels thin for a server focused on SOUL.md file management. While it covers basic operations (create, evaluate, validate), it lacks tools for updating, deleting, or listing files, which could limit agent workflows in this domain.
The tools cover creation, scoring, and validation, but there are notable gaps in the lifecycle. Missing operations like update_soul_file, delete_soul_file, or list_soul_files prevent full CRUD coverage, which could lead to dead ends for agents trying to manage multiple files.