1C Debug MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_debug_serverB | Check an existing 1C HTTP debug server without registering a debugger UI. |
| connect_debuggerB | Register this MCP as debugger UI for one infobase alias. Replaces any active MCP debug session but never stops 1C. |
| disconnect_debuggerA | Detach the MCP debugger UI without stopping 1C or dbgs. |
| list_debug_targetsA | List current client, server, background-job and other RDBG targets. |
| set_auto_attachC | Configure RDBG auto-attach target types. Typical values include Client, ManagedClient, Server, ServerEmulation, Job, JobFileMode, HTTPService and WebService. |
| attach_targetsB | Attach target IDs returned by list_debug_targets. |
| detach_targetsA | Detach targets without terminating their 1C processes. |
| poll_debug_eventsA | Poll target start/quit, breakpoint and step events. |
| get_call_stackA | Read the call stack of a stopped target. |
| get_local_variablesB | Read local variables at a stack level of a stopped target. |
| evaluate_expressionA | Evaluate a 1C expression in a stopped target. Expressions may have side effects. |
| continue_or_stepC | Continue, step over, step in, or step out in a stopped target. |
| suspend_targetA | Request a running target to stop on the next BSL instruction. |
| set_breakpointsA | Set active breakpoints for one local BSL module. XML metadata under sourceRoot resolves RDBG object/property IDs. |
| resolve_source_moduleB | Resolve a BSL path through exported 1C XML metadata to RDBG object/property identifiers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct phase of the 1C debugging workflow: connection, target management, execution control, inspection, and source mapping. Even similar actions like check_debug_server vs connect_debugger are clearly separated by whether a debugger UI is registered.
All tool names follow a consistent snake_case verb_noun pattern, such as list_debug_targets, attach_targets, set_breakpoints, and continue_or_step. This makes the toolset highly predictable and easy to navigate.
15 tools is at the upper boundary of the well-scoped range, but every tool earns its place in a debugger lifecycle: connect, list, attach, breakpoint, poll, inspect, evaluate, step, suspend, detach. The count matches the complexity of the domain without redundancy.
The toolset covers the full debugging workflow from connecting to a debug server and resolving source modules, through attaching targets, setting breakpoints, polling events, inspecting state, controlling execution, and detaching. There are no obvious dead ends or missing critical debugger operations.