venafi-integration-core 2.0.1 → 2.0.2

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 (2) hide show
  1. package/README.md +48 -28
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,23 +1,23 @@
1
- # venafi-connector-core
1
+ # venafi-integration-core
2
2
 
3
- An MCP (Model Context Protocol) server that provides shared knowledge, templates, and tools for building **Venafi TLS Protect Cloud connectors** — both machine connectors and CA connectors.
3
+ An MCP (Model Context Protocol) server that provides shared knowledge, templates, and tools for building **Venafi integrations** — both **TLS Protect Cloud connectors** (Go) and **TPP self-hosted adaptable drivers** (PowerShell).
4
4
 
5
- Use this with Claude Code or any MCP-compatible AI assistant to get expert guidance on connector architecture, manifest schemas, deployment, and troubleshooting.
5
+ Use this with Claude Code or any MCP-compatible AI assistant to get expert guidance on integration architecture, project scaffolding, deployment, and troubleshooting.
6
6
 
7
7
  ## What's Inside
8
8
 
9
9
  | Tool | Description |
10
10
  |---|---|
11
11
  | `get_template` | Go code templates: go.mod, main.go, app.go, web.go, Makefile, Dockerfile, golangci.yaml, .gitignore |
12
- | `scaffold_project` | Complete project structure showing every file needed for a new connector |
12
+ | `scaffold_project` | Complete project structure showing every file needed for a new connector or adaptable driver |
13
13
  | `get_guidance` | Focused guidance on: architecture, manifest, testing, deployment, troubleshooting, certificate-formats, common-mistakes, container-registry, bootstrap |
14
14
  | `get_core_patterns` | DI wiring, handler pattern, payload encryption, error handling, logging |
15
15
 
16
16
  | Resource | Description |
17
17
  |---|---|
18
- | Core Blueprint | Architecture, project structure, dependencies shared by all connectors |
18
+ | Core Blueprint | Architecture, project structure, dependencies shared by all integrations |
19
19
  | Deployment Guide | Container registry, vSatellite, build/push, plugin registration, troubleshooting |
20
- | Known Gaps | 19 documented Venafi platform behaviors learned from production connectors |
20
+ | Known Gaps | 19 documented Venafi platform behaviors learned from production integrations |
21
21
  | Bootstrap Guide | Step-by-step new project setup from Phase 0 (registry) to Phase 5 (deploy) |
22
22
  | Manifest Template | Base manifest.json with shared structure |
23
23
 
@@ -27,64 +27,84 @@ Use this with Claude Code or any MCP-compatible AI assistant to get expert guida
27
27
 
28
28
  ```bash
29
29
  # Add to your project
30
- claude mcp add venafi-connector-core -- npx -y venafi-connector-core
30
+ claude mcp add venafi-integration-core -- npx -y venafi-integration-core
31
31
 
32
32
  # Or add for all projects (user-level)
33
- claude mcp add -s user venafi-connector-core -- npx -y venafi-connector-core
33
+ claude mcp add -s user venafi-integration-core -- npx -y venafi-integration-core
34
34
  ```
35
35
 
36
- For full coverage, add all three:
36
+ For full coverage, add the sibling MCPs relevant to your integration type:
37
37
 
38
+ **Cloud machine connector:**
38
39
  ```bash
39
- claude mcp add venafi-connector-core -- npx -y venafi-connector-core
40
- claude mcp add venafi-connector-machine -- npx -y venafi-connector-machine
41
- claude mcp add venafi-connector-ca -- npx -y venafi-connector-ca
40
+ claude mcp add venafi-integration-core -- npx -y venafi-integration-core
41
+ claude mcp add venafi-cloud-machine -- npx -y venafi-cloud-machine
42
+ ```
43
+
44
+ **Cloud CA connector:**
45
+ ```bash
46
+ claude mcp add venafi-integration-core -- npx -y venafi-integration-core
47
+ claude mcp add venafi-cloud-ca -- npx -y venafi-cloud-ca
48
+ ```
49
+
50
+ **TPP adaptable app driver:**
51
+ ```bash
52
+ claude mcp add venafi-integration-core -- npx -y venafi-integration-core
53
+ claude mcp add venafi-tpp-app -- npx -y venafi-tpp-app
42
54
  ```
43
55
 
44
56
  ### Manual Setup
45
57
 
46
- Alternatively, add to your project's `.claude/settings.json`:
58
+ Add to your project's `.claude/settings.json`:
47
59
 
48
60
  ```json
49
61
  {
50
62
  "mcpServers": {
51
- "venafi-connector-core": {
52
- "command": "npx",
53
- "args": ["-y", "venafi-connector-core"]
54
- },
55
- "venafi-connector-machine": {
63
+ "venafi-integration-core": {
56
64
  "command": "npx",
57
- "args": ["-y", "venafi-connector-machine"]
58
- },
59
- "venafi-connector-ca": {
60
- "command": "npx",
61
- "args": ["-y", "venafi-connector-ca"]
65
+ "args": ["-y", "venafi-integration-core"]
62
66
  }
63
67
  }
64
68
  }
65
69
  ```
66
70
 
67
- ## What Is a Venafi Connector?
71
+ ## Venafi Integration Types
72
+
73
+ ### Cloud Connectors (Go)
68
74
 
69
- A Venafi connector is a containerized Go REST service that runs on a Venafi vSatellite. It acts as middleware between Venafi TLS Protect Cloud and an external system:
75
+ A Venafi Cloud connector is a containerized Go REST service that runs on a Venafi vSatellite. It acts as middleware between Venafi TLS Protect Cloud and an external system:
70
76
 
71
77
  - **Machine connectors** discover and provision TLS certificates on target systems (servers, load balancers, network appliances)
72
78
  - **CA connectors** integrate with Certificate Authorities for certificate issuance, import, and revocation
73
79
 
80
+ ### TPP Adaptable Drivers (PowerShell)
81
+
82
+ A Venafi TPP adaptable driver is a PowerShell `.ps1` script that runs directly on the TPP server. It implements 4 functions to manage certificates on a target platform:
83
+
84
+ - **Test-Settings** — validate connectivity and credentials
85
+ - **Discover-Certificates** — enumerate all certificates on the target, return PEM + metadata
86
+ - **Install-Certificate** — push a certificate (PEM or PKCS#12) to the target
87
+ - **Extract-Certificate** — retrieve a specific certificate by its platform ID
88
+
74
89
  ## Built From Experience
75
90
 
76
- This knowledge base was built from hands-on experience developing 5 production connectors:
91
+ This knowledge base was built from hands-on experience developing production integrations:
77
92
 
93
+ **Cloud connectors:**
78
94
  - **Splunk** (SSH machine connector)
79
95
  - **FortiGate** (REST API machine connector)
80
96
  - **IBM API Connect** (REST API machine connector)
81
97
  - **IBM DataPower** (REST API machine connector)
82
98
  - **DigiCert ONE** (CA connector)
83
99
 
100
+ **TPP adaptable drivers:**
101
+ - **Aruba ClearPass 6.11.x** (REST API adaptable app driver)
102
+
84
103
  ## Related Packages
85
104
 
86
- - [`venafi-connector-machine`](https://www.npmjs.com/package/venafi-connector-machine) — Machine connector-specific endpoints, SSH/REST client patterns, discovery/provisioning
87
- - [`venafi-connector-ca`](https://www.npmjs.com/package/venafi-connector-ca) — CA connector-specific endpoints, certificate issuance/import/revocation patterns
105
+ - [`venafi-cloud-machine`](https://www.npmjs.com/package/venafi-cloud-machine) — Machine connector-specific endpoints, SSH/REST client patterns, discovery/provisioning
106
+ - [`venafi-cloud-ca`](https://www.npmjs.com/package/venafi-cloud-ca) — CA connector-specific endpoints, certificate issuance/import/revocation patterns
107
+ - [`venafi-tpp-app`](https://www.npmjs.com/package/venafi-tpp-app) — TPP adaptable app driver templates, field definitions, PowerShell patterns
88
108
 
89
109
  ## License
90
110
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "venafi-integration-core",
3
- "version": "2.0.1",
3
+ "version": "2.0.2",
4
4
  "description": "MCP server providing shared knowledge, templates, and tools for building Venafi integrations (Cloud connectors and TPP adaptable drivers)",
5
5
  "main": "bundle.mjs",
6
6
  "type": "module",