mcp-aws-manager 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 soybin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/MCP_CLIENT_SETUP.md

@@ -0,0 +1,78 @@
+# MCP Client Setup (stdio)
+
+This project now includes an MCP stdio server wrapper.
+
+- Preferred CLI command: `mcp-aws-manager`
+- Preferred MCP server command: `mcp-aws-manager-mcp`
+- Compatibility aliases still available: `mcp-aws-discover`, `mcp-aws-discover-mcp`
+
+The MCP server exposes these tools:
+
+- `discover_public_ec2_with_pem`
+- `mcp_aws_discover_cli_help`
+
+## 1) Local Repo (recommended for development)
+
+Use this when running directly from this repository.
+
+```json
+{
+  "mcpServers": {
+    "mcp-aws-manager": {
+      "command": "node",
+      "args": [
+        "C:/Users/mybin/gesia/mcp_aws/bin/mcp-aws-manager-mcp.js"
+      ],
+      "cwd": "C:/Users/mybin/gesia/mcp_aws"
+    }
+  }
+}
+```
+
+## 2) Global npm Install
+
+After publishing/installing globally:
+
+```bash
+npm install -g @soybin/mcp-aws-manager
+```
+
+Client config:
+
+```json
+{
+  "mcpServers": {
+    "mcp-aws-manager": {
+      "command": "mcp-aws-manager-mcp"
+    }
+  }
+}
+```
+
+## 3) npx (without global install)
+
+This can be useful for clients that support `npx` commands.
+
+```json
+{
+  "mcpServers": {
+    "mcp-aws-manager": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "-p",
+        "@soybin/mcp-aws-manager",
+        "mcp-aws-manager-mcp"
+      ]
+    }
+  }
+}
+```
+
+## Notes
+
+- The current discovery tool is PEM-based and accepts `pemPath` or `pemPaths` (array).
+- If neither is provided, it auto-discovers `.pem` files from the working directory.
+- AWS credentials/profiles must be available on the machine running the MCP server.
+- Do not pass PEM contents through chat; use a local file path in tool arguments.
+- For scoped public npm packages, publish with `npm publish --access public` (or set `publishConfig.access`).

package/README.md

@@ -0,0 +1,140 @@
+# @soybin/mcp-aws-manager
+
+AWS operations CLI and MCP server package (currently discovery-focused).
+
+## What It Provides
+
+- CLI: `mcp-aws-manager`
+- MCP stdio server: `mcp-aws-manager-mcp`
+
+Current implementation focuses on:
+
+- EC2 public IPv4 inventory discovery
+- PEM fingerprint-based EC2 KeyPair matching
+- Optional SSH reachability checks
+- JSON/CSV output (CLI)
+- MCP tool wrapper for AI clients (stdio)
+
+## Install
+
+```bash
+npm install -g @soybin/mcp-aws-manager
+```
+
+## Quick Start
+
+1. Ensure AWS credentials/profile and a PEM file are available on your machine.
+2. Run a CLI check (explicit PEM path(s) or auto-discovery from current folder):
+
+```bash
+# explicit PEM path
+mcp-aws-manager --pem-path /path/to/key.pem --profiles default
+
+# multiple explicit PEM paths (comma-separated)
+mcp-aws-manager --pem-path /path/to/key1.pem,/path/to/key2.pem --profiles default
+
+# no args: auto-uses all *.pem in current directory
+cd /path/that/contains/pem
+mcp-aws-manager
+```
+
+3. For LLM clients, register the MCP command:
+
+```json
+{
+  "mcpServers": {
+    "mcp-aws-manager": {
+      "command": "mcp-aws-manager-mcp"
+    }
+  }
+}
+```
+
+## CLI Usage
+
+```bash
+mcp-aws-manager --pem-path /path/to/key.pem --profiles default
+
+# if current directory contains .pem files, pemPath is optional
+mcp-aws-manager
+```
+
+Windows PowerShell example:
+
+```powershell
+mcp-aws-manager --pem-path C:\Users\<you>\.ssh\mykey.pem --profiles default
+```
+
+Output format examples:
+
+```bash
+# JSON (default)
+mcp-aws-manager --pem-path /path/to/key.pem --profiles default
+
+# CSV
+mcp-aws-manager --pem-path /path/to/key.pem --profiles default --format csv
+```
+
+Optional SSH reachability check:
+
+```bash
+mcp-aws-manager --pem-path /path/to/key.pem --profiles default --ssh-check
+```
+
+## MCP (LLM Tool) Usage
+
+Run as an MCP stdio server:
+
+```bash
+mcp-aws-manager-mcp
+```
+
+Then configure your MCP-compatible client (Claude Desktop, Cursor, Cline, etc.) to launch that command.
+
+See `MCP_CLIENT_SETUP.md` for ready-to-copy config examples.
+
+### Exposed MCP Tools
+
+- `discover_public_ec2_with_pem`
+- `mcp_aws_discover_cli_help`
+
+Example tool arguments:
+
+```json
+{
+  "pemPaths": [
+    "C:\\Users\\<you>\\.ssh\\key1.pem",
+    "C:\\Users\\<you>\\.ssh\\key2.pem"
+  ],
+  "profiles": ["default"],
+  "noProgress": true
+}
+```
+
+## Requirements
+
+- Node.js `>=18`
+- AWS credentials/profile on the machine running the CLI/MCP server
+- Local PEM file path(s) (current discovery tool is PEM-based)
+
+## Security Notes
+
+- Do not paste PEM contents into LLM chats.
+- Pass only local file paths (`pemPath` or `pemPaths`) to the MCP tool.
+- Keep AWS credentials and PEM keys on the machine running the tool.
+
+## Compatibility Aliases
+
+These legacy commands are also available:
+
+- `mcp-aws-discover`
+- `mcp-aws-discover-mcp`
+
+## Keywords
+
+- `mcp`
+- `model-context-protocol`
+- `aws`
+- `ec2`
+- `inventory`
+- `cli`