2389 Research Plugins

2389 Research marketplace: 28 plugins and MCP servers for Claude Code, from parallel solution search to CSS and Firebase.

  • 102 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • Catalog plugins run commands, edit files and call outside services under their own rules.
  • Some MCP servers work with Slack and third-party social networks.
All reasons and checks

2389-research/claude-plugins

Install

Manual install

/plugin marketplace add 2389-research/claude-plugins

Then `/plugin install simmer@2389-research` or another plugin from the catalog.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Catalog plugins run commands, edit files and call outside services under their own rules.
  • Some MCP servers work with Slack and third-party social networks.

This is third-party code. Review the repository files before installing.

What it does

The repository publishes a `marketplace.json` catalog from which Claude Code installs the 2389 team plugins. The plugins themselves live in separate repositories of the organization. The list holds development workflows (CSS with Tailwind, Firebase, fast code generation, reverse engineering of ELF binaries), quality checks (end-to-end tests without mocks, a pre-commit sanity pass, documentation audits, reviewer panels) and business skills such as meeting transcript summaries. Four more MCP servers connect through Claude Code only: a journal, a social network for agents, a Slack integration and a server that alters agent behavior through prompts. Some plugins install in any agent with `npx skills add`.

Who it is for. Teams on Claude Code that want ready development and review workflows rather than one standalone skill.

Good fit when

  • A team wants one plugin set for CSS, Firebase and tests that installs with one command.
  • Changes need an independent second look before a commit.
  • A task should be tried several ways at once and the best one chosen.
  • Meeting transcripts must be turned into structured summaries in a batch.

Not a fit when

  • One narrow skill is enough and a 28-item catalog is excessive.
  • The agent is another one and a plugin needs an MCP server; servers install through Claude Code only.
  • Security rules forbid connecting third-party MCP servers to Slack or mail.

Example request

Add the 2389 Research marketplace and install the simmer plugin, then show how it improves a draft.

Limitations

The repository is a showcase: judge each plugin by its own repository code. MCP servers install in Claude Code only and have no skills for `npx`. Some plugins call outside services (Cerebras for fast generation, Slack, social networks), each with its own key requirements. The list includes a server that alters agent behavior through prompts, so review its purpose and consequences before installing. The repository also holds private journal notes that are worth ignoring.

How to disable. Run `/plugin uninstall <name>@2389-research` for a plugin and `/plugin marketplace remove 2389-research` for the whole catalog.

FAQ

How do I add the marketplace?

In Claude Code run `/plugin marketplace add 2389-research/claude-plugins`, then `/plugin install` with the plugin name and the `@2389-research` suffix.

Can a plugin be installed in Cursor or Codex?

Yes, for plugins with skills: `npx skills add 2389-research/simmer`. The four MCP servers have no such route.

Where is the plugin code?

In separate repositories of the 2389-research organization; the catalog only links to them in `marketplace.json`.

What categories are there?

Meta plugins, development, testing and quality, business and strategy, utilities and MCP servers. The README has the full list with descriptions.

Is there a catalog website?

Yes, `skills.2389.ai`: the page is generated from `marketplace.json` with `npm run generate`.

Discussion

No questions or reviews yet.

Plugins

A marketplace of 18 Claude Code plugins: access to blocked pages, second-model review, design systems from a site, research and planning

PluginBroad access1.3KRepository stars

MadAppGang's Claude Code plugin marketplace: agents and commands for a React frontend and a Bun backend

PluginExtended access288Repository stars

Plugins for git, Python and accessibility in one place: 400+ skills, subagents and hooks against dangerous agent commands.

PluginExtended access59Repository stars

A marketplace of eight Claude Code plugins: session memory, research, commits, skill authoring and more.

PluginExtended access275Repository stars

A marketplace of Claude Code plugins for engineering workflows: feature planning, tests, review, git automation and a code execution runtime

PluginExtended access694Repository stars

A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work

PluginExtended access596Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
2389 Research Plugins (this card)no102
Claude Plugins Communityno4,871curated community plugins; this is the own catalog of a single team, 2389
Agentic Plugin Marketplace by wshobsonno42,418a large set of plugins, agents and commands; this is 28 plugins from one team with a catalog site

README in short

The README lists plugins by group and two install routes. A plugin is added by creating a repository in the organization and an entry in `marketplace.json`; the catalog page is built by a script.

README badge

Report a problem