venafi-integration-core 2.0.5 → 2.0.6

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.
Files changed (3) hide show
  1. package/README.md +7 -10
  2. package/bundle.mjs +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -33,23 +33,20 @@ claude mcp add venafi-integration-core -- npx -y venafi-integration-core
33
33
  claude mcp add -s user venafi-integration-core -- npx -y venafi-integration-core
34
34
  ```
35
35
 
36
- For full coverage, add the sibling MCPs relevant to your integration type:
36
+ Then add the sibling MCPs for your integration type:
37
37
 
38
- **Machine connector:**
39
38
  ```bash
40
- claude mcp add venafi-integration-core -- npx -y venafi-integration-core
41
- claude mcp add venafi-connector-machine -- npx -y venafi-connector-machine
39
+ claude mcp add venafi-connector-machine -- npx -y venafi-connector-machine # Machine connector
40
+ claude mcp add venafi-connector-ca -- npx -y venafi-connector-ca # CA connector
41
+ claude mcp add venafi-adaptable-app -- npx -y venafi-adaptable-app # Adaptable driver
42
42
  ```
43
43
 
44
- **CA connector:**
45
- ```bash
46
- claude mcp add venafi-integration-core -- npx -y venafi-integration-core
47
- claude mcp add venafi-connector-ca -- npx -y venafi-connector-ca
48
- ```
44
+ **Add everything** (copy-paste to install the full suite):
49
45
 
50
- **Adaptable app driver:**
51
46
  ```bash
52
47
  claude mcp add venafi-integration-core -- npx -y venafi-integration-core
48
+ claude mcp add venafi-connector-machine -- npx -y venafi-connector-machine
49
+ claude mcp add venafi-connector-ca -- npx -y venafi-connector-ca
53
50
  claude mcp add venafi-adaptable-app -- npx -y venafi-adaptable-app
54
51
  ```
55
52
 
package/bundle.mjs CHANGED
@@ -31229,7 +31229,7 @@ Before writing any code, ask the user for:
31229
31229
 
31230
31230
  1. **Connector type** -- Machine connector or CA connector?
31231
31231
  2. **Target system** -- What system are we integrating with?
31232
- 3. **Connector name** -- What to call it (e.g., \`apache-connector\`, \`digicert-one-ca-connector\`)
31232
+ 3. **Connector name** -- What to call it (e.g., \`apache-connector\`, \`venafi-connector-digicert-one\`)
31233
31233
  4. **Container registry** -- Where will images be pushed?
31234
31234
  - Get the full registry URL (e.g., \`docker.io/yourusername\`, \`ghcr.io/yourusername\`)
31235
31235
  - Confirm the vSatellite's \`registries.yaml\` has auth configured for this registry
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "venafi-integration-core",
3
- "version": "2.0.5",
3
+ "version": "2.0.6",
4
4
  "description": "MCP server providing shared knowledge, templates, and tools for building Venafi integrations (connectors and adaptable drivers)",
5
5
  "main": "bundle.mjs",
6
6
  "type": "module",