IBM Bob Integration
IBM Bob is IBM’s AI-powered development assistant and IDE designed for enterprise software development.Platform Support: Windows, macOS, Linux
Transport Modes: Stdio (local) and HTTP (remote)
MCP Client: Built-in MCP client for connecting to MCP servers
Prerequisites
Ensure you have IBM Bob installed and configured:Getting Bob: IBM Bob is available to IBM employees and authorized partners. Visit the IBM Bob product page for access information.
Configuration File Location
Bob stores its MCP server configuration in:- User Configuration
- Workspace Configuration
Location:
~/.bob/mcp.json or %USERPROFILE%\.bob\mcp.json (Windows)Benefits:- Available across all projects
- Personal configuration
- Not shared via version control
Local (Stdio) Setup
Configure a local server that Bob will spawn and manage:Using Configuration File
Create or edit your MCP configuration file:Remote (HTTP) Setup
Connect to a remote IBM i MCP Server:Step 1: Start Remote Server
On your server machine, configure and start the MCP server with authentication:Step 2: Obtain Access Token
Step 3: Configure Bob
Edit your MCP configuration file:Environment Variable Expansion
Bob supports environment variable expansion for secure credential management:${VAR}- Expands to the value of environment variableVAR${VAR:-default}- Expands toVARif set, otherwise usesdefault
Testing the Connection
After configuration, restart Bob and verify the MCP server connection:- Restart Bob: Close and reopen the Bob IDE
- Check MCP status: Look for MCP indicators in the Bob interface
- List available tools: Ask Bob “What MCP tools are available?”
- Test a tool: Try “Show me the IBM i system status using MCP”
Troubleshooting
Server Not Appearing
Server Not Appearing
Symptoms: MCP server doesn’t show up in BobSolutions:
- Verify JSON syntax in your MCP configuration file
- Check that
npx -y @ibm/ibmi-mcp-server@latestworks from terminal - Ensure absolute paths are used for
--tools - Restart Bob completely
- Check Bob logs for MCP-related errors
Authentication Failed (Remote)
Authentication Failed (Remote)
Symptoms: Connection refused or 401 Unauthorized for remote connectionsSolutions:
- Verify server is running:
curl http://localhost:3010/mcp - Check token is valid: verify token hasn’t expired (default: 1 hour)
- Ensure
MCP_AUTH_MODE=ibmiandIBMI_HTTP_AUTH_ENABLED=trueon server - Get a fresh token:
node get-access-token.js --verbose - Confirm Authorization header format:
Bearer TOKEN
Tools Not Loading
Tools Not Loading
Symptoms: Server connects but no tools availableSolutions:
- Verify tools path exists and is absolute
- Check YAML files are valid in tools directory
- Ensure IBM i credentials are correct
- Verify Mapepire is running on IBM i (port 8076)
- Test tools:
npx -y @ibm/ibmi-mcp-server@latest --list-toolsets --tools /path
Connection to IBM i Failed
Connection to IBM i Failed
Symptoms: Server starts but can’t connect to IBM iSolutions:
- Test IBM i connectivity:
ping your-ibmi-host - Verify Mapepire is running:
netstat -an | grep 8076 - Check firewall allows port 8076
- Ensure DB2i credentials have appropriate authorities
- Verify hostname resolution
Advanced Configuration
Multiple IBM i Systems
Configure multiple server instances for different IBM i systems:Custom Toolsets
Load specific toolsets for different workflows:Next Steps
SQL Tools
Create custom SQL tools for your IBM i workflows
Configuration
Explore all IBM i MCP Server configuration options
Authentication
Set up secure IBM i HTTP authentication
Other Clients
Explore other MCP-compatible clients
Additional Resources
- IBM Bob Product Page
- IBM Bob Documentation (IBM Internal)
- IBM i MCP Server on IT Jungle
- IBM i MCP Quick Start
Internal Documentation: For IBM employees, detailed Bob MCP configuration is available at Bob MCP Documentation.