Storacha MCP Storage Server

Created By
storachaa year ago
Storacha MCP storage server - self-sovereign data for your AI applications.
Overview

What is Storacha MCP Storage Server?

The Storacha MCP Storage Server is a Model Context Protocol (MCP) server implementation that allows AI applications to interact with decentralized storage through a standardized interface.

How to use Storacha MCP Storage Server?

To use the server, clone the repository, install dependencies, configure the environment variables, and start the server using either Stdio or SSE transport modes.

Key features of Storacha MCP Storage Server?

  • File operations for uploading and retrieving files.
  • Identity management to get the DID key of the Storacha agent.
  • Dual transport modes (HTTP with SSE and Stdio).
  • Standardized MCP-compliant API for tool discovery.
  • Security features including bearer tokens and input validation.

Use cases of Storacha MCP Storage Server?

  1. Document storage and analysis.
  2. Long-term structured data storage.
  3. Data sharing between agents and systems.
  4. Application integration for seamless data access.
  5. AI model development with reliable access to datasets.
  6. Web application backups for disaster recovery.
  7. Managing large datasets for machine learning workflows.

FAQ from Storacha MCP Storage Server?

  • What is the purpose of the MCP Storage Server?

It enables AI applications to interact with decentralized storage efficiently.

  • Is there a cost to use the server?

The server is open-source and free to use.

  • What programming languages are supported?

The server is implemented in TypeScript.

Server Config

{
  "mcpServers": {
    "storacha-storage-server": {
      "command": "node",
      "args": [
        "./dist/index.js"
      ],
      "env": {
        "MCP_TRANSPORT_MODE": "stdio",
        "PRIVATE_KEY": "<agent_private_key>",
        "DELEGATION": "<base64_delegation>"
      },
      "shell": true,
      "cwd": "./"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
storacha
Star
6
Language
TypeScript
License
Apache-2.0 license
Category

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