Documentation Index
Fetch the complete documentation index at: https://mintlify.com/coollabsio/jean/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Jean supports the Model Context Protocol (MCP), allowing you to extend AI capabilities with custom tools and data sources. MCP servers can be configured globally or per-project, and work across all three supported backends: Claude CLI, Codex CLI, and OpenCode.Configuration Files
MCP servers are configured through backend-specific files:Claude CLI
- Global:
~/.claude.json- Applied to all sessions - Project:
.mcp.jsonin project root - Overrides global config
Codex CLI
- Global:
~/.codex/config.toml- Applied to all sessions - Project:
.codex/config.tomlin project root - Overrides global config
OpenCode
- Global:
~/.config/opencode/opencode.json- Applied to all sessions - Project:
opencode.jsonin project root - Overrides global config
Managing MCP Servers
Viewing Available Servers
- Open Preferences (
Cmd/Ctrl + ,) - Navigate to MCP Servers tab
- View servers grouped by backend (Claude, Codex, OpenCode)
Enabling/Disabling Servers
Global Level (all projects):- In Preferences > MCP Servers, toggle individual servers
- Changes apply to all new sessions across all projects
- Right-click project in sidebar > Project Settings
- Navigate to MCP Servers tab
- Toggle project-specific servers
- Project settings override global defaults
Per-Session Configuration
You can override MCP servers for individual sessions:- Open chat session
- Click the MCP icon in toolbar
- Enable/disable specific servers for this session
- Changes apply immediately
Health Checks
Jean includes built-in MCP health monitoring:- Preferences > MCP Servers
- Click Check Health button
- View status for each server (running/stopped/error)
Auto-Enabling New Servers
Jean automatically enables newly discovered MCP servers based on these rules:- Not explicitly disabled by user
- Not already enabled in current config
- Not in known servers list (prevents re-enabling user-disabled servers)
Configuration Examples
Claude CLI (.claude.json)
Codex CLI (config.toml)
OpenCode (opencode.json)
Backend Isolation
MCP servers are isolated by backend:- Claude sessions only load servers from Claude config
- Codex sessions only load servers from Codex config
- OpenCode sessions only load servers from OpenCode config
Default Enabled Servers
You can configure which servers are enabled by default: Global Defaults:Troubleshooting
Server Not Appearing
- Verify config file syntax (JSON/TOML)
- Check file location matches backend
- Restart Jean to reload config
Server Showing as Unhealthy
- Run manual health check from Preferences
- Check server command exists:
which npx - Verify environment variables are set
- Review Jean logs: Help > Open Logs Folder
Server Not Loading in Session
- Verify server is enabled for current backend
- Check project-level overrides aren’t disabling it
- Confirm session is using correct backend (Claude/Codex/OpenCode)
Best Practices
- Start with global config: Set up common servers in global config
- Use project overrides sparingly: Only override when project needs differ
- Test health regularly: Run health checks after config changes
- Keep servers updated: Update MCP server packages regularly
- Disable unused servers: Reduce overhead by disabling unnecessary servers
Security Considerations
- Never commit tokens: Use environment variables for sensitive data
- Restrict filesystem access: Limit server paths to necessary directories
- Review server code: Audit third-party MCP servers before use
- Use project configs for secrets: Store project-specific tokens in project config (not committed)