Get the FREE Ultimate OpenClaw Setup Guide →

stash_mcp_server

MCP server that exposes advanced tools for querying a Stash instance.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio donlothario-stash_mcp_server python -m stash_mcp_server \
  --env LOG_LEVEL="INFO" \
  --env STASH_API_URL="https://your-stash-instance" \
  --env STASH_API_TOKEN="your-api-token-or-empty-if-not-required" \
  --env CACHE_TTL_SECONDS="300"

How to use

This MCP server provides a focused toolkit for querying and analyzing a Stash instance. It exposes a concise set of prompts and tools to fetch performer data, generate insights, and surface personalized scene recommendations. You can use commands to get performer information, list all performers with advanced filters, retrieve scenes for a performer, and run strategic insights like library analytics or health checks. The server is designed to be composable, so you can chain tools or call individual endpoints to build your own analysis workflows against your Stash installation.

How to install

Prerequisites:

  • Python 3.9+ installed on your system
  • Git installed
  • Access to a Stash instance (self-hosted or cloud) with appropriate API credentials if required

Installation steps:

  1. Clone the repository git clone https://github.com/donlothario/stash_mcp_server.git cd stash_mcp_server

  2. (Optional but recommended) Create and activate a virtual environment python -m venv venv source venv/bin/activate # On Windows use: venv\Scripts\activate.bat

  3. Install dependencies pip install -U pip if an installation file exists, install from source: pip install -e . or install requirements if provided: pip install -r requirements.txt

  4. Run the MCP server python -m stash_mcp_server

  5. Configure mcp_config for your environment as shown in the example above, adjusting STASH_API_URL and credentials as needed.

Additional notes

Notes and tips:

  • Ensure your Stash API URL is reachable from the MCP server host and that any required authentication tokens are configured via environment variables.
  • The server includes prompts such as analyze-performer, library-insights, and recommend-scenes, plus a suite of tools for performer and scene data. You can adjust caching and log levels via environment variables.
  • If running behind a firewall or in a container, expose necessary ports and set appropriate network policies.
  • For production deployments, consider mounting a persistent cache directory and enabling structured logging.

Related MCP Servers

Sponsor this space

Reach thousands of developers