The publisher's own command. Not a PlugMCP endpoint.
npx -y @abhishekmcp/[email protected]
GITHUB_TOKEN=<secret> GITHUB_CLIENT_ID=<value> GITHUB_READONLY=<value> claude mcp add io.github.abhishekkumar2021-github -- npx -y @abhishekmcp/[email protected]
Run in a terminal.
{
"mcpServers": {
"io.github.abhishekkumar2021-github": {
"command": "npx",
"args": [
"-y",
"@abhishekmcp/[email protected]"
],
"env": {
"GITHUB_TOKEN": "<secret>",
"GITHUB_CLIENT_ID": "<value>",
"GITHUB_READONLY": "<value>"
}
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
GitHub via MCP: search, repos, issues, PRs, files, notifications. OAuth device flow or token.
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.
No FAQ yet. Enrichment fills this from the README on the next crawl.
No tool list yet. Remote servers get one after the first health check.
| 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 |
github | GitHub: search repos/code/issues, read repos/issues/PRs/files, notifications, create issues β OAuth device flow or token | β Stable |
git | Git: status, log, diff, file history, branches/tags, gated stage/commit, and remote clone/fetch/pull/push β pure-JS, no git binary | β Stable |
sql | SQL databases: read-only query + schema introspection over Postgres & SQLite, gated writes | β Stable |
http | HTTP/REST client: ad-hoc requests + saved collections/environments, env secrets, host-allowlisted + SSRF-safe | β Stable |
More on the way: a Spotify controller, and others.
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
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 |
github | /plugin install github | npx -y @abhishekmcp/github | drag github-*.mcpb | io.github.Abhishekkumar2021/github |
git | /plugin install git | npx -y @abhishekmcp/git | drag git-*.mcpb | io.github.Abhishekkumar2021/git |
sql | /plugin install sql | npx -y @abhishekmcp/sql | drag sql-*.mcpb | io.github.Abhishekkumar2021/sql |
http | /plugin install http | npx -y @abhishekmcp/http | drag http-*.mcpb | io.github.Abhishekkumar2021/http |
notesdefaults to~/notes;filesrequiresFS_ROOTS(the directories it may touch). MCPB bundles install via Claude Desktop β Settings β Extensions.
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" }
}
}
}
A few principles hold across every server:
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.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).<server>-v<version> publishes to npm
(with provenance), the official MCP registry, and attaches an MCPB bundle β all via OIDC, no secrets.node:test suite (unit + integration/security) run on
every push.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
servers/<name>/ with its own package.json (unique npm name) and a tsconfig.json that extends: "../../tsconfig.base.json".servers/<name>/src/.npm install at the root so the workspace picks it up.All servers follow the naming standard (@abhishekmcp/<slug>). See CONTRIBUTING.md for detailed guidelines.
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.
# bump servers/<name>/package.json, commit, then:
gh release create <name>-v<version> --title "<name> v<version>" --notes "β¦"
Contributions are welcome! Please read CONTRIBUTING.md and our Code of Conduct. Found a security issue? See SECURITY.md.
MIT Β© Abhishek