Installation
pnpm add @shinzolabs/instrumentation-mcp
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @shinzolabs/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add shinzo-labs-shinzo-ts -- npx -y @shinzolabs/instrumentation-mcp@1.1.0Execute em um terminal.
{ "mcpServers": { "shinzo-labs-shinzo-ts": { "command": "npx", "args": [ "-y", "@shinzolabs/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
pnpm add @shinzolabs/instrumentation-mcp
TypeScript SDK for MCP server observability, built on OpenTelemetry. Gain insight into agent usage patterns, contextualize tool calls, and analyze server performance across platforms. Integrate with any OpenTelemetry ingest service including the Shinzo platform.
For the simplest configuration, just pass in the server name, version, and exporter endpoint:
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"
import { instrumentServer, TelemetryConfig } from "@shinzolabs/instrumentation-mcp"
const NAME = "my-mcp-server"
const VERSION = "1.0.0"
const server = new McpServer({
name: NAME,
version: VERSION,
description: "Example MCP server with telemetry"
})
// Use TelemetryConfig to set configuration options
const telemetryConfig: TelemetryConfig = {
serverName: NAME,
serverVersion: VERSION,
exporterEndpoint: "http://localhost:4318/v1" // OpenTelemetry collector endpoint - /trace and /metrics are added automatically
}
// Initialize telemetry
const telemetry = instrumentServer(server, telemetryConfig)
// Add tools using the tool method
server.tool(...)
The TelemetryConfig exposes a number of other options for precise and expansive telemetry processing:
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"
import { instrumentServer, TelemetryConfig } from "@shinzolabs/instrumentation-mcp"
const NAME = "my-other-mcp-server"
const VERSION = "1.0.0"
const server = new McpServer({
name: NAME,
version: VERSION,
description: "Example MCP server with telemetry"
})
const telemetryConfig: TelemetryConfig = {
serviceName: NAME,
serviceVersion: VERSION,
exporterEndpoint: "http://localhost:4318/v1", // OpenTelemetry collector endpoint
exporterAuth: {
type: "bearer",
token: process.env.OTEL_AUTH_TOKEN
},
enablePIISanitization: false,
enableTracing: false,
samplingRate: 0.7,
dataProcessors: [
(telemetryData: any) => {
if (telemetryData['mcp.tool.name'] === "sensitive_operation") {
for (const key of Object.keys(telemetryData)) {
if (key.startsWith('mcp.request.argument')) delete telemetryData[key]
}
}
return telemetryData
}
]
}
const telemetry = instrumentServer(server, telemetryConfig)
// Add tools using the tool method
server.tool(...)
The TelemetryConfig interface provides comprehensive configuration options for customizing telemetry behavior:
The exporterAuth property supports multiple authentication methods:
const telemetryConfig: TelemetryConfig = {
serverName: "my-server",
serverVersion: "1.0.0",
exporterEndpoint: "http://localhost:4318/v1" // OpenTelemetry collector endpoint
}
const telemetryConfig: TelemetryConfig = {
serverName: "my-server",
serverVersion: "1.0.0",
exporterEndpoint: "https://api.example.com/v1",
exporterAuth: {
type: "bearer",
token: process.env.OTEL_AUTH_TOKEN
}
}
const telemetryConfig: TelemetryConfig = {
serverName: "my-server",
serverVersion: "1.0.0",
exporterEndpoint: "http://localhost:4318/v1", // OpenTelemetry collector endpoint
dataProcessors: [
(data) => {
// Remove sensitive parameters
if (data['mcp.tool.name'] === 'sensitive_tool') {
delete data['mcp.request.argument.password']
}
return data
}
]
}
const telemetryConfig: TelemetryConfig = {
serverName: "my-server",
serverVersion: "1.0.0",
exporterType: "console",
enableMetrics: false, // Console exporter doesn't support metrics
samplingRate: 1.0 // Sample all traces in development
}
Contributions are welcome! Please see the Contributing Guide in the main repository.
This package is distributed under the MIT License.
TypeScript SDK for MCP server observability, built on OpenTelemetry. Gain insight into agent usage patterns, contextualize tool calls, and analyze server performance across platforms. Integrate with a
{ "mcpServers": { "shinzo-labs-shinzo-ts": { "command": "npx", "args": [ "-y", "@shinzolabs/[email protected]" ] } }}Visão geral
TypeScript SDK for MCP server observability, built on OpenTelemetry. Gain insight into agent usage patterns, contextualize tool calls, and analyze server performance across platforms. Integrate with any OpenTelemetry ingest service including the Shinzo platform.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Shinzo Ts roda localmente via stdio.
Última verificação: 2026-10-27. TypeScript SDK for MCP server observability, built on OpenTelemetry. Gain insight into agent usage patterns, contextualize tool calls, and analyze server performance across platforms. Integrate with any OpenTelemetry ingest service including the Shinzo platform.