Skip to main content
Glama
baxtheman

mcp-lnav-canbus

by baxtheman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-lnav-canbus

No user-submitted related servers found.

    Related Servers

    • log-mcp

      ascii766164696D
      A
      license
      A
      quality
      D
      maintenance
      MCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.
      7
      100
      MIT
    • canforge-mcp by canforge

      canforge-mcpofficial

      canforge
      A
      license
      A
      quality
      B
      maintenance
      Local, read-only MCP server for inspecting DBC files and decoding CAN capture logs, with bounded and composable tools.
      13
      MIT

    • Kuksa MCP Server

      mikehaller
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server that connects LLMs to vehicle data via the Eclipse Kuksa Databroker, enabling AI assistants to read and write vehicle signals using the standardized COVESA Vehicle Signal Specification.
      9
      Apache 2.0

    • silotek-serial-mcp

      JOCOIN94
      F
      license
      A
      quality
      B
      maintenance
      A headless MCP server that enables AI tools (like Claude Code) to read and analyze serial logs from embedded boards (ESP32, STM32) for firmware debugging, with read-only tools for log retrieval and a built-in web viewer.
      6
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clear distinct purposes, but get_statistics with 'errors' type overlaps with find_errors, and query_can_messages can technically replace extract_can_frames. Overall, session management, analysis, and extraction tools are well-separated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (open_can_log, query_can_messages, get_statistics, etc.) with no mixed styles or ambiguous generic verbs.

    Tool Count5/5

    Nine tools is well within the ideal range for a focused domain. Each tool covers a distinct aspect of CAN bus log analysis without unnecessary bloat or missing essentials.

    Completeness4/5

    The toolset covers log opening, SQL querying, frame extraction, payload noise analysis, statistics, error detection, and session lifecycle. Minor gaps exist like export or DBC decoding, but core analysis workflows are fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources