Platform Support: macOS and Windows
Transport Mode: Stdio (local process management)
Note: For remote HTTP servers, use Claude Code instead
Configuration File Location
Claude Desktop stores its MCP server configuration in:- macOS
- Windows
Local (Stdio) Setup
For local development with the server running on your machine: Step 1: Ensure server is installedclaude_desktop_config.json:
Remote Servers: Claude Desktop only supports local stdio servers. For connecting to remote MCP servers via HTTP, use Claude Code instead, which supports HTTP transport.
Environment Variable Expansion
Claude Desktop 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 configuring and restarting Claude Desktop:- Check MCP status: Look for the MCP icon (plug symbol) in Claude Desktop
- List available tools: Ask Claude “What tools do you have available?”
- Test a tool: Try “Show me the system status of my IBM i”
Troubleshooting
Server Not Appearing
Server Not Appearing
Symptoms: MCP server doesn’t show up in Claude DesktopSolutions:
- Verify JSON syntax in
claude_desktop_config.json - Check that
npx -y @ibm/ibmi-mcp-server@latestworks from terminal - Ensure absolute paths are used for
--tools - Restart Claude Desktop completely (Cmd+Q / Alt+F4, then relaunch)
- Check Claude Desktop logs for errors
Authentication Failed (Remote)
Authentication Failed (Remote)
Symptoms: Connection refused or 401 UnauthorizedSolutions:
- Verify server is running:
curl http://localhost:3010/mcp - Check token is valid:
echo $IBMI_MCP_ACCESS_TOKEN - Ensure token hasn’t expired (default: 1 hour)
- Confirm
MCP_AUTH_MODE=ibmiandIBMI_HTTP_AUTH_ENABLED=true - Get a fresh token:
node get-access-token.js --verbose
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:
npm run validate -- --config tools - Ensure IBM i credentials are correct
- Verify Mapepire is running on IBM i:
sc check mapepire - Check server logs for tool loading errors
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
- Verify credentials with:
node get-access-token.js --verbose - Ensure user has database authorities
Advanced Configuration
Multiple IBM i Systems
Configure multiple server instances for different IBM i systems:Custom Tool Sets
Load specific toolsets instead of all tools:Next Steps
Configuration Reference
Explore all environment variables and settings
SQL Tools
Learn how to create custom SQL tools
Authentication
Set up secure IBM i HTTP authentication
Other Clients
Explore other MCP-compatible clients