Sandboxed local filesystem: read, search, edit, copy, archive, and safely manage files.
FS_ROOTS, FS_READONLY
ตรวจสอบล่าสุด
2026-11-08
ดาว
—
เครื่องมือ
—
อัปไทม์
—
Each server lives in its own folder under servers/ and publishes to npm as an independent package, while sharing tooling through an npm workspace. Connect them to any MCP client — Claude Desktop, Claude Code, Cursor, and more.
More on the way: a Spotify controller, and others.
Quickstart
git clone https://github.com/Abhishekkumar2021/mcp-suite.git
cd mcp-suite
npm install # installs deps for every workspace
npm run build # builds every server
Install
Every server ships through every common channel. For the Claude Code plugin, add the marketplace
once — /plugin marketplace add Abhishekkumar2021/mcp-suite — then install per the table. See each
server's README for full config.
Pure-JS/WASM by default; native only when genuinely required. Servers run via npx/MCPB on any
machine, so portable pure-JS/WebAssembly is strongly preferred and a native dependency is used only when
genuinely required (gated + documented). In practice these servers are dependency-light: notes uses
MiniSearch + WebAssembly embeddings, sql uses the sql.js WASM SQLite engine, and files uses
fast-glob instead of ripgrep. npm audit stays clean.
Sandbox-first, layered design. Each server keeps a thin index.ts (tool registration only) over
focused modules, with a single security boundary every path must pass through (realpath-containment,
symlink-escape rejection, atomic writes).
Token-efficient by default. Pagination, head/tail/section reads, snippets, and compact graph refs
keep tool output small.
Automated, hands-off releases. A GitHub Release tagged <server>-v<version> publishes to npm
(with provenance), the official MCP registry, and attaches an MCPB bundle — all via OIDC, no secrets.
Tested in CI. Each server ships a committed node:test suite (unit + integration/security) run on
every push.
npm install # install all workspace dependencies (run once at the root)
npm run build # build every server
npm run build -w servers/notes # build a single server
npm test --workspaces --if-present # run each server's test suite
npm run clean # remove all build output
Adding a new server
Create servers/<name>/ with its own package.json (unique npm name) and a tsconfig.json that extends: "../../tsconfig.base.json".
Put source in servers/<name>/src/.
Run npm install at the root so the workspace picks it up.
Releases are automated. Cutting a GitHub Release tagged <server>-v<version> triggers
publish.yml, which — authenticated entirely via GitHub OIDC (no
NPM_TOKEN) — publishes the package to npm with provenance, registers it on the official MCP
registry, and builds + attaches the MCPB bundle to the release.
