wopee-mcp 1.12.0 → 1.13.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 +53 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -70,6 +70,59 @@ If you're unsure about your proxy settings, check your VS Code settings (`settin
|
|
|
70
70
|
- `http://10.x.x.x:8080`
|
|
71
71
|
- `http://username:password@proxy.company.com:8080` (if authentication is required)
|
|
72
72
|
|
|
73
|
+
### TLS / Certificate Issues
|
|
74
|
+
|
|
75
|
+
**This is not required for MCP to work.** If you see HTTPS or certificate-related errors, that indicates a TLS or certificate trust issue in your environment.
|
|
76
|
+
|
|
77
|
+
If the server fails with errors such as **`UNABLE_TO_VERIFY_LEAF_SIGNATURE`** or **`certificate has expired`**, it may be due to:
|
|
78
|
+
|
|
79
|
+
- **Self-signed certificates** (e.g. when `WOPEE_API_URL` points to an internal or dev server)
|
|
80
|
+
- **Corporate proxy / SSL inspection** (traffic re-encrypted with a corporate CA your machine doesn’t trust)
|
|
81
|
+
- **Missing CA certificates** in Node’s trust store
|
|
82
|
+
|
|
83
|
+
#### Preferred solutions (secure)
|
|
84
|
+
|
|
85
|
+
1. **Use a valid TLS certificate** – e.g. Let’s Encrypt, or an internal CA – and ensure the **full certificate chain** is served.
|
|
86
|
+
2. **Install the corporate or internal CA** so Node trusts it:
|
|
87
|
+
|
|
88
|
+
Example:
|
|
89
|
+
|
|
90
|
+
```bash
|
|
91
|
+
export NODE_EXTRA_CA_CERTS=/etc/ssl/certs/internal-ca.pem
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
In MCP config `env`:
|
|
95
|
+
|
|
96
|
+
```json
|
|
97
|
+
"env": {
|
|
98
|
+
"WOPEE_PROJECT_UUID": "your-project-uuid-here",
|
|
99
|
+
"WOPEE_API_KEY": "your-api-key-here",
|
|
100
|
+
"NODE_EXTRA_CA_CERTS": "/path/to/ca.pem"
|
|
101
|
+
}
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
#### Insecure workaround (not recommended)
|
|
105
|
+
|
|
106
|
+
For **local debugging only**, you may disable TLS verification in Node. This should **never** be used in production, as it disables HTTPS security and exposes traffic to interception.
|
|
107
|
+
|
|
108
|
+
```bash
|
|
109
|
+
export NODE_TLS_REJECT_UNAUTHORIZED=0
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
Or in MCP config `env`:
|
|
113
|
+
|
|
114
|
+
```json
|
|
115
|
+
"env": {
|
|
116
|
+
"WOPEE_PROJECT_UUID": "your-project-uuid-here",
|
|
117
|
+
"WOPEE_API_KEY": "your-api-key-here",
|
|
118
|
+
"NODE_TLS_REJECT_UNAUTHORIZED": "0"
|
|
119
|
+
}
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
Treat this as a **debug-only escape hatch**, not a normal setup step.
|
|
123
|
+
|
|
124
|
+
**Note:** Some users have reported setting `PYTHONHTTPSVERIFY=0` as well. This MCP server does not use Python; that variable has no effect on it. It would only apply if you run a Python-based MCP host or other tooling that also performs HTTPS in the same environment—outside the scope of this server.
|
|
125
|
+
|
|
73
126
|
## Getting Started
|
|
74
127
|
|
|
75
128
|
Most tools in this MCP server require a `suiteUuid` to operate. You have two options to get started:
|