By julianjab
Slack bridge MCP server: subscribe to channels, claim and reply to messages, read threads via daemon + MCP architecture.
Centralized AI toolbox for development teams. Ships shared Claude Code agents, skills, and the Slack bridge MCP server as a single plugin.
pnpm install # install workspace deps (Biome + slack-bridge)
pnpm build # build TypeScript packages
pre-commit install # set up commit-msg + pre-commit hooks
.
├── .claude-plugin/
│ ├── plugin.json # Root ia-tools plugin manifest
│ └── marketplace.json
├── agents/ # Stack-agnostic agent definitions
├── skills/ # Reusable Claude Code skills
├── plugins/ # Nested Claude plugins (workspace packages)
│ ├── slack-bridge/ # Self-contained: src/, dist/, .mcp.json
│ │ ├── .claude-plugin/plugin.json
│ │ ├── .mcp.json # Points at ${CLAUDE_PLUGIN_ROOT}/dist/mcp-server.js
│ │ ├── package.json # @ia-tools/slack-bridge
│ │ ├── src/ # Daemon + MCP server (TypeScript)
│ │ └── dist/ # Committed build output (shipped to marketplace)
│ └── team-workflow/
├── biome.json # Lint + format config (TS/JS/JSON)
├── .pre-commit-config.yaml
├── pnpm-workspace.yaml
└── tsconfig.base.json
TypeScript packages live under plugins/* and are wired through pnpm-workspace.yaml. Today the only workspace package is plugins/slack-bridge (@ia-tools/slack-bridge). Its build output (plugins/slack-bridge/dist/mcp-server.js) is referenced from the plugin's own .mcp.json via ${CLAUDE_PLUGIN_ROOT}, so the plugin is fully self-contained and ships prebuilt. Staleness between src/ and dist/ is enforced by scripts/check-slack-bridge-dist.sh, which runs as a prebuild check and in CI.
pnpm lint, pnpm lint:fix, pnpm formatcommit-msgInstall hooks once:
pre-commit install --install-hooks
agents/ — 11 stack-agnostic agent definitions (orchestrator, architect, leads, specialists)skills/ — /worktree, /commit, /review, /pr, /deliver, /team, /ship, /sync-docs, /pr-review, /security-audit, /test-generationAGENTS.md — read natively by Cursor, Windsurf, Copilot, Codex, Amp, DevinCLAUDE.md — Claude Code specific (imports AGENTS.md)Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub julianjab/ia-tools --plugin slack-bridgeSet up the redhat-community-ai-tools Slack MCP server for use with Claude Code
Drives a full feature-development workflow (clarify -> design -> plan -> execute -> PR -> test) over Slack via the claude-slack-bridge daemon. Ships /process-setup for one-time per-repo configuration and /process for clarification + handoff to the daemon's workflow engine.
Connect Claude Managed Agents to messaging channels like Slack — initialize Slack integrations and run the bridging server directly from Claude Code
Start, stop, join, resume, and manage Claude Code sessions mirrored to Slack via slaude
Agent configuration utilities - project assimilation, config auditing, teammate definitions, MCP management, and hooks configuration
Turn any folder of projects into an AI-orchestrated workspace with Slack and Telegram integration. Creates a Project Orchestrator (PO) that routes requests, plans execution with dependency-aware phases, delegates to workspace-level Claude agents, and returns structured results.