Documentation Index
Fetch the complete documentation index at: https://sedataai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Does this work with non-Node MCP servers?
Does this work with non-Node MCP servers?
@sedata-ai/mcp is the TypeScript / Node.js package. Python and Go
packages are mirrored in the same repo
(example-servers/{python,golang}-mcp-server/) and are tracked as
separate releases.Will instrumentation slow my tools down?
Will instrumentation slow my tools down?
Per-call overhead is tens of microseconds for span creation and recording
(negligible vs typical tool latency). The exporter runs asynchronously in
the background and never blocks your handler. The biggest cost in
practice is the optional
safetyCheck round-trip (~tens of ms).Can I use this with my own OTel collector?
Can I use this with my own OTel collector?
Yes. Set
exporterEndpoint to your collector’s HTTP endpoint
(typically https://otel.example.com/v1). Sedata Cloud is just one
option — any OTLP/HTTP backend works.Does it work with self-hosted Jaeger / Tempo / Honeycomb?
Does it work with self-hosted Jaeger / Tempo / Honeycomb?
If they accept OTLP/HTTP, yes. Honeycomb accepts OTLP directly. For
Jaeger / Tempo, point at the OTel collector that fronts them.
What about MCP methods other than tools/call?
What about MCP methods other than tools/call?
Today only
tools/call is auto-instrumented. Completions, prompts,
resources, and the rest are tracked as 🚧 in
Architecture. You can record them yourself
today using
custom instrumentation.Does safetyCheck send my data to Sedata?
Does safetyCheck send my data to Sedata?
Yes — the wrapper POSTs the value of the chosen parameter to
https://api.sedata-ai.tech/security/safety-check. If you don’t want
that, don’t wrap with safetyCheck. Tracing alone never sends tool args
unless you opt in via enableArgumentCollection.How do I run without sending anything to Sedata?
How do I run without sending anything to Sedata?
Set
exporterType: 'console' (or point exporterEndpoint at your own
collector) and don’t use safetyCheck. The package then runs
fully local.Is there a way to test the wrapper in CI?
Is there a way to test the wrapper in CI?
Yes — switch to console exporter, drive a known tool call, and grep for
expected attributes in stdout. See
Console debugging for an assertion pattern.
Why is enableArgumentCollection off by default?
Why is enableArgumentCollection off by default?
Tool arguments often contain user-supplied content, secrets, or PII.
Defaulting to off means a fresh install can’t accidentally leak. Turn it
on knowingly, ideally paired with
dataProcessors.Can I use multiple TelemetryManagers in one process?
Can I use multiple TelemetryManagers in one process?
Yes — useful for testing or for instrumenting two separate sub-systems
with different
serverNames. The OTel NodeSDK is started per manager,
so be deliberate about lifecycle.What's the version stability story?
What's the version stability story?
The package is
0.0.x — the surface is stable enough to depend on, but
expect minor field tweaks before 1.0. Pin the version in production.