CoolPlugz

An MCP orchestrator that ensures Claude Code delivers your tasks without your constant supervision.

CoolPlugz is an MCP (Model Context Protocol) server for engineers who are tired of tab-hopping, re-prompting, and babysitting AI. Stay in Claude. CoolPlugz gathers context from Jira, Slack, GitHub, and Notion, engineers the prompt, runs the task, and delivers PRs, CI fixes, and Slack drafts - so you work less, save mental energy, and avoid AI fatigue and context-switching spirals.

Website: coolplugz.com

Coolplugz - Ships merge-ready code and handles your Slack

Live dashboard - tasks, PRs, execution log, and updates to share

Loop Engineering

State-machine-driven orchestration for autonomous Jira → GitHub → PR workflows over MCP. Every tool response carries structured loop metadata via _meta — Claude Code reads it to determine the next action instead of parsing free text.

01 - System architecture

02 - Loop state machine

03 - Loop metadata shape

What CoolPlugz is

CoolPlugz is not another chat wrapper. It is a paid MCP connector that:

Gives each customer a unique MCP URL (minted after purchase)
Fetches live context from your engineering tools
Builds structured prompts (CRISPE-style) so Claude gets trustworthy inputs
Executes end-to-end - code, PRs, CI, Slack replies — from a single conversation

You connect once in Claude (web or desktop). After that, plain-English commands replace hours of manual context gathering.

Who it is for

Senior / staff engineers shipping daily across Jira + GitHub + Slack
Remote devs drowning in notifications and standup prep
Solopreneurs & contractors who need merge-ready output without brain fry from constant context switching
Teams evaluating MCP workflows before rolling out org-wide (Enterprise)

If you spend more time feeding context to AI than doing the work, CoolPlugz is built for you.

The problem we solve

Pain	CoolPlugz answer
AI fatigue - endless prompt → fix → re-prompt loops	One `@RUN` completes a full ticket hands-off
Context switching - Jira tab, Slack tab, GitHub tab	One dashboard, one MCP, one chat
AI spirals - model drifts without grounded context	Context fetched from your real tools before every run
Mental load - “what was I doing on PROJ-124?”	Live task board + execution log in Claude
Low-quality AI output	CRISPE prompt engineering baked in per task

Goal: deliver high-quality code and updates by working less — not by typing more prompts.

How it works (high level)

You (Claude)          CoolPlugz MCP              Your tools
    │                      │                        │
    │  "Show my dashboard" │── fetch ──────────────►│ Jira · GitHub · Slack · Notion
    │                      │◄── context ────────────│
    │◄── dashboard UI ─────│                        │
    │                      │                        │
    │  "Run"               │── sync + execute ─────►│ tickets → PRs → CI → Slack drafts
    │◄── results ──────────│                        │

1. Unique MCP URL per user

After checkout, each customer receives a private MCP endpoint, for example:

https://api.coolplugz.com/mcp/your-unique-key-here

Free trial — 7-day access, full integration stack
Pro — persistent URL for the billing period, unlimited orchestration
URLs are not shared — one key per account

2. Context fetching

When you say "Hi Coolplugz, run my tasks for the day", CoolPlugz:

Pulls open Jira tickets assigned to you
Scans linked GitHub repos, open PRs, and CI status
Reads Slack mentions and threads that need replies
Optionally syncs Notion docs linked to projects

All of this feeds into your Claude Code session — no copy-paste between tools.

3. Session orchestration

CoolPlugz guides your Claude Code session with structured context and workflow steps:

Context — ticket description, acceptance criteria, related PRs
Workflow — implementation steps derived from ticket + repo state
Conventions — your repo patterns, stack, and CI constraints

You never assemble this manually. CoolPlugz orchestrates so Claude Code works from ground truth, not guesswork.

4. Task delivery

CoolPlugz orchestrates Claude Code through:

Code changes and branch/PR creation
CI awareness and fix suggestions
Slack draft replies for stakeholders
Status updates ready to approve and send

You stay in Claude Code. CoolPlugz keeps the session on track.

Pricing

Plan	Price	What you get
Free trial	$0 / 7 days	Full integration stack — Jira, GitHub, Notion, Slack, PR & CI workflow
Pro	$17 / mo	Unlimited usage, multi-repo tasks, developer insights
Pro annual	$147 / yr	Same as Pro, ~28% savings
Enterprise	Custom	Multi-seat, CI/CD rollout, SSO — contact sales

Referral program

Developers can earn 15% revenue share when friends subscribe — friends get 15% off. Details on the homepage Make money with CoolPlugz section.

Access model

Free trial: 7 days, no credit card — one trial per account
Pro: unlimited orchestration while subscribed
Manage your plan and MCP setup at coolplugz.com/app

Usage caps (if any) are enforced by the MCP service — not tracked as credits in the web app.

MCP setup — connect CoolPlugz to Claude

After starting your trial or subscribing, open your install page (linked from account or /premium/unique-mcp-url). Copy your unique URL, then choose web or desktop.

Option A — Claude web (easiest)

Go to claude.ai → Settings → Connectors → Add → Custom connector
Name it coolplugz
Paste your unique MCP URL → Add

Option B — Claude Desktop (JSON config)

Settings → Developer → Edit Config
Open claude_desktop_config.json:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Paste this JSON (replace the URL with yours):

{
  "mcpServers": {
    "coolplugz": {
      "url": "https://api.coolplugz.com/mcp/your-unique-key-here",
      "transport": "http"
    }
  }
}

Save, quit Claude Desktop completely, then reopen

Company email on Claude? If your org blocks custom MCPs on a work Claude account, sign in with a personal Claude email, connect CoolPlugz there, then authorize Jira/GitHub/Slack with your work accounts when prompted.

Connect your tools

Type in Claude:

Show my dashboard

CoolPlugz shows Connect buttons for Jira, GitHub, Notion, and Slack. Click each, authorize in the popup, close the tab. Done — one time per tool.

Commands to use in Claude

Plain English — no ticket IDs required for most flows:

Say this	What happens
`Show my dashboard`	Syncs tools; shows tasks, PRs, Slack drafts
`Run`	Works your incomplete Jira tickets — PRs, CI, Slack
`What's blocking my tasks?`	Re-analyzes stuck or failing work
`Show task PROJ-42`	Deep dive on one ticket
`Reject PROJ-42 and redo it`	Re-run with your feedback
`Refresh Slack`	Latest mentions + draft replies
`Refetch and rerun`	Pull fresh context and execute again

Works on Claude web and desktop. Connect once, stays connected.

What the dashboard shows

From your MCP-connected Claude session (and the CoolPlugz dashboard UI):

All tasks — Jira tickets with status, CI, linked PRs
Execution log — live feed while a run is in progress
Updates to share — standup-ready summary for calls
Pull requests — open PRs with CI pass/fail
Slack — mentions scanned, replies drafted

See the dashboard screenshot at the top of this README.

Architecture (public overview)

Piece	Role
coolplugz.com (this repo)	Marketing, auth, Stripe billing, MCP URL provisioning, usage ledger
CoolPlugz MCP server	Context sync, prompt engineering, task execution, per-user keys
Claude	Your interface — you chat; CoolPlugz is the connector
Jira · GitHub · Slack · Notion	Source-of-truth context

Each paying user gets a unique MCP key. The website provisions the key after payment; the MCP server enforces run limits and TTL.

Marketing & content hub

Use this README as the single source of truth for external messaging. Align all copy with:

Tagline: Ships merge-ready code and handles your Slack in minutes
Trial pitch: 7-day free trial — full integration stack, no card required
Pro pitch: 10 tasks/month for engineers shipping every day
Emotional hooks: less context switching, less AI fatigue, more mental energy
Proof points: CRISPE prompts, live Jira/GitHub/Slack sync, approve & submit workflow

Official links

Channel	URL
Website	coolplugz.com
Pricing	coolplugz.com/pricing
Guides (SEO)	coolplugz.com/guides
LinkedIn	linkedin.com/company/coolplugz
GitHub	github.com/adaOctopus/claude-plugins-app
X	@CryptoSympozium

Screenshot assets (for posts & docs)

File	Use
`src/assets/coolpreview.png` → `npm run sync:og`	Social / OG thumbnail — generates `public/social-preview.jpg` (1200×630) for Twitter/X, LinkedIn, Slack, iMessage
`public/marketing/dashboard.jpg`	Live dashboard UI
`public/marketing/loop-engineering/01-system-architecture.png`	Loop Engineering — system architecture
`public/marketing/loop-engineering/02-loop-state-machine.png`	Loop Engineering — state machine
`public/marketing/loop-engineering/03-loop-metadata-shape.png`	Loop Engineering — `_meta.loop` JSON shape
`public/guides/claude-web-connector.png`	Web MCP setup
`public/guides/claude-desktop-edit-config.png`	Desktop JSON setup

Repository note

This repository is the CoolPlugz marketing & billing website (Next.js 15, App Router, TypeScript). The MCP execution server is a separate deployment. Operational runbooks and internal configuration are not published in this public README.

For SEO operations and partner promo internals, see docs/seo-ops.md and docs/partner-promos.md (no secrets — admin access required at runtime).

Name		Name	Last commit message	Last commit date
docs		docs
guide		guide
public		public
scripts		scripts
src		src
.cool.sh.swo		.cool.sh.swo
.gitignore		.gitignore
AGENTS.md		AGENTS.md
CLAUDE.md		CLAUDE.md
README.md		README.md
cool.sh		cool.sh
eslint.config.mjs		eslint.config.mjs
next.config.ts		next.config.ts
package-lock.json		package-lock.json
package.json		package.json
postcss.config.mjs		postcss.config.mjs
tsconfig.json		tsconfig.json

Navigation Menu

Repository navigation

About

Repository files navigation

CoolPlugz

Loop Engineering

What CoolPlugz is

Who it is for

The problem we solve

How it works (high level)

1. Unique MCP URL per user

2. Context fetching

3. Session orchestration

4. Task delivery

Pricing

Referral program

Access model

MCP setup — connect CoolPlugz to Claude

Option A — Claude web (easiest)

Option B — Claude Desktop (JSON config)

Connect your tools

Commands to use in Claude

What the dashboard shows

Architecture (public overview)

Marketing & content hub

Official links

Screenshot assets (for posts & docs)

Repository note

License

About

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

CoolPlugz

Loop Engineering

What CoolPlugz is

Who it is for

The problem we solve

How it works (high level)

1. Unique MCP URL per user

2. Context fetching

3. Session orchestration

4. Task delivery

Pricing

Referral program

Access model

MCP setup — connect CoolPlugz to Claude

Option A — Claude web (easiest)

Option B — Claude Desktop (JSON config)

Connect your tools

Commands to use in Claude

What the dashboard shows

Architecture (public overview)

Marketing & content hub

Official links

Screenshot assets (for posts & docs)

Repository note

License

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages