bitslicer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITSLICER_SOCKET_PATH | No | Path to the Unix socket used to communicate with the native bridge. If not set, the server reads the path from the session descriptor. | |
| BITSLICER_ENABLE_WRITES | No | Set to 'true' to enable write operations. Defaults to 'false' and writes remain disabled in this build. | false |
| BITSLICER_SESSION_TOKEN | No | Session token used to authenticate requests. Generated automatically by the native app; not required if the session descriptor is available. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Check the local Bit Slicer bridge and report capabilities. |
| list_processesA | List attachable processes. Listing does not authorize attachment. |
| attachB | Request explicit attachment. The native bridge must independently approve the target before access. |
| list_memory_regionsA | List mapped regions for the currently approved target. |
| read_memoryB | Read at most 65536 bytes from an approved target. |
| scan_valueA | Start a bounded integer or UTF-8 string scan in readable regions. |
| filter_scanA | Filter a prior scan using an exact, changed, unchanged, increased, or decreased predicate. |
| resolve_pointer_chainA | Resolve a base address plus a bounded sequence of pointer offsets. |
| list_loaded_imagesA | List Mach-O images loaded in the approved target. |
| dump_memoryA | Return a base64 memory dump of at most 1048576 bytes; this tool does not write files. |
| disassembleC | Decode a bounded instruction range through the bridge disassembly abstraction. |
| begin_edit_sessionA | Begin a short-lived write session. Requires server write opt-in and native target authorization. |
| preview_memory_patchC | Compare expected bytes and preview a patch of at most 64 bytes without writing. |
| apply_memory_patchA | Apply only a previously previewed patch using its one-time confirmation ID. |
| undo_last_patchA | Undo the latest patch in the edit session using recorded compare-before-write metadata. |
| end_edit_sessionA | Invalidate previews and close the active edit session. |
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 16 tools
Each tool has a clearly distinct purpose: attach/list processes, read/dump memory, scan/filter, edit session phases, and utility functions. The only close pair is read_memory vs dump_memory, but descriptions clearly distinguish by size and encoding.
All tools follow a consistent snake_case verb_noun pattern (e.g., list_memory_regions, apply_memory_patch, resolve_pointer_chain). Standalone verbs like ping, attach, and disassemble are also in snake_case and fit the convention.
16 tools is slightly above the typical 3-15 range for a well-scoped server, but every tool serves a distinct function in the memory editing workflow. The count feels justified by the domain's complexity.
Covers process attachment, memory enumeration/reading, scanning/filtering, pointer resolution, disassembly, and a safe patch workflow with preview/apply/undo. Missing an explicit detach tool, and writes are restricted to previewed patches, but the core lifecycle is well covered.