JSON MCP Logs Server

Created By
mfreeman451a year ago
Overview

what is JSON Logs MCP Server?

JSON Logs MCP Server is a Model Context Protocol (MCP) server designed to enable clients like Claude Desktop to read and analyze JSON-formatted log files efficiently.

how to use JSON Logs MCP Server?

To use the server, clone the repository, set up a virtual environment, install the package, and configure the log directory. You can then run the server and interact with it through a compatible MCP client.

key features of JSON Logs MCP Server?

  • 📁 Browse log files: List and read JSON-formatted log files.
  • 🔍 Search and filter: Query logs by various criteria such as level, module, and time range.
  • 📊 Aggregate data: Group and analyze logs based on specified criteria.
  • 📈 Statistics: Obtain comprehensive statistics about log data.
  • 🚀 Fast and efficient: Optimized for handling large log files.

use cases of JSON Logs MCP Server?

  1. Analyzing application logs for debugging purposes.
  2. Monitoring system performance through log data.
  3. Generating reports based on log statistics.

FAQ from JSON Logs MCP Server?

  • Can I use this server with any MCP client?

Yes! It is designed to work with any MCP client, including Claude Desktop.

  • What log format does the server expect?

The server expects JSON log files with one JSON object per line, including specific fields like timestamp, level, and message.

  • Is there a limit to the size of log files?

While the server can handle large log files, performance may vary based on file size and system resources.

Server Config

{
  "mcpServers": {
    "json-logs": {
      "command": "python",
      "args": [
        "/Users/mfreeman/src/nco/json_logs_mcp_server.py"
      ],
      "cwd": "/Users/mfreeman/src/nco"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mfreeman451
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago