SillyTavern-MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SillyTavern-MCPAdd a new tool to my MCP server"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SillyTavern MCP Server
A read-only Model Context Protocol server that exposes a SillyTavern user directory (characters, personas, chat-completion presets, lorebooks, chats) to general-purpose agent clients — Claude Desktop, Raycast, BoltAI, etc.
See docs/MVP.md for the full design spec: architecture, handle scheme, envelope format, and tool inventory.
Status
The full MVP tool inventory (§6) is implemented and end-to-end tested over real stdio:
Characters —
list-characters,get-characterPersonas —
list-personas,get-personaPresets —
list-presets,get-preset,export-presetLorebooks —
list-lorebooks,get-lorebook,search-lorebookChats (the ladder) —
list-chats→get-chat-manifest→get-chat-summaries→search-chat→get-messages→export-chat
Remaining work is the explicitly-deferred post-MVP backlog (docs/MVP.md §8) — track it via bd (this repo's issue tracker — run bd ready / bd list).
Related MCP server: labsolu-mcp-test
Project layout
packages/core/ pure library — no MCP awareness
fs/ the ONLY module that touches the filesystem (reads + export writes)
resolve/ user-dir resolution, startup validation, handles, name resolution
parse/ one parser per surface (cards, chats, lorebooks, presets, personas, summaries)
render/ transcript assembly, preset outline/full, token estimates, prefix stripping
packages/mcp/ stdio MCP adapter — envelope, tool registration, one file per tool group
packages/cli/ st-mcp CLI — npx entrypoint + `doctor` subcommand
docs/MVP.md design specGetting started locally
npm install
npm run build
node packages/cli/dist/bin.js --user-dir /path/to/SillyTavern/data/default-user--user-dir is optional — see docs/MVP.md §3 for the full resolution order (flag > SILLYTAVERN_USER_DIR env var > ~/.config/st-mcp/config.json > platform-default guesses). The server refuses to start and lists every path it tried if none resolve to a valid SillyTavern user directory.
To check your user-dir without starting the server:
node packages/cli/dist/bin.js doctor --user-dir /path/to/SillyTavern/data/default-userRunning tests
npm testLearn more
This server cannot be deployed
Maintenance
Related MCP Connectors
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Give any MCP-compatible AI assistant a builder for live, hosted web tools and workflows.
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceA minimal Model Context Protocol server template for Render with bearer token authentication, an example tool, and a health check endpoint. Enables deploying custom MCP tools quickly on Render.-
- FlicenseNot gradedqualityCmaintenanceEnables developers to deploy a Model Context Protocol server to Render with bearer token authentication, allowing custom tools to be connected to MCP clients like Claude Desktop and Cursor.-
- FlicenseNot gradedqualityCmaintenanceThis template enables developers to quickly scaffold, deploy, and extend a Model Context Protocol server on Render, with bearer-token authentication and a streamable HTTP endpoint, by adding custom tools via Python.-
- FlicenseNot gradedqualityCmaintenanceEnables users to deploy a minimal Model Context Protocol server on Render, connect MCP clients with bearer-token authentication, and add custom tools callable through the MCP endpoint.-