@aipermission/mcp 0.2.16 → 0.2.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -7
- package/dist/resources/aipermission-operator/SKILL.md +4 -0
- package/package.json +1 -1
- package/server.json +2 -2
package/README.md
CHANGED
|
@@ -8,8 +8,8 @@ credentials, or other connector secrets.
|
|
|
8
8
|
|
|
9
9
|
The gateway is intentionally local-only. Run it on the developer machine and
|
|
10
10
|
keep the URL on `localhost`; remote systems are connector targets, not places
|
|
11
|
-
to host the gateway for LAN or internet users. SSH, Postgres,
|
|
12
|
-
Docker, and Kubernetes are built-in connectors that use the same
|
|
11
|
+
to host the gateway for LAN or internet users. SSH, Postgres, ClickHouse,
|
|
12
|
+
Redis / Valkey, RabbitMQ, Kafka / Redpanda, S3, Docker, and Kubernetes are built-in connectors that use the same
|
|
13
13
|
target/profile/action permission model as future connectors.
|
|
14
14
|
|
|
15
15
|

|
|
@@ -65,8 +65,8 @@ The generated MCP config contains a bearer token. Keep it private. For project-l
|
|
|
65
65
|
- `get_vault_action_request`
|
|
66
66
|
- `cancel_vault_action_request`
|
|
67
67
|
|
|
68
|
-
All integration work goes through connector targets. SSH, Postgres,
|
|
69
|
-
RabbitMQ, Docker, Kubernetes, and future connectors share the same model: target,
|
|
68
|
+
All integration work goes through connector targets. SSH, Postgres, ClickHouse,
|
|
69
|
+
Redis / Valkey, RabbitMQ, Kafka / Redpanda, S3, Docker, Kubernetes, and future connectors share the same model: target,
|
|
70
70
|
credential profile, connector action, token action permission, approval,
|
|
71
71
|
history, and audit.
|
|
72
72
|
|
|
@@ -99,9 +99,12 @@ table, and bounded read-only query actions. Postgres targets can connect
|
|
|
99
99
|
directly from the gateway or over an SSH connector profile when the database is
|
|
100
100
|
reachable only from a remote server.
|
|
101
101
|
|
|
102
|
-
For Redis, call `get_connector_actions(target_ref)` to discover
|
|
103
|
-
browser actions such as `scan_keys`, `get_key`, `set_string`,
|
|
104
|
-
`delete_keys`.
|
|
102
|
+
For Redis or Valkey, call `get_connector_actions(target_ref)` to discover
|
|
103
|
+
bounded key-browser actions such as `scan_keys`, `get_key`, `set_string`,
|
|
104
|
+
`expire_key`, and `delete_keys`. Both products intentionally use the `redis`
|
|
105
|
+
connector kind and target-ref prefix; no separate Valkey MCP tool family is
|
|
106
|
+
required. The current connector uses RESP2 against one configured endpoint and
|
|
107
|
+
does not provide Cluster or Sentinel routing.
|
|
105
108
|
|
|
106
109
|
For RabbitMQ, call `get_connector_actions(target_ref)` to discover queue
|
|
107
110
|
browser actions such as `overview`, `list_vhosts`, `list_queues`, `get_queue`,
|
|
@@ -109,6 +112,12 @@ browser actions such as `overview`, `list_vhosts`, `list_queues`, `get_queue`,
|
|
|
109
112
|
previews and published payloads can contain secrets or customer data; use short
|
|
110
113
|
reasons and prefer approval-required access until the workflow is trusted.
|
|
111
114
|
|
|
115
|
+
For Kafka or Redpanda, call `get_connector_actions(target_ref)` to discover
|
|
116
|
+
cluster, topic, consumer-group, lag, and bounded message-read actions. Message
|
|
117
|
+
reads use explicit partition assignment, never join a consumer group, and
|
|
118
|
+
never commit offsets. Payloads can contain sensitive application data, so keep
|
|
119
|
+
these reads in Prompt mode until the workflow is trusted.
|
|
120
|
+
|
|
112
121
|
For Docker, call `get_connector_actions(target_ref)` to discover bounded
|
|
113
122
|
actions such as `docker_version`, `list_containers`, `list_images`,
|
|
114
123
|
`list_networks`, `list_volumes`, `inspect_container`, `container_logs`,
|
|
@@ -53,6 +53,10 @@ Peek a RabbitMQ queue after the operator approved payload inspection. Publish
|
|
|
53
53
|
RabbitMQ messages only when the operator explicitly asked for a write.
|
|
54
54
|
```
|
|
55
55
|
|
|
56
|
+
For Kafka / Redpanda, discover topics before describing partitions or reading
|
|
57
|
+
messages. Keep message reads bounded, prefer Prompt because payloads can be
|
|
58
|
+
sensitive, and remember that read actions never join groups or commit offsets.
|
|
59
|
+
|
|
56
60
|
Avoid vague reasons:
|
|
57
61
|
|
|
58
62
|
```text
|
package/package.json
CHANGED
package/server.json
CHANGED
|
@@ -3,12 +3,12 @@
|
|
|
3
3
|
"name": "io.github.aipermission/aipermission-mcp",
|
|
4
4
|
"title": "AIPermission",
|
|
5
5
|
"description": "Local-first MCP bridge for the AIPermission gateway.",
|
|
6
|
-
"version": "0.2.
|
|
6
|
+
"version": "0.2.18",
|
|
7
7
|
"packages": [
|
|
8
8
|
{
|
|
9
9
|
"registryType": "npm",
|
|
10
10
|
"identifier": "@aipermission/mcp",
|
|
11
|
-
"version": "0.2.
|
|
11
|
+
"version": "0.2.18",
|
|
12
12
|
"transport": {
|
|
13
13
|
"type": "stdio"
|
|
14
14
|
}
|