MCP Cursor

Enhance your development workflow with AI-powered MCP tools and extensions for Cursor IDE.

Product

  • MCP Servers
  • Getting Started
  • Documentation
  • Open Source

Resources

  • MCP Specification
  • Cursor IDE
  • MCP GitHub
  • Contributing

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy
Made withfor the developer community
© 2025 MCP Cursor. All rights reserved.
MCP Logo
MCP Cursor
IntroductionMCPs
IntroductionMCPs
3D MCP Cursor Visualization
  1. Home
  2. Servers
  3. Log Analysis SQLite MCP
Log Analysis SQLite MCP Logo

Log Analysis SQLite MCP

Model Context Protocol Integration

Overview

Transforms compressed log files into a queryable SQLite database with tables for logs, stack traces, and errors, enabling efficient analysis and troubleshooting of application issues by timestamp, log level, and module.

Log Analysis SQLite

Transforms compressed log files into a queryable SQLite database with tables for logs, stack traces, and errors, enabling efficient analysis and troubleshooting of application issues by timestamp, log level, and module.

Installation Instructions


README: https://github.com/direkt/mcp-test

Log Analysis with SQLite MCP Server

This project provides tools to create an SQLite database from compressed log files and interact with it using the Model Context Protocol (MCP) SQLite server.

Install instructions

python3 -m venv venv
source venv/bin/activate
pip3 install -r requirements.txt

Place log files in the folder as .gz files, then run:

python3 create_log_db.py 

MCP SQLite Server

To configure the MCP SQLite server in Cursor-

  • Cursor Settings
  • MCP
  • Add New MCP Server
  • Name SQLlite
  • Set the type to command
  • Put this in the command box
npx -y @smithery/cli@latest run mcp-server-sqlite-npx --config "{\"databasePath\":\"/path/to/thedatbase/logs.db\"}"

Contents

  • create_log_db.py: Script to extract and parse log files into an SQLite database
  • query_logs.py: Script to directly query the SQLite database
  • logs.db: SQLite database containing parsed log data

Database Structure

The database contains the following tables:

logs Table

  • id: Unique identifier for each log entry
  • timestamp: Timestamp of the log entry
  • thread: Thread that generated the log
  • level: Log level (INFO, WARN, ERROR, DEBUG)
  • module: Module that generated the log
  • message: Log message content
  • source_file: Source log file
  • raw_log: Raw log entry

stack_traces Table

  • id: Unique identifier for each stack trace
  • log_id: Reference to the log entry this stack trace belongs to
  • stack_trace: Full stack trace text

parsing_errors Table

  • id: Unique identifier for each parsing error
  • line: The line that couldn't be parsed
  • source_file: Source log file
  • error_message: Error message explaining why parsing failed
  • timestamp: When the parsing error occurred

You can query the database directly using the query_logs.py script:

Featured MCPs

Github MCP - Model Context Protocol for Cursor IDE

Github

This server provides integration with Github's issue tracking system through MCP, allowing LLMs to interact with Github issues.

Sequential Thinking MCP - Model Context Protocol for Cursor IDE

Sequential Thinking

An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process. Break down complex problems into manageable steps, revise and refine thoughts as understanding deepens, and branch into alternative paths of reasoning.

Puppeteer MCP - Model Context Protocol for Cursor IDE

Puppeteer

A Model Context Protocol server that provides browser automation capabilities using Puppeteer. This server enables LLMs to interact with web pages, take screenshots, execute JavaScript, and perform various browser-based operations in a real browser environment.