AIStorageDepot
@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)andget_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):
{
"mcpServers": {
"aisd": { "command": "npx", "args": ["-y", "@aistoragedepot/mcp"] }
}
}Related MCP server: @prompthub/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:
In AIStorageDepot, go to Settings → API tokens and create a token (free for individuals). Copy it.
Add the server to your MCP client's config. Example (Claude Desktop /
claude_desktop_config.json, Cursor~/.cursor/mcp.json, etc.):
{
"mcpServers": {
"aisd": {
"command": "npx",
"args": ["-y", "@aistoragedepot/mcp"],
"env": {
"AISD_TOKEN": "aisd_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}Restart the client. The items you marked / appear as slash-commands; everything is available as resources; and the
search_library/get_itemtools are ready.
Configuration
Env var | Required | Default | Notes |
| no | — | 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. |
| no |
| Point at a self-hosted / dev instance if needed. |
| no | — | 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:
npx -y @aistoragedepot/mcp pull --token=aisd_your_token --to=allTarget | Writes to | Commands appear as |
|
|
|
|
|
|
| your VS Code profile's |
|
|
|
|
|
|
|
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.
Option | Default | |
|
| Which tools to write commands for — comma list, or |
|
| Your API token. |
|
| Which item types become commands (e.g. |
| your personal library | Which workspaces to pull (names, or |
| off | Write into the current repo instead: |
| per-target | Write somewhere else entirely (single |
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
npm install
AISD_TOKEN=<token> AISD_BASE_URL=http://localhost:3100 npm run test:clientTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
v0.6.7- Removed
get_item - Removed
search_library
2 tool updates
v0.1.1- Changed
get_item1 field changed- changed
Input schema / properties / id / descriptionPrevious value: -"The item id, or an aisd://item/<id> URI."New value: +"An item id, or a full aisd://item/<id> URI — the aisd://item/ prefix is stripped for you, so search_library output can be pasted unchanged. Exact match only, one id per call: no titles, slugs, partial ids, wildcards, or comma-separated lists, so fetch N items with N calls. Use only an id returned by search_library, a resource listing, or supplied by the user — ids cannot be derived from titles, and an id outside the libraries you can read resolves as not found."
- Added
search_library
1 tool update
v0.1.0- First observed
get_item
TDQS
The two tools have completely distinct purposes: search_library discovers items by keyword (returns metadata only) and get_item retrieves full content by ID. There is no overlap or ambiguity in their functionalities.
Both tool names follow a consistent verb_noun pattern (search_library, get_item) using snake_case, making it clear what each tool does at a glance.
With only 2 tools, the server is minimal but well-scoped for a read-only library search and retrieval workflow. While one might expect additional tools for browsing or management, the count fits the stated purpose.
The server covers the core search and retrieve workflow, but lacks tools for browsing libraries without a keyword or listing all items. This limits discoverability and leaves some common operations unsupported.
Maintenance
Related MCP Connectors
Self-hosted AI prompt library: prompts, collections, tags, teams, chains. 29 MCP tools for agents.
shared AI-context layer for teams — persistent memory your agents search and update over MCP
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Governed AI agent skills — one library, distributed to devs and exposed to remote agents over MCP.
Related MCP Servers
AlicenseAqualityAmaintenanceTurns team chat (Slack, Discord, MS Teams, Mattermost) into a living knowledge base - a typed knowledge graph plus auto-generated wiki - exposed to AI agents through a 28-tool MCP server with semantic search, expert finding, and decision tracing.28443Apache 2.0- AlicenseNot gradedqualityBmaintenanceMCP server for PromptHub. Enables publishing, fetching, listing, updating, and searching prompt repositories from Claude Code or Codex.10MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP server for storing and serving structured team knowledge, enabling AI sessions to load relevant team context without re-prompting.Apache 2.0
- AlicenseAqualityDmaintenanceDelivers on-demand knowledge from a built-in library of 728 agents, skills, patterns, and examples across 26 domains to any MCP-compatible AI tool.6141MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIStorageDepot/aistoragedepot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server