get_local_variables

MCP tool from MCP Debugger by debugmcp

Get local variables in current frame

How to use it

get_local_variables is exposed by the MCP Debugger MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the get_local_variables tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install MCP Debugger

$docker run -v $(pwd):/workspace debugmcp/mcp-debugger:latest

FULL MCP DEBUGGER LISTING

Other tools in MCP Debugger (27)

attach_to_process

Attach debugger to a running process

clear_breakpoints

Remove all breakpoints (optionally per file)

close_debug_session

Close a session

continue_execution

Continue running

create_debug_session

Create a new debugging session

detach_from_process

Detach debugger from a process

evaluate_expression

Evaluate expressions in debug context

Open a read-only DAP mirror endpoint so an IDE can attach and inspect

Read captured debuggee output (stdout/stderr)

Get variable scopes for a frame

get_source_context

Get source code context

get_stack_trace

Get the current stack trace

Get variables in a scope

list_breakpoints

List a session's breakpoints with verified state

list_debug_sessions

List all active sessions

list_supported_languages

Show available language adapters

List all threads in the debug session

pause_execution

Pause running execution

redefine_classes

Hot-swap changed Java classes into a running JVM (Java only)

remove_breakpoint

Remove a breakpoint by id or file+line

restart_debugging

Relaunch with the same config, breakpoints re-applied

Set a breakpoint in a file

start_debugging

Start debugging a script

Step into a function

Step out of a function

Step over the current line

unexpose_session

Close the mirror endpoint and disconnect IDE clients