cursor-logs

Locate and inspect Cursor MCP and extension logs under ~/.config/Cursor/logs/.

Updated Aug 23, 2026

Search Tags:#debugging #logs #mcp #extension #cursor #log-analysis

Ready to run

npx skills add https://github.com/flesler/dotfiles --skill cursor-logs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cursor-logs
Source: https://github.com/flesler/dotfiles/tree/main/home/.cursor/skills/cursor-logs
Command: npx skills add https://github.com/flesler/dotfiles --skill cursor-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locating and inspecting Cursor logs scattered across config folders can be tedious and time-consuming, hindering rapid debugging.

Core Features & Use Cases

Locate most recent Cursor logs in ~/.config/Cursor/logs/ with timestamped directories.
Identify MCP logs under anysphere.cursor-mcp and extension-specific logs for quick issue diagnosis.
Quickly surface errors and warnings using simple CLI queries and targeted file searches in a multi-project environment.

Quick Start

Find the most recent MCP log for a failing extension and tail it to view the latest errors.

Frequently Asked Questions about cursor-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find Cursor logs for debugging MCP and extension issues?▼

To find Cursor logs for debugging, locate timestamped directories under ~/.config/Cursor/logs/. You can identify MCP logs under anysphere.cursor-mcp and extension-specific logs to quickly surface errors and warnings.

Where are Cursor MCP logs stored on my system?▼

Cursor MCP logs are stored under ~/.config/Cursor/logs/ within anysphere.cursor-mcp directories. These timestamped folders allow you to pinpoint specific Model Context Protocol failures and extension errors across projects.

What is the best way to view recent errors in Cursor extension logs?▼

The best way to view recent errors in Cursor extension logs is to locate the most recent timestamped directory in ~/.config/Cursor/logs/ and tail the specific extension log file to see the latest warnings and stack traces.

Does this approach work for filtering logs across multiple Cursor projects?▼

Yes, this approach works for multi-project environments by targeting file searches within ~/.config/Cursor/logs/. You can use simple CLI queries to filter and view relevant log entries across different projects.

Can I tail Cursor logs to monitor debugging issues in real time?▼

You can tail Cursor logs to monitor debugging issues by applying simple CLI queries to the active log files in ~/.config/Cursor/logs/. This surfaces the latest errors and warnings as they are written.

Why is locating Cursor logs manually considered tedious for debugging?▼

Locating Cursor logs manually is tedious because they are scattered across config folders with timestamped directories. Streamlining this process with targeted searches rapidly surfaces errors and warnings to accelerate debugging.