Platform Support: macOS, Linux, Windows
Transport Modes: Stdio (local) and HTTP (remote)
Configuration:
~/.gemini/settings.jsonConfiguration File Location
Gemini CLI stores its MCP server configuration at:~ is your home directory.
Local (Stdio) Setup
Step 1: Install Gemini CLI (if not already installed)~/.gemini/settings.json and add the following to the mcpServers object:
Remote (HTTP) Setup
For connecting to a remote IBM i MCP Server: Step 1: Start remote server~/.gemini/settings.json:
Testing the Connection
After configuration:Multiple Servers
You can configure multiple MCP servers for different purposes:Troubleshooting
Server Not Found
Server Not Found
Solutions:
- Verify
~/.gemini/settings.jsonexists and has valid JSON - Check that
npx -y @ibm/ibmi-mcp-server@latestworks from terminal - Ensure Node.js and npm are in PATH
- Restart Gemini CLI after configuration changes
Tools Not Loading
Tools Not Loading
Solutions:
- Verify tools path is absolute:
/full/path/to/tools - Check YAML files are valid
- Ensure IBM i credentials are correct
- Verify Mapepire is running on IBM i
Authentication Failed (Remote)
Authentication Failed (Remote)
Solutions:
- Confirm server is running with auth enabled
- Verify token hasn’t expired
- Get fresh token:
node get-access-token.js --verbose - Check Authorization header format
Custom Toolsets
Load specific toolsets for focused workflows:Next Steps
SQL Tools
Create custom SQL operations
Configuration
Explore all configuration options
Quick Start
Basic server setup
Other Clients
Explore other MCP clients