AIShelf

The AIShelf Ecosystem

AIShelf has one central piece - the service - and multiple thin clients that connect to it. This page explains each component, what it does, and how they relate. If you want to understand the system before committing, you're in the right place.

// clients (thin)

VS Code Extension

ide-extension

coming soon

Browser Extension

chrome-extension

MCP Server

mcp-server

coming soon

Claude Code Plugins

& Skills

HTTP - localhost:5314

AISHELF SERVICE

shared hub · runs in background

Single connection point · :5314Shared local store · ~/.aishelf/GitHub auth & sync

GitHub Registries

team repos

AIShelf Backend

auth & subscriptions

Every client - VS Code, MCP server, browser extension - connects to the same local store. Change a resource once and every tool stays in sync automatically.

The Service

@aishelf/service · port 5314 · ~/.aishelf/

The AIShelf Service is what makes your team's resources available everywhere. Run it once, and every client - your VS Code extension, MCP server, and browser extension - reads from the same local store. You don't copy-paste resources between tools; they're all in sync because they all connect here.

What it does

  • Keeps local copies of your team's registries so everything loads fast and works offline - stored in ~/.aishelf/
  • Sign in to GitHub once - every client you use gets access automatically, credentials stored in ~/.aishelf/
  • Syncs registries with GitHub - pull, commit, push - on request
  • Runs on http://localhost:5314 - every client on your machine connects to it
  • Keeps your local resources secure - only trusted clients on your machine can connect

Key design principle

Everything in sync, automatically

You never have to manually sync resources between tools. Every client reads from and writes to the same place - so when your team updates a workflow, every client sees the latest version. Your GitHub credentials are stored once in ~/.aishelf/, not scattered across every tool.

No cloud dependency for local operations

Once your registries are cloned, the service works entirely offline - browse and read resources without an internet connection. GitHub is only contacted when you choose to sync or push changes. Your credentials stay on your machine in ~/.aishelf/ - not in any cloud service.

Health check

curl http://localhost:5314/health
# Expected: {"status":"ok"}

VS Code Extension

AIShelf.aishelf · VS Code Marketplace

The VS Code extension is the primary way to interact with AIShelf from your IDE. It provides a sidebar panel for browsing registries, an inline preview for resources, and tools for creating and pushing content back to the registry.

What you can do

  • Browse all connected registries in a tree view from the IDE sidebar
  • Preview resources inline without switching context
  • Copy any resource to the clipboard with one click
  • Insert resources directly into AI tools - Cursor's .cursorrules, Windsurf custom rules, and more
  • Create and edit resources as local drafts, then push to the registry when ready
  • Sync registries to pull the latest team updates

Compatible IDEs

Works with any VS Code-based editor - VS Code, Cursor, Windsurf, and others (version 1.105.0+).

MCP ServerEarly Preview

@aishelf/mcp-server · npm

The AIShelf MCP server exposes your registry resources to AI models via the Model Context Protocol. Once configured, AI assistants can discover and apply your team's workflows, rules, prompts, and skills automatically - without any manual copy-paste.

Compatible clients

Any MCP-capable AI client works: Claude, Cursor, Windsurf, and others that support the Model Context Protocol.

Two tools

  • list_resources - returns an index of all resources across your connected registries, with enough metadata for the AI to identify what to fetch
  • get_resource - fetches the full content of a specific resource by its path

Configuration

Add this to your IDE's MCP configuration file:

mcp.json
{
  "mcpServers": {
    "aishelf": {
      "command": "npx",
      "args": ["-y", "@aishelf/mcp-server"]
    }
  }
}

Tip

Add use aishelf anywhere in your prompt to explicitly tell the model to check AIShelf for relevant resources before responding.

Browser ExtensionComing Soon

chrome-extension

The browser extension will bring AIShelf to any web-based AI tool - ChatGPT, Claude.ai, Gemini, and others. Browse your registry and insert resources directly from the browser, using the same service hub running on your machine.

Not yet available

The browser extension is in development. It will connect to the same local AIShelf Service as all other clients. Check back for updates, or watch the GitHub repository for progress.

Claude Code Plugins & SkillsComing Soon

claude-code

An upcoming integration that will bring AIShelf resources directly into Claude Code sessions. The goal is to let Claude Code automatically discover and apply team-maintained workflows, rules, and skills from your AIShelf registries - without any manual setup per project.

Use AIShelf with Claude Code today

The MCP server already works with Claude Code. Configure it once and Claude Code will be able to discover your registry resources via the list_resources and get_resource tools. See the MCP Server setup guide.

Next Steps