javaperf 1.0.2 → 1.0.4

package/.github/workflows/publish.yml

@@ -1,9 +1,9 @@
-name: Publish to npm
+name: Publish to npm and MCP Registry
 
 on:
   push:
     branches: [main]
-    paths: ["package.json"]
+    paths: ["package.json", "server.json"]
   workflow_dispatch:
 
 jobs:
@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       contents: read
-      id-token: write  # Required for npm provenance
+      id-token: write  # Required for npm provenance and MCP Registry OIDC
     steps:
       - uses: actions/checkout@v4
 
@@ -25,6 +25,19 @@ jobs:
       - run: npm run build
       - run: npm run lint
 
-      - run: npm publish --provenance
+      - name: Publish to npm
+        id: npm
+        run: npm publish --provenance
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        continue-on-error: true
+
+      - name: Install mcp-publisher
+        run: |
+          curl -sL "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
+
+      - name: Authenticate to MCP Registry
+        run: ./mcp-publisher login github-oidc
+
+      - name: Publish to MCP Registry
+        run: ./mcp-publisher publish

package/AGENTS.md

@@ -0,0 +1,36 @@
+# AGENTS.md
+
+## Cursor Cloud specific instructions
+
+### Overview
+
+This is `javaperf` — a stdio-based MCP (Model Context Protocol) server for profiling Java applications via JDK utilities (`jcmd`, `jfr`, `jps`). It is a single-package TypeScript project (not a monorepo).
+
+### Development commands
+
+See `package.json` scripts. Key commands:
+
+- **Lint:** `npm run lint` (ESLint on `src/`)
+- **Build:** `npm run build` (TypeScript compiler → `dist/`)
+- **Dev mode:** `npm run dev` (runs via `tsx`)
+- **Production:** `npm start` (runs built `dist/index.js`)
+- **MCP Inspector:** `npm run inspector` (interactive debugging UI)
+
+### Testing the MCP server
+
+The server uses stdio transport (no HTTP port). To test it, pipe JSON-RPC messages via stdin:
+
+```bash
+printf '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}\n{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}\n' | node dist/index.js
+```
+
+There are no automated tests in this codebase. The CI pipeline only runs `lint` and `build`.
+
+### Runtime dependency
+
+JDK 8u262+ or 11+ must be installed for the profiling tools (`jps`, `jcmd`, `jfr`) to work at runtime. JDK is auto-detected via `JAVA_HOME` or `PATH`. The Cloud VM has OpenJDK 21 pre-installed at `/usr/bin/java`.
+
+### Gotchas
+
+- `npm run dev` blocks on stdin (it's a stdio server) — use piped input or `timeout` for non-interactive testing.
+- The `recordings/` directory is created at runtime by the server when profiling; it does not exist in the repo.

package/README.md

@@ -9,6 +9,27 @@ Enables AI assistants to diagnose performance, analyze threads, and inspect JFR
 📦 **Install**: `npm install -g javaperf` or use via npx  
 🌐 **npm**: https://www.npmjs.com/package/javaperf
 
+## How to connect to Claude Desktop / IDE
+
+Add the server to your MCP config. Example for **claude_desktop_config.json**:
+
+**macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`  
+**Windows:** `%APPDATA%\Claude\claude_desktop_config.json`  
+**Linux:** `~/.config/Claude/claude_desktop_config.json`
+
+```json
+{
+  "mcpServers": {
+    "javaperf": {
+      "command": "npx",
+      "args": ["-y", "javaperf"]
+    }
+  }
+}
+```
+
+For **Cursor IDE**: Settings → Features → Model Context Protocol → Edit Config, then add the same block inside `mcpServers`. See the [Integration](#integration) section for more options (local dev, custom `JAVA_HOME`, etc.).
+
 ## Requirements
 
 - **Node.js** v18+

package/README_RU.md

@@ -9,6 +9,27 @@
 📦 **Установка**: `npm install -g javaperf` или через npx  
 🌐 **npm**: https://www.npmjs.com/package/javaperf
 
+## Как подключить к Claude Desktop / IDE
+
+Добавьте сервер в конфиг MCP. Пример для **claude_desktop_config.json**:
+
+**macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`  
+**Windows:** `%APPDATA%\Claude\claude_desktop_config.json`  
+**Linux:** `~/.config/Claude/claude_desktop_config.json`
+
+```json
+{
+  "mcpServers": {
+    "javaperf": {
+      "command": "npx",
+      "args": ["-y", "javaperf"]
+    }
+  }
+}
+```
+
+Для **Cursor IDE**: Settings → Features → Model Context Protocol → Edit Config, затем добавьте тот же блок в `mcpServers`. Подробнее в разделе [Интеграция](#интеграция).
+
 ## Требования
 
 - **Node.js** v18+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "javaperf",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "repository": {
     "type": "git",
     "url": "https://github.com/theSharque/mcp-jperf.git"
@@ -31,5 +31,12 @@
     "tsx": "^4.0.0",
     "typescript": "^5.0.0",
     "typescript-eslint": "^8.56.1"
-  }
-}
+  },
+  "mcpName": "io.github.theSharque/javaperf",
+  "keywords": [
+    "mcp",
+    "java",
+    "performance",
+    "profiling"
+  ]
+}

package/server.json

@@ -0,0 +1,21 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.theSharque/javaperf",
+  "description": "Java profiling MCP via jcmd/jfr/jps. Diagnose performance, analyze threads, inspect JFR recordings.",
+  "title": "javaperf",
+  "repository": {
+    "url": "https://github.com/theSharque/mcp-jperf",
+    "source": "github"
+  },
+  "version": "1.0.4",
+  "packages": [
+    {
+      "registryType": "npm",
+      "identifier": "javaperf",
+      "version": "1.0.4",
+      "transport": {
+        "type": "stdio"
+      }
+    }
+  ]
+}