SillyTavern

This MCP server provides a bridge between SillyTavern and MCP clients, allowing you to load and manage server plugins for SillyTavern through the MCP protocol. Once the SillyTavern MCP server is running, you can connect using the SillyTavern-MCP-Client to browse available MCP servers, install or enable plugins, and configure plugin behavior. The server exposes typical MCP capabilities such as activating plugins, retrieving plugin metadata, and handling runtime configuration changes for SillyTavern.

To get started, clone the repository into SillyTavern's plugins directory, start the MCP server, and then use the client to connect to the SillyTavern MCP server. Ensure you have trusted sources when enabling MCP servers, and restart SillyTavern after enabling plugins to apply changes.

Prerequisites:

• A running SillyTavern instance with plugins support
• Node.js installed on the machine where you install this MCP server (recommended for this server implementation)
• Access to the SillyTavern plugins directory

Installation steps:

1. Open a terminal in the SillyTavern plugins directory.
2. Clone the MCP server repository:

git clone https://github.com/bmen25124/SillyTavern-MCP-Server

3. (Optional) Install dependencies if a package.json exists:

cd SillyTavern-MCP-Server
npm install

4. Enable server plugins in SillyTavern configuration:

• Edit {SillyTavern_Folder}/config.yaml and set enableServerPlugins: true

5. Start the MCP server (based on the mcp_config, typically via node server.js):

node server.js

6. Connect using the SillyTavern-MCP-Client to manage plugins and configurations.

Note: Always ensure you are using trusted MCP servers and clients to avoid running unverified code.

Tips and caveats:

• Only install MCP servers from trusted sources to minimize security risks.
• If you modify environment variables, restart SillyTavern and the MCP server to apply changes.
• Some MCP servers may require specific Node.js versions or additional dependencies; check the repository README for any extra prerequisites.
• If the MCP server fails to start, verify that the plugin directory is writable and that the required port is not in use.
• Use the SillyTavern-MCP-Client to gracefully manage plugins, view metadata, and update configurations without restarting SillyTavern.

Configuration options to consider:

• Environment variables for log level, plugin paths, or feature toggles.
• Custom port bindings for the MCP server if you run multiple MCP servers concurrently.
• Security: restrict MCP access to trusted networks or require authentication where supported.