Skip to main content
Glama
Sign In
ibm-bob-cursor-bridge

ibm-bob-cursor-bridge

by thelad-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

IBM Bob → Cursor MCP Bridge

MCP-Server, der IBM Bob Shell als Tools für Cursor bereitstellt.

Ausführliche Dokumentation: docs/README.md — Einrichtung, IBM-i-MCP-Integration, Beispiele (TASA001F01, DDSHOPBES.CSV).

Voraussetzungen

  • Node.js 18+

  • Bob Shell (bob --version, aktuell 1.0.6 auf vm88)

  • BOBSHELL_API_KEY für non-interactive Aufrufe

Related MCP server: macOS Shell MCP Server

Installation

git clone
cd ./bob-cursor-mcp
npm install
npm run build

Cursor einrichten

Die Projekt-Konfiguration liegt in .cursor/mcp.json. Ergänzen Sie dort den API-Key:

{
  "mcpServers": {
    "ibm-bob": {
      "command": "node",
      "args": ["./bob-cursor-mcp/dist/index.js"],
      "env": {
        "BOBSHELL_API_KEY": "<Ihr-Key>",
        "BOB_BIN": "~/.local/bin/bob"
      }
    }
  }
}

Danach in Cursor: Settings → Tools & MCP → Server ibm-bob aktivieren.

Alternativ können Sie .env.example nach .env kopieren und den Key dort setzen — für Cursor MCP muss der Key jedoch in mcp.json oder der globalen MCP-Konfiguration stehen.

MCP-Tools

Tool

Beschreibung

bob_version

Healthcheck: installierte Bob-Version

bob_prompt

Aufgabe an Bob delegieren (Modi: plan, code, advanced, ask)

bob_list_sessions

Bob-Sessions des Projekts auflisten

bob_resume_session

Session fortsetzen und Follow-up-Prompt senden

bob_prompt und bob_resume_session nutzen standardmäßig den Modus advanced (MCP-Tools inkl. IBM i). Über BOB_DEFAULT_CHAT_MODE oder das Tool-Argument mode änderbar.

bob_prompt und bob_resume_session nutzen --approval-mode=auto_edit: Datei-Edits werden automatisch genehmigt, Shell-Befehle weiterhin von Bob bestätigt.

Beispiel (Agent-Chat)

Nutze bob_version, dann bob_prompt im Modus ask: Was ist 2+2?

Umgebungsvariablen

Variable

Default

Beschreibung

BOBSHELL_API_KEY

—

Pflicht für Prompt/Resume

BOB_BIN

bob

Pfad zur Bob-CLI

BOB_DEFAULT_CHAT_MODE

advanced

Standard-Modus für bob_prompt / bob_resume_session

BOB_DEFAULT_WORKSPACE

Cursor-Projekt / cwd

Standard-Arbeitsverzeichnis

BOB_TIMEOUT_MS

600000

Timeout pro Bob-Aufruf

Smoke-Test

npm run build
node scripts/smoke-test.mjs

Architektur

Cursor Agent → MCP (stdio) → dieser Server → bob CLI → IBM Bob Shell

Bob bleibt MCP-Client; dieser Server ist die Brücke in die andere Richtung (Cursor → Bob).

Available Tools

4 tools
bob_list_sessionsA

List Bob Shell sessions for the current project workspace.

Inputs: workspace.

bob_promptA

Run IBM Bob Shell non-interactively with auto_edit approval (edits auto-approved, shell still confirmed by Bob).

Inputs: prompt (required), mode, model, stdin, +2 more.

bob_resume_sessionB

Resume a previous Bob Shell session and run a new prompt with auto_edit approval.

Inputs: prompt (required), session (required), mode, model, +3 more.

bob_versionA

Return the installed IBM Bob Shell version (health check).

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose, covering the core operations without unnecessary complexity or bloat.

    Completeness4/5

    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.

    Resources

    Related MCP Connectors

    Related MCP Servers