n24q02m Claude Plugins

Claude Code plugin marketplace for the n24q02m MCP servers -- install web search, memory, Notion, email, Telegram, code review, and Google Workspace tools in one command.

Table of contents

• Install
• Plugins
• Configuration
• Skills
• Other MCP Clients
• Deployment
• Contributing
• License

7 MCP servers for AI coding agents, from one marketplace.

Full documentation: docs.n24q02m.com — setup and tool references for all 7 servers, the hull foundation, and Fastretrieval. Libraries and CLIs do not gain an MCP transport by appearing in the same documentation site.

Install

/plugin marketplace add n24q02m/claude-plugins
/plugin install <plugin-name>@n24q02m-plugins

Or browse all plugins: run /plugin and go to the Discover tab.

Plugins

Not marketplace plugins

Four n24q02m projects share this documentation site without getting a marketplace entry. The test is the plugin layout: the project itself ships .claude-plugin/plugin.json plus a skills/ or hooks/ tree over an MCP server entrypoint, which is what plugin-sync copies from. None of the four does, so an entry here would be a copy with no upstream to sync from.

Install each the way its project documents it: pip install n24q02m-hull, pip install fastretrieval, a sillstone-* crate (or cargo install sillstone-cli for the sillstone binary), or the skret install script. Adding .claude-plugin/ to one of them is what would make it a marketplace entry — the entry does not create the capability.

Configuration

When you run /plugin install, Claude Code prompts for that plugin's credentials (declared in each plugin's userConfig) and stores sensitive values in your system keychain. You can also set them via the env block in ~/.claude/settings.local.json, or export them in your shell profile.

notion, email, and workspace require credentials for their upstream APIs. telegram needs a bot token only for bot mode. Wet, Mnemo, and CRG preserve local Fastretrieval-based retrieval without provider API keys. Wet web search additionally needs a runnable backend: credential-free DuckDuckGo/Startpage, an external SearXNG endpoint, a configured cloud provider, or a local installation that can run SearXNG.

Cloud providers (wet, mnemo, crg)

Cloud model selection is separate from installing a plugin and is configured on
the machine that runs the server, in ~/.<server>/config.toml. Do not infer a
fallback chain just because several keys are present.

• Wet and Mnemo use model cells: [models.embed], [models.rerank] and
  [models.chat], each with base_url, model and api_key. The environment
  variable HULL_<TASK>_API_KEY (for example HULL_EMBED_API_KEY) overrides
  the key in the file, and OPENROUTER_API_KEY serves the pre-wired default
  cells. An empty embed or rerank cell falls back to local ONNX models.
• CRG uses [models.chat] for summaries and EMBEDDING_MODELS for embeddings
  (empty means local ONNX); its optional query reranker is selected by
  LOCAL_RERANK_MODEL, not a cloud rerank chain.
• Without a chat key, LLM-backed features are switched off rather than failing.
• Empty/local configuration and cloud behavior are server-specific; see
  Credential setup and
  the setup references.

CRG does not currently implement cloud reranking.

Telegram

TELEGRAM_BOT_TOKEN=123456:ABC-DEF...

Required for bot mode (from @BotFather); leave empty for user mode.

Email

[email protected]:app-password

Multiple accounts: [email protected]:pass1,[email protected]:pass2

Notion

NOTION_TOKEN=ntn_xxx

Get your token from notion.so/my-integrations.

Google Workspace

GOOGLE_OAUTH_CLIENT_ID=<your-client-id>.apps.googleusercontent.com
GOOGLE_OAUTH_CLIENT_SECRET=<your-client-secret>

Create the OAuth client yourself at console.cloud.google.com/apis/credentials — type Desktop app for the default stdio mode, Web application for self-hosted HTTP. The first run opens Google's consent screen once, then reuses the stored refresh token.

Skills

Most plugins ship skills, invoked in Claude Code as <plugin>:<skill>:

Other MCP Clients

Each plugin works with any MCP client. Run directly:

Python plugins (uvx / pipx / docker):

uvx --python 3.13 --from n24q02m-wet wet server start   # HTTP only: http://127.0.0.1:8000/mcp
uvx --python 3.13 n24q02m-mnemo                         # HTTP only: http://127.0.0.1:8000/mcp
uvx --python 3.13 n24q02m-telegram
uvx --python 3.13 n24q02m-crg

TypeScript plugins (npx / bunx / docker):

npx -y @n24q02m/notion
npx -y @n24q02m/email

Add to any MCP client's settings.json (stdio servers by command, HTTP-only servers such as wet and mnemo by URL):

{
  "mcpServers": {
    "crg": {
      "command": "uvx",
      "args": ["--python", "3.13", "n24q02m-crg"]
    },
    "wet": {
      "type": "http",
      "url": "http://127.0.0.1:8000/mcp"
    }
  }
}

Deployment

The docs site (docs.n24q02m.com) is served by the consolidated portal in n24q02m/tools-docs (Cloudflare Pages project tools-n24q02m); legacy paths such as docs.n24q02m.com/plugins/** and docs.n24q02m.com/skret/** are the portal routes. This repo no longer builds or deploys a docs site: the old Pages project and its deploy-docs job in cd.yml are retired. The docs/ Astro tree stays because CI still runs its generator and tests (docs/scripts/sync-plugin-docs.mjs, exercised by node --test docs/scripts/test-sync-plugin-docs.mjs in ci.yml); it is not published here.

Plugin assets are synced separately: when a server repo cuts a release, cd.yml (plugin-sync) copies that release tag's plugin.json, skills, hooks, and commands into plugins/<name>/ on main. Nothing in this repo redeploys a docs site after that sync.

Contributing

See CONTRIBUTING.md.

License

Apache-2.0