Skip to content

Commit 4085397

Browse files
Nima21claude
andcommitted
feat: remove MCP registry publishing and rebrand for NIMBUS21
- Removed OIDC-based MCP registry publish workflow (not needed) - Updated README with NIMBUS21 branding and marketing content - Added disclaimer about unofficial fork - Updated all package references to @nimbus21.ai/chrome-devtools-mcp - Enhanced SEO with keywords: AI automation, browser automation, DevTools, MCP - Added NIMBUS21 company links (nimbus21.com, nimbus21.ai) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
1 parent 48eba08 commit 4085397

2 files changed

Lines changed: 27 additions & 59 deletions

File tree

.github/workflows/publish-to-npm-on-tag.yml

Lines changed: 0 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -38,45 +38,3 @@ jobs:
3838
run: npm publish --access public
3939
env:
4040
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
41-
42-
publish-to-mcp-registry:
43-
runs-on: ubuntu-latest
44-
needs: publish-to-npm
45-
permissions:
46-
id-token: write # Required for OIDC authentication with MCP registry
47-
contents: read
48-
steps:
49-
- name: Check out repository
50-
uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
51-
with:
52-
fetch-depth: 2
53-
54-
- name: Set up Node.js
55-
uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
56-
with:
57-
cache: npm
58-
node-version-file: '.nvmrc'
59-
registry-url: 'https://registry.npmjs.org'
60-
61-
# Ensure npm 11.5.1 or later is installed
62-
- name: Update npm
63-
run: npm install -g npm@latest
64-
65-
- name: Install dependencies
66-
run: npm ci
67-
68-
- name: Build
69-
run: npm run build
70-
71-
- name: Bump
72-
run: npm run sync-server-json-version
73-
74-
- name: Install MCP Publisher
75-
run: |
76-
curl -L "https://github.com/modelcontextprotocol/registry/releases/download/v1.1.0/mcp-publisher_1.1.0_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
77-
78-
- name: Login to MCP Registry
79-
run: ./mcp-publisher login github-oidc
80-
81-
- name: Publish to MCP Registry
82-
run: ./mcp-publisher publish

README.md

Lines changed: 27 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,18 @@
1-
# Chrome DevTools MCP
1+
# Chrome DevTools MCP - Enhanced by NIMBUS21
22

3-
[![npm chrome-devtools-mcp package](https://img.shields.io/npm/v/chrome-devtools-mcp.svg)](https://npmjs.org/package/chrome-devtools-mcp)
3+
[![npm @nimbus21.ai/chrome-devtools-mcp package](https://img.shields.io/npm/v/@nimbus21.ai/chrome-devtools-mcp.svg)](https://npmjs.org/package/@nimbus21.ai/chrome-devtools-mcp)
44

5-
`chrome-devtools-mcp` lets your coding agent (such as Gemini, Claude, Cursor or Copilot)
5+
> **Note:** This is an **unofficial community-maintained fork** of the original Chrome DevTools MCP server, enhanced and modified by the **NIMBUS21 Team**. This package is not affiliated with or endorsed by Google or the Chrome DevTools team.
6+
7+
## 🚀 Powered by NIMBUS21
8+
9+
This enhanced version is brought to you by **[NIMBUS21](https://nimbus21.com)** - a leading technology innovation company specializing in AI-powered automation, browser automation solutions, and enterprise software development. Visit [nimbus21.ai](https://nimbus21.ai) to explore our cutting-edge AI tools, automation platforms, and developer services.
10+
11+
**NIMBUS21** delivers advanced browser automation frameworks, intelligent testing solutions, and AI-driven development tools for modern web applications. Our expertise in Chrome automation, DevTools integration, and Model Context Protocol (MCP) implementations helps developers and enterprises build more reliable, performant, and intelligent software solutions.
12+
13+
---
14+
15+
`@nimbus21.ai/chrome-devtools-mcp` lets your coding agent (such as Gemini, Claude, Cursor or Copilot)
616
control and inspect a live Chrome browser. It acts as a Model-Context-Protocol
717
(MCP) server, giving your AI coding assistant access to the full power of
818
Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.
@@ -42,14 +52,14 @@ Add the following config to your MCP client:
4252
"mcpServers": {
4353
"chrome-devtools": {
4454
"command": "npx",
45-
"args": ["-y", "chrome-devtools-mcp@latest"]
55+
"args": ["-y", "@nimbus21.ai/chrome-devtools-mcp@latest"]
4656
}
4757
}
4858
}
4959
```
5060

51-
> [!NOTE]
52-
> Using `chrome-devtools-mcp@latest` ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
61+
> [!NOTE]
62+
> Using `@nimbus21.ai/chrome-devtools-mcp@latest` ensures that your MCP client will always use the latest version of the NIMBUS21-enhanced Chrome DevTools MCP server.
5363
5464
### MCP Client configuration
5565

@@ -58,7 +68,7 @@ Add the following config to your MCP client:
5868
Use the Claude Code CLI to add the Chrome DevTools MCP server (<a href="https://docs.anthropic.com/en/docs/claude-code/mcp">guide</a>):
5969

6070
```bash
61-
claude mcp add chrome-devtools npx chrome-devtools-mcp@latest
71+
claude mcp add chrome-devtools npx @nimbus21.ai/chrome-devtools-mcp@latest
6272
```
6373

6474
</details>
@@ -74,7 +84,7 @@ claude mcp add chrome-devtools npx chrome-devtools-mcp@latest
7484
using the standard config from above. You can also install the Chrome DevTools MCP server using the Codex CLI:
7585

7686
```bash
77-
codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
87+
codex mcp add chrome-devtools -- npx @nimbus21.ai/chrome-devtools-mcp@latest
7888
```
7989

8090
**On Windows 11**
@@ -88,7 +98,7 @@ args = [
8898
"/c",
8999
"npx",
90100
"-y",
91-
"chrome-devtools-mcp@latest",
101+
"@nimbus21.ai/chrome-devtools-mcp@latest",
92102
]
93103
env = { SystemRoot="C:\\Windows", PROGRAMFILES="C:\\Program Files" }
94104
startup_timeout_ms = 20_000
@@ -116,7 +126,7 @@ Configure the following fields and press `CTR-S` to save the configuration:
116126
- **Server name:** `chrome-devtools`
117127
- **Server Type:** `[1] Local`
118128
- **Command:** `npx`
119-
- **Arguments:** `-y, chrome-devtools-mcp@latest`
129+
- **Arguments:** `-y, @nimbus21.ai/chrome-devtools-mcp@latest`
120130

121131
</details>
122132

@@ -126,7 +136,7 @@ Configure the following fields and press `CTR-S` to save the configuration:
126136
with the standard config from above. You can also install the Chrome DevTools MCP server using the VS Code CLI:
127137

128138
```bash
129-
code --add-mcp '{"name":"chrome-devtools","command":"npx","args":["chrome-devtools-mcp@latest"]}'
139+
code --add-mcp '{"name":"chrome-devtools","command":"npx","args":["@nimbus21.ai/chrome-devtools-mcp@latest"]}'
130140
```
131141
</details>
132142

@@ -135,7 +145,7 @@ Configure the following fields and press `CTR-S` to save the configuration:
135145

136146
**Click the button to install:**
137147

138-
[<img src="https://cursor.com/deeplink/mcp-install-dark.svg" alt="Install in Cursor">](https://cursor.com/en/install-mcp?name=chrome-devtools&config=eyJjb21tYW5kIjoibnB4IC15IGNocm9tZS1kZXZ0b29scy1tY3BAbGF0ZXN0In0%3D)
148+
[<img src="https://cursor.com/deeplink/mcp-install-dark.svg" alt="Install in Cursor">](https://cursor.com/en/install-mcp?name=chrome-devtools&config=eyJjb21tYW5kIjoibnB4IC15IEBuaW1idXMyMS5haS9jaHJvbWUtZGV2dG9vbHMtbWNwQGxhdGVzdCJ9)
139149

140150
**Or install manually:**
141151

@@ -150,13 +160,13 @@ Install the Chrome DevTools MCP server using the Gemini CLI.
150160
**Project wide:**
151161

152162
```bash
153-
gemini mcp add chrome-devtools npx chrome-devtools-mcp@latest
163+
gemini mcp add chrome-devtools npx @nimbus21.ai/chrome-devtools-mcp@latest
154164
```
155165

156166
**Globally:**
157167

158168
```bash
159-
gemini mcp add -s user chrome-devtools npx chrome-devtools-mcp@latest
169+
gemini mcp add -s user chrome-devtools npx @nimbus21.ai/chrome-devtools-mcp@latest
160170
```
161171

162172
Alternatively, follow the <a href="https://github.com/google-gemini/gemini-cli/blob/main/docs/tools/mcp-server.md#how-to-set-up-your-mcp-server">MCP guide</a> and use the standard config from above.
@@ -182,7 +192,7 @@ The same way chrome-devtools-mcp can be configured for JetBrains Junie in `Setti
182192

183193
**Click the button to install:**
184194

185-
[<img src="https://img.shields.io/badge/Visual_Studio-Install-C16FDE?logo=visualstudio&logoColor=white" alt="Install in Visual Studio">](https://vs-open.link/mcp-install?%7B%22name%22%3A%22chrome-devtools%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22chrome-devtools-mcp%40latest%22%5D%7D)
195+
[<img src="https://img.shields.io/badge/Visual_Studio-Install-C16FDE?logo=visualstudio&logoColor=white" alt="Install in Visual Studio">](https://vs-open.link/mcp-install?%7B%22name%22%3A%22chrome-devtools%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22@nimbus21.ai/chrome-devtools-mcp%40latest%22%5D%7D)
186196
</details>
187197

188198
<details>
@@ -301,7 +311,7 @@ Pass them via the `args` property in the JSON configuration. For example:
301311
"chrome-devtools": {
302312
"command": "npx",
303313
"args": [
304-
"chrome-devtools-mcp@latest",
314+
"@nimbus21.ai/chrome-devtools-mcp@latest",
305315
"--channel=canary",
306316
"--headless=true",
307317
"--isolated=true"
@@ -311,7 +321,7 @@ Pass them via the `args` property in the JSON configuration. For example:
311321
}
312322
```
313323

314-
You can also run `npx chrome-devtools-mcp@latest --help` to see all available configuration options.
324+
You can also run `npx @nimbus21.ai/chrome-devtools-mcp@latest --help` to see all available configuration options.
315325

316326
## Concepts
317327

0 commit comments

Comments
 (0)