AIStorageDepot

io.github.aistoragedepot-adminPublished by GitHub account aistoragedepot-adminv0.6.7Updated Oct 24, 2026

Prompt, rules, skills & docs library over MCP. No token = read-only sample of the public library.

The publisher's own server: Tigris MCP Server

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Exposes an AIStorageDepot library of prompts, rules, docs and skills to MCP clients as prompts, resources and search tools.

What you can do
The server surfaces a stored AIStorageDepot library inside MCP-aware clients. Items marked with a slash in the app become MCP prompts whose bracketed fields appear as prompt arguments; every item (rules, docs, skills, MCP configs, prompts) is readable as a resource at aisd://item/ ; and the tools search_library(query) and get_item(id) let an agent find and fetch content programmatically. A separate pull command can sync the library into native slash-command files for Claude, Cursor, VS Code, Windsurf and Codex.
When to use it
Use it when you keep reusable prompts, coding rules, guidelines or skills in AIStorageDepot and want an assistant to pull them into context on demand, or to expose them as slash-commands in your editor. It is also a way to preview the public curated library without an account.
Requirements
Runs locally over stdio, typically via npx @aistoragedepot/mcp, so Node.js is needed. No account is required for anonymous sample mode; full access to your own and team libraries needs an API token in the AISD_TOKEN environment variable. AISD_BASE_URL can point at a self-hosted instance. Network access to the AIStorageDepot API is required.
Before you install
AISD_TOKEN is described as having full access to your account and should be kept secret; it can be revoked in Settings. Without a token the server is read-only against a public sample library. The server is read-only in v0.1 and does not write back, but the pull command writes command files into tool config directories or, with --project, into the current repository, so check the target paths before running it.

Installation

In SourceWeft

  1. Open AIStorageDepot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@aistoragedepot/mcp

A Model Context Protocol server that exposes your AIStorageDepot library to any MCP-aware AI client — Claude Desktop, Cursor, Cline, Windsurf, and others.

Your stored content shows up where you actually work:

  • Prompts → the items you mark with / in the app become MCP prompts (slash-commands) — any type, with each prompt's [field] surfaced as a prompt argument you fill in.
  • Resources → every item (rules, docs, skills, MCP configs, prompts) is readable at aisd://item/<id>, so an agent can pull "my coding rules" or "my project guidelines" into context on demand.
  • Tools → search_library(query) and get_item(id) let an agent find and fetch anything in your library programmatically.

Try it with no account (sample mode)

AISD_TOKEN is optional. Run the server with no token and it serves a free, read-only sample of the public curated library — a good way to see AIStorageDepot inside your editor before signing up. Add a token later to switch to your own & team libraries. Add the server with an empty env (or omit AISD_TOKEN):

json
{  "mcpServers": {    "aisd": { "command": "npx", "args": ["-y", "@aistoragedepot/mcp"] }  }}

Setup

👉 Easiest path: step-by-step instructions for each app (config-file locations and all) are at https://www.aistoragedepot.com/connect. The manual version:

  1. In AIStorageDepot, go to Settings → API tokens and create a token (free for individuals). Copy it.
  2. Add the server to your MCP client's config. Example (Claude Desktop / claude_desktop_config.json, Cursor ~/.cursor/mcp.json, etc.):
json
{  "mcpServers": {    "aisd": {      "command": "npx",      "args": ["-y", "@aistoragedepot/mcp"],      "env": {        "AISD_TOKEN": "aisd_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"      }    }  }}
  1. Restart the client. The items you marked / appear as slash-commands; everything is available as resources; and the search_library / get_item tools are ready.

Configuration

Env varRequiredDefaultNotes
AISD_TOKENno—Token from Settings → API tokens. No token = anonymous sample mode (the free public curated library, read-only). With a token you get your own & team libraries. Has full access to your account — keep it secret.
AISD_BASE_URLnohttps://www.aistoragedepot.comPoint at a self-hosted / dev instance if needed.
AISD_WORKSPACESno—Retired. Your slash menu is now the items you mark / in the app (strict opt-in); this variable is ignored. Search and resources still cover every workspace.

Slash-commands (pull)

Not every client turns MCP prompts into / slash-commands (some only use the tools). To get your library as native slash-commands, sync it to command files — for every AI tool you use, not just Claude:

bash
npx -y @aistoragedepot/mcp pull --token=aisd_your_token --to=all
TargetWrites toCommands appear as
claude (default)~/.claude/commands/aisd//aisd:<name>
cursor~/.cursor/commands//aisd-<name>
vscodeyour VS Code profile's prompts/ folder (Copilot Chat)/aisd-<name>
windsurf~/.codeium/windsurf/global_workflows/ (Cascade)/aisd-<name>
codex~/.codex/prompts//prompts:aisd-<name>

Tools that aren't installed are skipped automatically. Each tool gets its own dialect (frontmatter, argument hints, $ARGUMENTS where supported). Skills run as-is. Prompts take input: their [fields] show as an argument hint, and whatever you type after the command fills them —

/aisd:cold-outreach Jane at Globex, about our payments API

— with the AI asking for any value you left out.

OptionDefault
--to=…claudeWhich tools to write commands for — comma list, or all.
--token=…AISD_TOKEN envYour API token.
--types=…skill,promptWhich item types become commands (e.g. skill for skills only).
--workspaces="A,B"your personal libraryWhich workspaces to pull (names, or all).
--projectoffWrite into the current repo instead: .claude/commands/, .cursor/commands/, .github/prompts/, .windsurf/workflows/.
--dir=<path>per-targetWrite somewhere else entirely (single --to only).

Re-runs are safe: each target only clears its own files (claude: its namespaced folder; the others: only files with the aisd- prefix — your own commands are never touched).

Notes

  • Read-only in v0.1 (it surfaces and fetches your content; it doesn't write back).
  • The library snapshot is cached for ~30s, so a burst of calls hits the API once.
  • Revoke a token any time in Settings → API tokens; the server loses access immediately.

Local development

bash
npm installAISD_TOKEN=<token> AISD_BASE_URL=http://localhost:3100 npm run test:client

Source: README.md at commit c08f56e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.7LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Storage integrations