Unstorage

Created By
slow-groovina year ago
Overview

what is Unstorage?

Unstorage is a Key-Value storage MCP server that utilizes the unjs/unstorage library, providing a flexible and efficient way to manage data across various storage drivers.

how to use Unstorage?

To use Unstorage, you need to install it via npm and configure the desired storage driver (e.g., Redis, MongoDB, filesystem) by setting the appropriate environment variables. You can then interact with the server using provided commands to store and retrieve data.

key features of Unstorage?

  • Supports multiple storage drivers including memory, filesystem, Redis, and MongoDB.
  • Provides a set of tools for data manipulation such as getItem, setItem, and removeItem.
  • Easy installation and configuration through environment variables.

use cases of Unstorage?

  1. Storing user session data in Redis for fast access.
  2. Managing application configuration settings in a filesystem.
  3. Using MongoDB for persistent data storage in web applications.

FAQ from Unstorage?

  • What storage drivers does Unstorage support?

Unstorage supports memory, filesystem, Redis, MongoDB, and HTTP server drivers.

  • Is Unstorage easy to install?

Yes! Unstorage can be installed using npm with simple configuration steps.

  • Can I extend Unstorage with custom storage drivers?

Yes! You can clone the repository and implement your own storage driver by following the provided guidelines.

Server Config

{
  "mcpServers": {
    "unstorage": {
      "command": "npx",
      "env": {
        "REDIS_URL": "redis://default:123456@localhost:6379",
        "REDIS_BASE": "my:mcp:values:",
        "REDIS_MOUNT_POINT": "redis_storage"
      },
      "args": [
        "/y",
        "@slow-groovin/unstorage-mcp",
        "--disable-modify"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
slow-groovin
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago