TinyAssets
Related Servers
Alternatives to TinyAssets
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceGoal-oriented narrative state machine for AI agents, exposing live world/scene context as MCP tools and resources.-
- AlicenseAqualityCmaintenanceEnables AI assistants to manage goals, tasks, weekly schedules, time tracking, reports, notes, and journal entries on a GoalSlot account through MCP tools.18MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP apps to manage durable, model-defined goal phases with persistent state, checkpointed progress, and safe resumption after interruptions or lost turns, ensuring elapsed time never implies completed business work.MIT
- AlicenseNot gradedqualityBmaintenanceExposes the Nodus orchestration runtime as MCP tools for memory management, goal/workflow execution, and sandboxed code execution.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.92MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI agents to branch, score, prune, and merge conversation strands with provenance and timeline export. Provides MCP tools and resources for managing parallel exploratory strands.-
TDQS
Scored across 12 tools
Most tools are clearly distinct, but get_status, get_review_state, and get_progress all report overlapping data such as word count, phase, and progress. The descriptions help somewhat, but an agent could plausibly select the wrong one when checking daemon state.
The set mostly follows a clear verb_noun snake_case pattern like add_note, get_premise, get_progress, and add_canon. The pause and resume verbs break the noun-object pattern slightly, giving a minor inconsistency rather than a serious one.
Twelve tools is a well-scoped size for a story-daemon management server. Each tool has a defined role in reading state, steering the story, or controlling execution, and none feel purely redundant.
Core workflows are covered: orient via status, read progress/chapters, steer via notes, add worldbuilding canon, and pause/resume the daemon. Minor gaps exist, such as no way to list or remove notes/canon, but the primary interaction model is still workable.