mcp-local-telemetry

Purpose: Giving AI agents access to local system telemetry without building custom monitoring integrations.

Inferred · not functionally tested

Audience: developers building AI agents and MCP integrations

Inferred · not functionally tested

Functions: monitoring

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org. These links do not verify the individual claims.

In the Frameworks & runtimes space, mcp-local-telemetry takes a focused approach. Inferred · not functionally tested: It focuses on giving AI agents access to local system telemetry without building custom monitoring integrations. Inferred · not functionally tested: mcp-local-telemetry is an open-source project aimed at developers building AI agents and MCP integrations. Basis unknown · not verified: mcp-local-telemetry is open source under the MIT license. Basis unknown · not verified: It ships for the command line and API, and it can be self-hosted.

mcp-local-telemetry first shipped in 2026. Inferred · not functionally tested: Among its 5 catalogued features are system telemetry, MCP server, and local metrics. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.