silly-tavern-mcp
Related Servers
Alternatives to silly-tavern-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for managing and playing a running SillyTavern instance, enabling AI coding assistants to read/write character cards, worldbooks, and chats, and to interact as a player via the full generation pipeline.32MIT
- FlicenseNot gradedqualityCmaintenanceEnables external CLI agents to directly operate TauriTavern via MCP, including reading runtime data, executing STScript, sending messages, switching characters, and running JavaScript diagnostics in iframes.1-
- AlicenseAqualityCmaintenanceEnables AI assistants to inspect, create, modify, and manage FiveM/RedM server resources, configuration, backups, and live runtime actions through a secure MCP interface.12MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, browse, inspect, download, convert, and manage manga albums, chapters, comments, favorites, account sessions, runtime configuration, and asynchronous download tasks through standardized MCP tools and resources.-
- FlicenseNot gradedqualityCmaintenanceEnables AI clients like Claude and ChatGPT to generate images and videos, animate images, create lip-synced videos, list TTS voices, and manage media via remote MCP tools.-
- AlicenseNot gradedqualityBmaintenanceEnables users to generate music, manage LoRAs, recordings, and studio workflows through MCP tools.MIT
TDQS
Scored across 60 tools
Most tools are namespaced by concrete resource and action, but generic st.resource.read and st.resource.patch overlap with the many typed list/inspect/configure/patch tools, and st.doctor, st.bridge.health, and st.runtime.control all touch runtime status. The descriptions help clarify intent, but at 60 tools there are still several near-boundary choices an agent must disambiguate.
The dominant st.<domain>.<action> convention is consistent and readable, with clear verb choices like list, inspect, read, write, patch, configure, and registry. A few names such as st.doctor, st.config_locations, st.snapshot, and st.plan_change break the pattern, and some tools differ in granularity, but the overall naming system is still predictable.
60 tools is far above the typical well-scoped 3-15 tool surface and falls explicitly in the 50+ extreme range. Even though the tools are organized across SillyTavern subdomains, the sheer count will burden model selection and make the tool surface hard to navigate efficiently.
The server covers nearly every major SillyTavern subsystem: characters, worldbooks, chats, config, extensions, plugins, MVU, regex, variables, quick replies, snapshots, and runtime control. The main gaps are lifecycle operations such as explicit character creation/deletion and chat creation/deletion, but the rest of the surface is unusually comprehensive.