@aipermission/mcp 0.2.3 → 0.2.6

package/README.md

@@ -8,11 +8,11 @@ credentials, or other connector secrets.
 
 The gateway is intentionally local-only. Run it on the developer machine and
 keep the URL on `localhost`; remote systems are connector targets, not places
-to host the gateway for LAN or internet users. SSH and Postgres are built-in
-connectors that use the same target/profile/action permission model as future
-connectors.
+to host the gateway for LAN or internet users. SSH, Postgres, Redis, and RabbitMQ are
+built-in connectors that use the same target/profile/action permission model
+as future connectors.
 
-![AIPermission demo: AI installs Uptime Kuma through approval-based SSH access](https://raw.githubusercontent.com/aipermission/aipermission/main/docs/assets/demo/aipermission-demo.gif)
+![AIPermission demo: AI operates through approval-based connector access](https://raw.githubusercontent.com/aipermission/aipermission/main/docs/assets/demo/aipermission-demo.gif)
 
 [Watch the demo video](https://github.com/aipermission/aipermission/releases/download/v0.1.0-rc.1/aipermission-demo.mp4) to see an AI assistant install Uptime Kuma on a VPS while the user approves commands and changes the plan mid-run.
 
@@ -61,7 +61,7 @@ The generated MCP config contains a bearer token. Keep it private. For project-l
 - `call_connector_action`
 - `get_connector_action_request`
 
-All integration work goes through connector targets. SSH, Postgres, and future
+All integration work goes through connector targets. SSH, Postgres, Redis, RabbitMQ, and future
 connectors share the same model: target, credential profile, connector action,
 token action permission, approval, history, and audit.
 
@@ -70,6 +70,21 @@ For SSH, call `get_connector_actions(target_ref)` to discover actions such as
 `start_file_download`. SSH `exec` is intended for non-interactive commands. Use
 the web console for truly interactive work.
 
+For Postgres, call `get_connector_actions(target_ref)` to discover schema,
+table, and bounded read-only query actions. Postgres targets can connect
+directly from the gateway or over an SSH connector profile when the database is
+reachable only from a remote server.
+
+For Redis, call `get_connector_actions(target_ref)` to discover bounded key
+browser actions such as `scan_keys`, `get_key`, `set_string`, `expire_key`, and
+`delete_keys`.
+
+For RabbitMQ, call `get_connector_actions(target_ref)` to discover queue
+browser actions such as `overview`, `list_vhosts`, `list_queues`, `get_queue`,
+`list_bindings`, `peek_messages`, and `publish_message`. Message payload
+previews and published payloads can contain secrets or customer data; use short
+reasons and prefer approval-required access until the workflow is trusted.
+
 Connector responses can include `approval_pending` or `running`. Poll
 `get_connector_action_request(request_id)` until the request reaches a terminal
 status. MCP tool responses never include file contents, gateway temporary paths,

package/dist/resources/aipermission-operator/SKILL.md

@@ -46,6 +46,8 @@ Good reasons:
 Check Docker service state before cleanup.
 Inspect recent kubelet errors on worker node.
 List Postgres schemas before a read-only metadata query.
+Peek a RabbitMQ queue after the operator approved payload inspection. Publish
+RabbitMQ messages only when the operator explicitly asked for a write.
 ```
 
 Avoid vague reasons:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aipermission/mcp",
-  "version": "0.2.3",
+  "version": "0.2.6",
   "mcpName": "io.github.aipermission/aipermission-mcp",
   "description": "Local-first MCP bridge for the aipermission gateway.",
   "license": "AGPL-3.0-only",

package/server.json

@@ -3,12 +3,12 @@
   "name": "io.github.aipermission/aipermission-mcp",
   "title": "AIPermission",
   "description": "Local-first MCP bridge for the AIPermission gateway.",
-  "version": "0.2.3",
+  "version": "0.2.6",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@aipermission/mcp",
-      "version": "0.2.3",
+      "version": "0.2.6",
       "transport": {
         "type": "stdio"
       }