guniweb-sap-mcp 0.6.0 → 0.7.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 +4 -0
- package/dist/index.js +47 -47
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -173,6 +173,8 @@ Every tool call logs one line on completion, carrying a correlation id that also
|
|
|
173
173
|
|
|
174
174
|
`grep a3f19c8b2d04` then shows the full story of that one call — including how many SAP requests it produced. `outcome` is one of `ok`, `error`, `timeout` (budget expired) or `aborted` (client disconnected).
|
|
175
175
|
|
|
176
|
+
Send a W3C `traceparent` header with the request, and its trace id appears in the same line as `traceId`, so a job can be followed from the calling application through n8n to the SAP request. The header is only logged. An invalid one is ignored, and it is never forwarded to SAP ([details](docs/api-reference.md#tracing-across-systems-traceparent)).
|
|
177
|
+
|
|
176
178
|
**`level: 50` means something is actually wrong.** Expected non-2xx responses — the `404`s from the catalog path probing and from the V4 catalog attempt on systems that have none — are logged at `info` with `"expected": true`, not at `error`. Measured on a production system: over 96 hours of runtime that false alarm was the *only* error-level entry in the log. Alerting on `level: 50` is therefore meaningful; before, it produced nothing but noise.
|
|
177
179
|
|
|
178
180
|
#### When something breaks
|
|
@@ -292,6 +294,8 @@ curl -H "$A" -X DELETE "$U/destinations/s4test?force=true" # remove; withou
|
|
|
292
294
|
- **Bootstrap without any SAP configuration.** With `--admin-token` the server starts even if `destinations.json` does not exist yet and no `SAP_*` is set: `/mcp` answers `503` until the first destination (and a token, or a destination named `default`) has been created through the API. `docker run … -e SAP_MCP_ADMIN_TOKEN=… -e SAP_MCP_DESTINATIONS=/config/destinations.json` is a complete first start.
|
|
293
295
|
- Put the API behind the same reverse proxy/TLS as `/mcp`; the admin secret travels as a Bearer header like any other credential.
|
|
294
296
|
|
|
297
|
+
**Rotating tokens and SAP passwords** — step by step, with what needs a restart and what does not: [Setup Guide → Rotating credentials](docs/setup-guide.md#rotating-credentials).
|
|
298
|
+
|
|
295
299
|
### 4. Use with n8n
|
|
296
300
|
|
|
297
301
|
1. Add an **AI Agent** node with an **MCP Client Tool** sub-node
|