ibm-bob-cursor-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOB_BIN | No | Pfad zur Bob-CLI | bob |
| BOB_TIMEOUT_MS | No | Timeout pro Bob-Aufruf | 600000 |
| BOBSHELL_API_KEY | Yes | Pflicht für Prompt/Resume. API-Key für non-interactive Aufrufe. | |
| BOB_DEFAULT_CHAT_MODE | No | Standard-Modus für bob_prompt / bob_resume_session | advanced |
| BOB_DEFAULT_WORKSPACE | No | Standard-Arbeitsverzeichnis | Cursor-Projekt / cwd |
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 |
|---|---|
| bob_promptA | Run IBM Bob Shell non-interactively with auto_edit approval (edits auto-approved, shell still confirmed by Bob). |
| bob_versionA | Return the installed IBM Bob Shell version (health check). |
| bob_list_sessionsA | List Bob Shell sessions for the current project workspace. |
| bob_resume_sessionB | Resume a previous Bob Shell session and run a new prompt with auto_edit approval. |
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 4 tools
Each tool has a clear, distinct purpose: running a new prompt, resuming an existing session, listing sessions, and checking version. The overlap between bob_prompt and bob_resume_session is resolved by the explicit new-vs-resume distinction.
All tools share the 'bob_' prefix, but the second part mixes noun forms (prompt, version) with verb_noun forms (list_sessions, resume_session). The pattern is readable and predictable, though not uniformly verb_noun.
With 4 tools, the server is well-scoped for its purpose, covering the core operations without unnecessary complexity or bloat.
The set covers running a prompt, resuming a session, listing sessions, and checking version. Minor gaps exist, such as no explicit session termination or detailed session inspection, but the core lifecycle is represented.