Add wire support for IBM Bob#1000
Conversation
|
Someone is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughAdds a new "bob" connector adapter using createJsonMcpAdapter with home-directory-based detection and config paths, registers it in the connect ADAPTERS list in index.ts, and updates the install runbook to list bob as a supported agent. ChangesBob connector support
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/cli/connect/bob.ts`:
- Line 9: The Bob adapter is using the project-level MCP filename instead of the
global settings filename, so update the config path in the bob connector to use
Bob’s global MCP settings file name. In the connect/bob.ts logic that builds the
settings path with join(homedir(), ".bob", "settings", ...), replace the current
mcp.json reference with mcp_settings.json so the adapter writes and verifies the
file Bob actually reads.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 6fc0674f-06c8-4dcc-9b6d-d9fdd6dee0f2
📒 Files selected for processing (3)
INSTALL_FOR_AGENTS.mdsrc/cli/connect/bob.tssrc/cli/connect/index.ts
| name: "bob", | ||
| displayName: "IBM Bob", | ||
| detectDir: join(homedir(), ".bob"), | ||
| configPath: join(homedir(), ".bob", "settings", "mcp.json"), |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
IBM Bob MCP settings file name path mcp_settings.json mcp.json global configuration ~/.bob/settings
💡 Result:
IBM Bob manages Model Context Protocol (MCP) server configurations through two primary levels of JSON-based files. Global Configuration Global settings are stored in mcp_settings.json, which applies configurations across all workspaces [1][2][3]. The standard location for this file is in the user's home directory under the.bob/settings/ subdirectory [4][5]: ~/.bob/settings/mcp_settings.json Note: Depending on the specific environment or installation, some official documentation may refer to the global file simply as ~/.bob/mcp_settings.json [2][3]. Additionally, some IDE-integrated versions of IBM Bob store these settings within application-specific data directories, such as: macOS: ~/Library/Application Support/IBM Bob/User/globalStorage/ibm.bob-code/settings/mcp_settings.json [6] Linux: ~/.config/IBM Bob/User/globalStorage/ibm.bob-code/settings/mcp_settings.json [6] Windows: %APPDATA%\IBM Bob\User\globalStorage\ibm.bob-code\settings\mcp_settings.json [6] Project-Level Configuration Project-specific settings are stored in a file named mcp.json [1][2]. This file is located in the root directory of your project folder [1][3]:.bob/mcp.json If the same MCP server name exists in both global and project configurations, the project-level setting takes precedence [2][3]. You can manage these files directly or through the IBM Bob settings menu, which allows you to open and edit the global or project-specific MCP configurations [1][7]. Changes usually require a restart or reload of IBM Bob to take effect [4][8].
Citations:
- 1: https://bob.ibm.com/docs/ide/configuration/mcp/mcp-in-bob
- 2: https://bob.ibm.com/docs/shell/configuration/mcp/mcp-bobshell
- 3: https://www.ibm.com/think/tutorials/mcp-integration-ibm-bob
- 4: https://community.ibm.com/community/user/blogs/kavita-patil/2026/03/24/bridging-business-automation-and-ai-ibm-business-a
- 5: https://community.ibm.com/community/user/blogs/namita-singroha/2026/03/24/bob-meets-ibm-cas-mcp
- 6: IBM/gcm-mcp-server@0fd25f7
- 7: https://community.ibm.com/community/user/blogs/aaron-ploetz/2026/06/25/using-watsonxdata-intelligence-with-mcp-and-ibm-bo
- 8: https://www.ibm.com/docs/en/decision-intelligence?topic=server-configuring-bob-connect-mcp
🏁 Script executed:
git ls-files | rg '^src/cli/connect/bob\.ts$|^README|bob|mcp'Repository: rohitg00/agentmemory
Length of output: 1176
🏁 Script executed:
sed -n '1,220p' src/cli/connect/bob.tsRepository: rohitg00/agentmemory
Length of output: 620
🏁 Script executed:
sed -n '1,260p' src/cli/connect/json-mcp-adapter.tsRepository: rohitg00/agentmemory
Length of output: 4079
Use Bob’s global MCP settings filename here — ~/.bob/settings/ should use mcp_settings.json; mcp.json is the project-level name, so this adapter writes and verifies the wrong file and Bob won’t read it.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/cli/connect/bob.ts` at line 9, The Bob adapter is using the project-level
MCP filename instead of the global settings filename, so update the config path
in the bob connector to use Bob’s global MCP settings file name. In the
connect/bob.ts logic that builds the settings path with join(homedir(), ".bob",
"settings", ...), replace the current mcp.json reference with mcp_settings.json
so the adapter writes and verifies the file Bob actually reads.
1 participant
Add wire support for IBM Bob
Summary by CodeRabbit