AI-powered session analysis with GitHub Copilot
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.
Ask Copilot to analyze sessions, find bugs, and suggest fixes
Browse and search sessions with visual previews
View, explain, or fix issues with one click
Full extension
Full extension
Uses same extension as VS Code
JetBrains plugin
WebStorm 2025.2+ required
Claude Code, Factory, etc.
Works with any tool that supports MCP
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/"
}
}
}
}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.
Logspace provides MCP tools that AI assistants can use to analyze your sessions:
Comprehensive session analysis - errors, network issues, user behavior summary
Get complete raw log data for a session
Deep error investigation - includes 5 seconds of context before error
Filter network calls by method, status code, or URL pattern
Filter console output by type (log, warn, error, debug)
Storage operations - localStorage, sessionStorage, cookies, IndexedDB
User interactions - clicks, inputs, scrolls, navigation
Session annotations, notes, and user-flagged issues
SSE and WebSocket messages for real-time communication analysis
DOM recording events for visual replay analysis
Intelligent pattern detection, user frustration indicators, performance bottlenecks
Authenticate with Logspace using device flow - works in any MCP client without an IDE extension
Log out and clear stored tokens
Check current authentication status, token expiry, and configured API URL
Open Copilot Chat and use #logspace to analyze sessions:
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
Use the hashtag #logspace to reference MCP tools. The @ prefix is for chat participants, which Logspace doesn't use.
#logspace appears in Copilot suggestionslogin tool to re-authenticatenode --version