Skip to main content
Glama
jnjaeschke

pernosco-mcp

by jnjaeschke

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
session_connectA

Connect to a Pernosco trace by URL or trace ID. Opens the tab in Firefox if not already open.

session_listA

List available Pernosco traces (open Firefox tabs with pernos.co loaded)

session_statusA

Get current focus position (event number, source file, line) for the connected session

session_disconnectB

Disconnect from the current Pernosco session

find_executionsA

Find all calls to a function across the trace. Optionally evaluate C++ expressions at each call site using print_exprs (semicolon-delimited).

stackA

Get the call stack at the current focus position

evaluateB

Evaluate a C++ expression at the current focus position

gotoA

Navigate to a specific execution point by result index (from a previous query) or raw focus object

task_treeA

Get the complete process/thread hierarchy for the trace

searchB

Search for symbols, functions, or types by name

watchpoint_historyA

Get complete write history for a memory address across the trace (reads all writes before and after current focus)

stdout_stderrA

Get stdout/stderr output around the current focus position. Output is scoped to the current process — use goto to navigate to a content process first if needed. Results include event IDs for navigation.

current_tasksB

Get active processes and threads at the current focus moment

notebook_readA

Read Pernosco notebook annotations saved in this session

find_breakpoint_hitsB

Find all hits of a specific source line. Use when you have a file:line from a stack trace or crash report.

dynamic_annotationsA

Show which lines of the current source file executed at the current focus, with execution counts for loops. Essential for understanding which code paths and branches ran.

source_readA

Read source code lines from the current trace. Use after stack or session_status to see code around the current position.

step_to_next_hitA

Navigate forward to the next execution of the current source line (or a specified line). Useful for stepping through loop iterations or repeated calls.

watch_variableA

Get the complete write history of a C++ variable. Evaluates the expression to find its memory address, then traces all writes. Simpler than manually using evaluate + watchpoint_history.

step_to_prev_hitB

Navigate backward to the previous execution of the current source line (or a specified line). Useful for reverse debugging.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Pernosco debugging guideHow to use Pernosco MCP tools effectively
Open sessionsList of open Pernosco traces

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jnjaeschke/pernosco-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server