Docs/IDE Integration

IDE Integration

AI-powered session analysis with GitHub Copilot

Overview

Logspace integrates with your favorite IDE through the Model Context Protocol (MCP). This enables AI assistants like GitHub Copilot to analyze session logs, find bugs, and suggest fixes directly in your development environment.

AI Analysis

Ask Copilot to analyze sessions, find bugs, and suggest fixes

Session Browser

Browse and search sessions with visual previews

Quick Actions

View, explain, or fix issues with one click

Supported IDEs

VS Code

VS Code

Full extension

  • Session browser sidebar
  • MCP tools for Copilot
  • Quick action buttons
  • OAuth authentication
Cursor

Cursor

Full extension

  • Session browser sidebar
  • MCP tools for AI
  • Quick action buttons
  • OAuth authentication

Uses same extension as VS Code

WebStorm

WebStorm

JetBrains plugin

  • MCP tools for Copilot
  • Device flow authentication
  • Auto MCP configuration

WebStorm 2025.2+ required

Any MCP Client

Claude Code, Factory, etc.

  • All MCP analysis tools
  • Built-in login tool
  • Auto token refresh
  • No IDE extension required

Works with any tool that supports MCP

VS Code / Cursor Setup

Prerequisites

  • VS Code 1.90+ or Cursor (latest)
  • GitHub Copilot subscription
  • Node.js 18+

Installation

  1. Open Extensions (Cmd+Shift+X)
  2. Search for "Logspace"
  3. Click "Install"
  4. Reload when prompted

Login

  1. Click the Logspace icon in the Activity Bar
  2. Click "Login to Logspace"
  3. Enter your server URL
  4. Complete OAuth in your browser
  5. Click "Setup MCP Server" when prompted

WebStorm Setup

Prerequisites

  • WebStorm 2025.2 or later (build 252+)
  • GitHub Copilot plugin installed
  • Node.js 18+
  • JDK 21 (for building from source)

Login

  1. Go to Tools → Logspace → Login
  2. A dialog shows your device code
  3. Click "Open Browser" and enter the code
  4. Return to WebStorm after authenticating
  5. MCP is configured automatically on restart

Verify MCP in Copilot

  1. Open GitHub Copilot Chat
  2. Click the "Agent" dropdown at the bottom
  3. Select "Configure Tools"
  4. Find "logspace" in the list
  5. Click "Start" to enable (should show green indicator)

Standalone MCP Setup (Claude Code, Factory, etc.)

1. Add MCP Server

Add the Logspace MCP server to your MCP client configuration. For example, in your mcp.json or equivalent:

{
  "mcpServers": {
    "logspace": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@logspace/mcp-server@latest"],
      "env": {
        "API_BASE_URL": "https://your-server.logspace.io/"
      }
    }
  }
}

2. Authenticate

No IDE extension needed. Simply ask the AI to use the login tool:

In your AI chat:

"Log me in to Logspace"

The AI will call the login tool, which provides a URL and code. Open the URL in your browser, approve the request, and you're authenticated. Tokens refresh automatically.

MCP Tools

Logspace provides MCP tools that AI assistants can use to analyze your sessions:

analyze_session

Comprehensive session analysis - errors, network issues, user behavior summary

fetch_bug_logs

Get complete raw log data for a session

get_error_context

Deep error investigation - includes 5 seconds of context before error

list_network_requests

Filter network calls by method, status code, or URL pattern

get_console_logs

Filter console output by type (log, warn, error, debug)

get_storage_logs

Storage operations - localStorage, sessionStorage, cookies, IndexedDB

get_interactions

User interactions - clicks, inputs, scrolls, navigation

get_annotations

Session annotations, notes, and user-flagged issues

get_sse_websocket_logs

SSE and WebSocket messages for real-time communication analysis

get_rrweb_events

DOM recording events for visual replay analysis

smart_analysis

AI-Powered

Intelligent pattern detection, user frustration indicators, performance bottlenecks

Authentication Tools

login

Authenticate with Logspace using device flow - works in any MCP client without an IDE extension

logout

Log out and clear stored tokens

auth_status

Check current authentication status, token expiry, and configured API URL

Using with GitHub Copilot

Open Copilot Chat and use #logspace to analyze sessions:

Example Prompts

Analyze a specific session:

#logspace analyze bug 123

Explain errors in a session:

#logspace what caused the error in log 456?

Find failed network requests:

#logspace show failed requests from session 789

Get fix suggestions:

#logspace fix the bug in session 123

Run smart analysis:

#logspace smart analysis of bug 456

💡 Tip: Use #logspace, not @logspace

Use the hashtag #logspace to reference MCP tools. The @ prefix is for chat participants, which Logspace doesn't use.

Troubleshooting

MCP tools not working in Copilot▼
  • VS Code/Cursor: Run "Logspace: Setup MCP Server" from Command Palette
  • WebStorm: Check Tools → Logspace → Login, then restart the IDE
  • Ensure GitHub Copilot is installed and authenticated
  • Verify #logspace appears in Copilot suggestions
  • Restart your IDE after first installation
Authentication failing▼
  • Verify your Logspace server is running and accessible
  • Check the server URL is correct (include https://)
  • Try logging out and logging back in
  • Any MCP client: Ask the AI to call the login tool to re-authenticate
  • VS Code/Cursor: Run "Logspace: Login" from Command Palette
  • Check if your network blocks outgoing connections
Sessions not appearing (VS Code/Cursor)▼
  • Click the refresh button in the Logspace sidebar
  • Check your project filter
  • Verify sessions exist in the admin dashboard
  • Check that your user has permission to view sessions
WebStorm: logspace not in Copilot tools list▼
  • Ensure you're logged in: Tools → Logspace → Login
  • Restart WebStorm (MCP setup runs on startup)
  • Check IDE logs: Help → Show Log in Finder and search for "logspace"
  • Verify Node.js 18+ is installed: node --version