CoolPlugz

CoolPlugz is a paid MCP (Model Context Protocol) connector built for engineers who are tired of tab-hopping, re-prompting, and babysitting AI coding agents. It connects to Claude Code and autonomously gathers context from Jira, Slack, GitHub, and Notion, then engineers structured prompts and executes tasks end-to-end — delivering merge-ready PRs, CI fixes, and Slack drafts from a single conversation. The project is developed by CoolPlugz Inc. and is actively maintained as of mid-2026.

What It Is

CoolPlugz is an MCP orchestrator that sits between Claude Code and a developer's engineering toolchain. Rather than requiring developers to manually copy-paste context between tools, CoolPlugz fetches live data from Jira tickets, GitHub repos, Slack threads, and Notion docs, then builds CRISPE-style structured prompts so Claude Code works from ground truth instead of guesswork. Each paying user receives a unique private MCP endpoint URL that connects directly to Claude (web or desktop). The core loop follows Anthropic's agentic pattern: Gather → Act → Verify → Repeat, implemented as a state machine that carries structured _meta.loop metadata on every tool response so Claude can determine the next action without parsing free text.

How the Orchestration Loop Works

CoolPlugz implements what it calls "Loop Engineering" — a state-machine-driven orchestration model for autonomous Jira → GitHub → PR workflows. The loop progresses through states (IDLE → EXECUTING → PUSHED → PR_OPEN → DONE) with built-in self-correction for CI failures and review comments. Key mechanics include:

• Context fetching: Pulls open Jira tickets, linked GitHub repos, open PRs, CI status, Slack mentions, and Notion docs before every run
• Prompt engineering: Applies CRISPE-style prompt construction so Claude receives structured, trustworthy inputs
• Task execution: Orchestrates code changes, branch/PR creation, CI awareness, and Slack draft replies
• Approve & submit / Reject & redo: Developer reviews results in chat and either approves (merges PR, posts Slack drafts, closes Jira ticket) or rejects with feedback for a full context re-run

Setup Path

After starting a trial or subscribing, users receive a unique MCP URL (e.g., https://api.coolplugz.com/mcp/your-unique-key-here). Connection options include Claude web (Settings → Connectors → Add → Custom connector) or Claude Desktop via a JSON config file. Tool authorization for Jira, GitHub, Notion, and Slack is done once via OAuth popups triggered from within the Claude chat interface. Plain-English commands like "Show my dashboard" or "Run" drive the entire workflow — no ticket IDs required for most flows.

Target Audience

CoolPlugz is positioned for developers who spend more time feeding context to AI than doing the work itself:

• Senior/staff engineers shipping daily across Jira, GitHub, and Slack
• Remote developers dealing with notification overload and standup prep
• Solopreneurs and contractors managing multiple client contexts simultaneously
• Engineering teams evaluating MCP workflows before org-wide rollout (Enterprise tier)

The tool also includes a referral program where developers earn 15% revenue share when referred engineers subscribe, with referred users receiving 15% off — per the CoolPlugz homepage.

Architecture and Deployment Model

The public GitHub repository (adaOctopus/claude-plugins-app) contains the marketing and billing website built with Next.js 15, App Router, and TypeScript. The MCP execution server is a separate, non-public deployment. Each paying user gets a unique MCP key provisioned by the website after payment; the MCP server enforces run limits and TTL. The architecture separates concerns across: the CoolPlugz website (auth, Stripe billing, MCP URL provisioning), the MCP server (context sync, prompt engineering, task execution), Claude as the user interface, and the source-of-truth tools (Jira, GitHub, Slack, Notion).

Update: Active Development as of August 2026

The GitHub repository was created on June 29, 2026, and last pushed on August 22, 2026, indicating active early-stage development. The README describes the repository as the marketing and billing website, with the MCP execution server as a separate deployment. The product is live with a 7-day free trial (no credit card required) and a Pro annual plan, signaling a production-ready launch phase rather than a beta or waitlist stage.