venafi-integration-core 2.0.0
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 +91 -0
- package/bundle.mjs +33001 -0
- package/package.json +44 -0
package/README.md
ADDED
|
@@ -0,0 +1,91 @@
|
|
|
1
|
+
# venafi-connector-core
|
|
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.
|
|
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.
|
|
6
|
+
|
|
7
|
+
## What's Inside
|
|
8
|
+
|
|
9
|
+
| Tool | Description |
|
|
10
|
+
|---|---|
|
|
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 |
|
|
13
|
+
| `get_guidance` | Focused guidance on: architecture, manifest, testing, deployment, troubleshooting, certificate-formats, common-mistakes, container-registry, bootstrap |
|
|
14
|
+
| `get_core_patterns` | DI wiring, handler pattern, payload encryption, error handling, logging |
|
|
15
|
+
|
|
16
|
+
| Resource | Description |
|
|
17
|
+
|---|---|
|
|
18
|
+
| Core Blueprint | Architecture, project structure, dependencies shared by all connectors |
|
|
19
|
+
| Deployment Guide | Container registry, vSatellite, build/push, plugin registration, troubleshooting |
|
|
20
|
+
| Known Gaps | 19 documented Venafi platform behaviors learned from production connectors |
|
|
21
|
+
| Bootstrap Guide | Step-by-step new project setup from Phase 0 (registry) to Phase 5 (deploy) |
|
|
22
|
+
| Manifest Template | Base manifest.json with shared structure |
|
|
23
|
+
|
|
24
|
+
## Setup
|
|
25
|
+
|
|
26
|
+
### Quick Install (Claude Code CLI)
|
|
27
|
+
|
|
28
|
+
```bash
|
|
29
|
+
# Add to your project
|
|
30
|
+
claude mcp add venafi-connector-core -- npx -y venafi-connector-core
|
|
31
|
+
|
|
32
|
+
# Or add for all projects (user-level)
|
|
33
|
+
claude mcp add -s user venafi-connector-core -- npx -y venafi-connector-core
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
For full coverage, add all three:
|
|
37
|
+
|
|
38
|
+
```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
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
### Manual Setup
|
|
45
|
+
|
|
46
|
+
Alternatively, add to your project's `.claude/settings.json`:
|
|
47
|
+
|
|
48
|
+
```json
|
|
49
|
+
{
|
|
50
|
+
"mcpServers": {
|
|
51
|
+
"venafi-connector-core": {
|
|
52
|
+
"command": "npx",
|
|
53
|
+
"args": ["-y", "venafi-connector-core"]
|
|
54
|
+
},
|
|
55
|
+
"venafi-connector-machine": {
|
|
56
|
+
"command": "npx",
|
|
57
|
+
"args": ["-y", "venafi-connector-machine"]
|
|
58
|
+
},
|
|
59
|
+
"venafi-connector-ca": {
|
|
60
|
+
"command": "npx",
|
|
61
|
+
"args": ["-y", "venafi-connector-ca"]
|
|
62
|
+
}
|
|
63
|
+
}
|
|
64
|
+
}
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
## What Is a Venafi Connector?
|
|
68
|
+
|
|
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:
|
|
70
|
+
|
|
71
|
+
- **Machine connectors** discover and provision TLS certificates on target systems (servers, load balancers, network appliances)
|
|
72
|
+
- **CA connectors** integrate with Certificate Authorities for certificate issuance, import, and revocation
|
|
73
|
+
|
|
74
|
+
## Built From Experience
|
|
75
|
+
|
|
76
|
+
This knowledge base was built from hands-on experience developing 5 production connectors:
|
|
77
|
+
|
|
78
|
+
- **Splunk** (SSH machine connector)
|
|
79
|
+
- **FortiGate** (REST API machine connector)
|
|
80
|
+
- **IBM API Connect** (REST API machine connector)
|
|
81
|
+
- **IBM DataPower** (REST API machine connector)
|
|
82
|
+
- **DigiCert ONE** (CA connector)
|
|
83
|
+
|
|
84
|
+
## Related Packages
|
|
85
|
+
|
|
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
|
|
88
|
+
|
|
89
|
+
## License
|
|
90
|
+
|
|
91
|
+
Apache-2.0
|