🧰 mcp-suite

A collection of Model Context Protocol servers, built in TypeScript.

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.

Servers
Quickstart
Install
Connecting to a client
Architecture & conventions
Development
Adding a new server
Publishing
Contributing
License

Servers

Server	Description	Status
`notes`	Local markdown notes: ranked full-text and semantic search, tags, todos, a `[[wiki-link]]` knowledge graph, daily notes + templates, and slash-command workflows (prompts)	✅ Stable
`files`	Sandboxed local filesystem: read, glob + content search, token-efficient edits, copy/move, soft-delete trash, zip, checksums, and dedup	✅ Stable

More on the way: a GitHub helper, 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.

Server	Claude Code plugin	npm (any client)	Claude Desktop (MCPB)	MCP registry
`notes`	`/plugin install notes`	`npx -y @abhishekmcp/notes`	drag `notes-*.mcpb` from the latest release	`io.github.Abhishekkumar2021/notes`
`files`	`/plugin install files`	`npx -y @abhishekmcp/files`	drag `files-*.mcpb`	`io.github.Abhishekkumar2021/files`

notes defaults to ~/notes; files requires FS_ROOTS (the directories it may touch). MCPB bundles install via Claude Desktop → Settings → Extensions.

Connecting to a client

Each server's README has full configuration instructions. As an example, to use the notes server with Claude Code:

claude mcp add notes --env NOTES_DIR=$HOME/notes -- node "$(pwd)/servers/notes/dist/index.js"

Or with Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "notes": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-suite/servers/notes/dist/index.js"],
      "env": { "NOTES_DIR": "/absolute/path/to/your/notes" }
    }
  }
}

Architecture & conventions

A few principles hold across every server:

Pure-JS, no native dependencies. Servers run via npx/MCPB on any machine, so anything needing a native build is off-limits (e.g. notes uses MiniSearch + WebAssembly embeddings instead of SQLite; 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 -v 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.

Development

This is an npm workspaces monorepo.

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// with its own package.json (unique npm name) and a tsconfig.json that extends: "../../tsconfig.base.json".
Put source in servers//src/.
Run npm install at the root so the workspace picks it up.
Add a row to the Servers table above.

All servers follow the naming standard (@abhishekmcp/). See CONTRIBUTING.md for detailed guidelines.

Publishing

Releases are automated. Cutting a GitHub Release tagged -v 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.

# bump servers//package.json, commit, then:
gh release create -v --title " v" --notes "…"

Contributing

Contributions are welcome! Please read CONTRIBUTING.md and our Code of Conduct. Found a security issue? See SECURITY.md.

Files