API Monitor MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIMONITOR_HOME | No | Set APIMONITOR_HOME if the Rohitab API Monitor app is installed elsewhere. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| api_monitor_statusB | List running Rohitab API Monitor x86/x64 processes. |
| api_monitor_target_processesC | List current Windows processes that can be selected for API Monitor attach. |
| api_monitor_ui_treeB | Inspect Rohitab API Monitor top-level windows and immediate controls. |
| api_monitor_gui_screenshotC | Capture an API Monitor window in the background as a PNG data URL. |
| api_monitor_summaryC | Read Rohitab Summary panes without foregrounding the application. |
| api_monitor_gui_actionD | Act on a Rohitab GUI control using background Win32 messages. |
| api_monitor_gui_click_pointC | Click a point inside an exact Rohitab control without foregrounding it. |
| api_monitor_gui_scrollC | Scroll an exact Rohitab control in the background. |
| api_monitor_gui_keyC | Send one navigation key to an exact Rohitab control in the background. |
| api_monitor_gui_treeC | Read Rohitab's native API/filter tree, including checkbox states, in the background. |
| api_monitor_gui_tree_checkC | Set one Rohitab native API/filter tree checkbox without foregrounding the app. |
| api_monitor_window_controlC | Move or change API Monitor window state without activating it. |
| api_monitor_gui_readC | Read one Rohitab GUI control without focusing or raising the window. |
| api_monitor_gui_select_optionC | Select a native Rohitab combo-box option without focusing the window. |
| api_monitor_gui_listsC | Read Rohitab list views through background Windows UI Automation. |
| api_monitor_gui_selectB | Select a Rohitab list row by index or text without foregrounding the app. |
| api_monitor_trafficC | Read captured API-call rows from Rohitab's background traffic panes. |
| api_monitor_traffic_detailsC | Select one captured API call and return its related GUI detail panes. |
| api_monitor_wait_for_trafficC | Wait for a Rohitab Summary call count, then return the current traffic panes. |
| api_monitor_add_display_filterC | Add a Rohitab Display Filter through its background GUI dialog. |
| api_monitor_monitor_processC | Start monitoring an executable through Rohitab's native Monitor Process dialog. |
| api_monitor_capture_processC | Capture one executable in the background and save the resulting APMX file. |
| api_monitor_attach_processC | Select a running process and start monitoring it in Rohitab's background GUI. |
| api_monitor_monitoring_controlC | Start or stop the selected Rohitab monitoring session in the background. |
| api_monitor_process_controlC | Remove or terminate the selected process in Rohitab's monitor window. |
| api_monitor_detach_allC | Detach pending Rohitab API Monitor hooks through its background safeguard dialog. |
| api_monitor_launchC | Launch the installed Rohitab API Monitor x86 or x64 executable. |
| api_monitor_open_captureC | Open an APMX capture with the real Rohitab API Monitor application. |
| api_monitor_save_captureC | Save the current Rohitab capture through its background GUI. |
| capture_infoB | Inspect an APMX file header and list its ZIP container entries. |
| capture_validateC | Validate an APMX prefix, ZIP entries, process metadata, and call streams. |
| capture_compareC | Compare two APMX captures by their stored entry sizes and CRCs. |
| capture_compare_callsC | Compare saved call traffic by index and bounded payload fingerprints. |
| capture_list_entriesC | List files stored inside an APMX capture container. |
| capture_stringsC | Extract/search printable ANSI and UTF-16LE strings from an APMX capture. |
| capture_search_entriesC | Search printable strings inside each APMX ZIP entry. |
| capture_read_entryC | Read one APMX ZIP entry, returning text when printable or base64 otherwise. |
| capture_xml_entryC | Parse one bounded XML entry, such as an APMX display/filter tree. |
| capture_call_recordsC | Decode saved process call offsets and their raw data references. |
| capture_read_definitionC | Resolve one API definition node from an APMX definitions entry. |
| capture_read_typeC | Resolve one type descriptor from an APMX definitions entry. |
| capture_export_callsC | Export a bounded saved call-record page as JSON or CSV. |
| capture_extract_call_payloadC | Extract one bounded raw payload referenced by a saved call record. |
| capture_read_process_dataC | Read a bounded logical slice from a saved process data entry. |
| capture_decode_callC | Return one saved call with exact encoded args plus bounded candidates. |
| capture_call_statsC | Summarize saved raw call streams without returning every record. |
| capture_list_apisC | List resolved API definitions ordered by saved call frequency. |
| capture_search_callsC | Search saved call payloads, API definitions, and decoded arguments. |
| capture_calls_aroundC | Return a bounded raw call-record window around one saved call. |
| capture_extract_entryC | Extract one bounded APMX ZIP entry to a caller-selected file. |
| capture_monitoring_logC | Read and search the monitoring log stored in an APMX capture. |
| capture_list_processesC | List process records and executable paths recoverable from an APMX capture. |
| capture_hexC | Return a bounded hex/ASCII view of raw bytes from an APMX capture. |
| capture_find_bytesC | Find a hexadecimal byte pattern in an APMX file and return raw offsets. |
| capture_list_directoryC | List Rohitab APMX captures in a directory. |
| capture_search_directoryC | Search printable strings across all APMX captures in a directory. |
| api_monitor_search_apisC | Search Rohitab API Monitor's installed XML API definitions. |
| api_monitor_parse_api_definitionC | Return structured Rohitab API signatures from one XML definition. |
| api_monitor_read_api_definitionB | Read a bounded Rohitab XML API definition returned by the API search tool. |
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 59 tools
Descriptions do a decent job of binding each tool to a specific control or artifact, but there are clear clusters of overlapping purpose: api_monitor_monitor_process vs capture_process vs attach_process, and multiple string/search readers (capture_strings, capture_search_entries, capture_search_directory, capture_search_calls), plus several API-definition readers (api_monitor_search_apis, parse_api_definition, read_api_definition, capture_read_definition, capture_list_apis). An agent must read carefully to avoid misselection across the GUI-control family and the entry-reading family.
Names are uniformly snake_case and split cleanly into two predictable prefixes: live-control tools (api_monitor_*) and capture-file tools (capture_*). Minor deviations exist where tools are noun-only (api_monitor_status, api_monitor_summary, capture_info) rather than verb_noun, but the pattern remains readable and largely predictable.
59 tools is far beyond what an agent can reliably select from, even for a broad domain combining Windows GUI automation with APMX capture forensics. Many closely related operations (scroll, key, click_point, action, select_option, tree_check) could have been consolidated into one parameterized control tool.
The surface covers the full lifecycle: launch/attach/monitor/stop/detach, GUI reading and manipulation, screenshotting, capture export/extract, validation/comparison, and extensive call decoding and search. Only minor gaps exist, such as first-class capture deletion/creation or diffing beyond entry-size/CRC comparison.