
Mcp Telemetry Server
io.github.arnavranjan005Published by GitHub account arnavranjan005v0.1.3Updated Oct 24, 2026
Streams live progress from mcp-telemetry-sdk-instrumented tools to any connected MCP client.
Overview
Local MCP server that streams live progress, status and cost from tools instrumented with the mcp-telemetry SDK to a connected assistant.
- What you can do
- Subscribe to a job and block while its live progress streams until it finishes
- List all known jobs with their status and cost
- Inspect one job's full state, including steps, cost and failure reason
- When to use it
- Useful when you run tools instrumented with mcp-telemetry-sdk and want the assistant to follow long-running jobs, check their status, or see why one failed.
- Requirements
- A local Node.js runtime; the package is installed globally or launched with npx. It only shows jobs produced by tools instrumented with mcp-telemetry-sdk. No accounts, keys or environment variables are declared.
Installation
In SourceWeft
- Open Mcp Telemetry Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-telemetry-server
The collector half of mcp-telemetry. Register it as an MCP server to watch live progress from any tool instrumented with mcp-telemetry-sdk.
Install
Register it
Tools it exposes
See the main README for a full worked example.
License
MIT
Source: packages/server/README.md at commit 8bf4891
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts