mcp-stashbox

What this does

mcp-stashbox exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

STASHBOX_STASHDB_KEY
STASHBOX_TPDB_KEY
STASHBOX_FANSDB_KEY
STASHBOX_PMV_KEY
STASHBOX_JAVSTASH_KEY
SB_USER_AGENT
SB_MIN_INTERVAL_MS
SB_TIMEOUT_MS
SB_MAX_RETRIES
SB_CACHE_TTL_MS
SB_CACHE_MAX_ENTRIES
SB_LOG_LEVEL

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install mcp-stashbox?

Run the Claude Code command in the install section to add mcp-stashbox to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with mcp-stashbox?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to mcp-stashbox as well.

Does mcp-stashbox need an API key?

This listing does not flag an API key as required. The server can use these environment variables: STASHBOX_STASHDB_KEY, STASHBOX_TPDB_KEY, STASHBOX_FANSDB_KEY, STASHBOX_PMV_KEY, STASHBOX_JAVSTASH_KEY, SB_USER_AGENT, SB_MIN_INTERVAL_MS, SB_TIMEOUT_MS, SB_MAX_RETRIES, SB_CACHE_TTL_MS, SB_CACHE_MAX_ENTRIES, SB_LOG_LEVEL; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.