What databases does MyCLI support?

MyCLI supports MySQL, MariaDB, and Percona Server. It's designed for MySQL-compatible databases with auto-completion and syntax highlighting that actually works with MySQL SQL dialect.

How do I enable auto-completion in MyCLI?

Auto-completion should just work, but if it's not showing up, you probably have an old config file. Delete `~/.myclirc` and restart - that fixes it 90% of the time. If your database has 500+ tables, auto-completion will be slower than molasses.

Can I use MyCLI with SSL connections?

Yes, MyCLI supports SSL. Use options like `--ssl-cert`, `--ssl-key`, `--ssl-ca`, and `--ssl-verify-server-cert` to configure secure connections. SSL settings can also be stored in the configuration file.

How do I connect when IT gave me a VPN that breaks everything?

Use SSH tunneling: `mycli --ssh-host jumpbox.company.com --ssh-user youruser -h 10.0.0.123`. Takes forever to type but works when nothing else will. If you get `(2003, "Can't connect to MySQL server on 'localhost'")`, MyCLI tried the socket first and failed - just wait for it to retry over TCP/IP.

Where is the MyCLI configuration file located?

The configuration file is located at `~/.myclirc` in your home directory. It's automatically created on first launch and contains settings for colors, keybindings, auto-completion, and connection defaults.

How do I save and reuse favorite queries?

Save a query using `\fs alias query_text` and execute it later with `\f alias`. Favorite queries are great once you remember to actually use them. They support parameters, so you can do `\fs users SELECT * FROM users WHERE status = ?` and call it with arguments.

Can I change the color scheme or syntax highlighting?

Yes, MyCLI supports multiple [color themes](https://www.mycli.net/syntax). Modify the `syntax_style` setting in `~/.myclirc` to choose from themes like default, monokai, vim, or others.

How do I enable query logging?

Enable logging by adding `log_file = ~/.mycli.log` to your configuration file or use the `-l` command-line option. This logs all queries and results for audit or debugging purposes.

Why should I use MyCLI instead of the standard MySQL client?

The standard MySQL client makes you feel like you're using telegraph equipment. MyCLI adds auto-completion that saves your ass when you can't remember if it's `user_id` or `userid`, syntax highlighting so you don't accidentally run `DELET` instead of `DELETE`, and error messages that actually make sense.

Is MyCLI compatible with my existing MySQL setup?

Yes, MyCLI uses the same connection protocols and authentication methods as the standard MySQL client. It works with existing MySQL users, privileges, and connection configurations.

How do I update MyCLI to the latest version?

Update using `pip install -U mycli` for pip installations, `brew upgrade mycli` for Homebrew on macOS, or use your system's package manager for distribution-specific packages. Sometimes updates break your workflow - if something's working, maybe don't update it right before a deadline.

Can I use MyCLI in scripts or automation?

Yes, but why would you? Use the regular `mysql` client for scripts. MyCLI is for interactive work where you actually want to be productive.

Why does MyCLI randomly disconnect during long queries?

Usually a [timeout issue](https://github.com/dbcli/mycli/issues/564) on the MySQL side. Check your `wait_timeout` and `interactive_timeout` settings. If you're seeing `Protocol error, expecting EOF`, your connection probably got reset mid-query.

How do I stop it from logging my passwords in plain text?

Don't put passwords on the command line. Use [mysql_config_editor](https://dev.mysql.com/doc/refman/8.0/en/mysql-config-editor.html) to store credentials or put them in `~/.my.cnf`. If you must use command line passwords, at least put a space before the command so it doesn't go in your shell history.

Can I make it shut up about SSL warnings?

Add `ssl_disabled = True` to your `~/.myclirc` file. Or properly configure SSL if you're connecting over the internet like a responsible adult.

Why is auto-completion slow as hell on our prod database?

Your schema has too many tables. MyCLI loads all table and column names for auto-completion. With 1000+ tables, this takes forever. You can disable it with `smart_completion = False` in your config, but then what's the point?

Currently viewing the AI version

Switch to human version

MyCLI: MySQL Terminal Client - AI-Optimized Technical Reference

Overview

MyCLI is a Python-based MySQL terminal client that replaces the standard MySQL client with intelligent auto-completion, syntax highlighting, and enhanced user experience. Built on prompt_toolkit library, actively maintained with 11.7k+ GitHub stars.

Critical Configuration Requirements

System Prerequisites

Python: 3.9+ required (3.8 will break mysteriously)
Database Support: MySQL, MariaDB, Percona Server
Platform Compatibility: macOS, Linux (Windows not officially tested but should work)

Installation Methods (Priority Order)

pip (Recommended): pip install -U mycli
- Warning: macOS Apple Silicon may show compilation warnings (ignorable)
- Failure Point: Dependency conflicts with existing PyMySQL installations
- Time Cost: 2-5 minutes, potentially hours if dependency hell occurs
Homebrew (macOS): brew update && brew install mycli
- Limitation: Lags 2 months behind pip releases
- Trade-off: Stability vs latest features
Distribution Packages:
- Ubuntu/Debian: sudo apt-get install mycli (ancient versions, use pip)
- Fedora: sudo dnf install mycli
- Arch/Manjaro: yay -S mycli

Configuration File Management

Location: ~/.myclirc (auto-created on first launch)
Critical Fix: Delete config file to resolve 90% of startup issues
Windows Unicode Issue: Delete and regenerate config if encountering em-dash encoding errors

Performance Characteristics and Failure Modes

Auto-completion Performance

Breaking Point: 200+ tables causes significant sluggishness
Failure Scenario: 1000+ tables makes auto-completion effectively unusable
Impact: Essential feature becomes counterproductive in large schemas
Workaround: smart_completion = False in config (defeats primary purpose)

Connection Reliability

Timeout Issues: Long queries disconnect due to MySQL wait_timeout and interactive_timeout
Error Pattern: "Protocol error, expecting EOF" indicates mid-query connection reset
Socket Connection: Initial connection attempts socket first, falls back to TCP/IP

Resource Requirements

Memory: Reasonable unless dealing with massive result sets
CPU: Python overhead vs C binary (standard MySQL client)
Network: Connection to large schemas takes significant time for metadata loading

Feature Implementation Reality

Auto-completion Intelligence

Context-Aware: SELECT * FROM <tab> shows tables, SELECT * FROM users WHERE <tab> shows columns
Failure Mode: Complex subqueries confuse the parser, suggests irrelevant completions
Real Benefit: Eliminates manual typing of long table names

Syntax Highlighting

Technology: Powered by Pygments library
Critical Value: Prevents DELETE without WHERE clause execution
Customization: Multiple themes available, custom themes possible
Reliability: Consistent highlighting reduces typo-based query errors

Enhanced User Experience vs Standard MySQL Client

Semicolon Requirement: Removed (major usability improvement)
Error Messages: Actually informative vs "helpful as fortune cookies"
Query Timing: Built-in timing display
Multiline Queries: Natural support without semicolon requirements

Security and Connection Considerations

SSL Configuration

Support Level: Full SSL options available
Command Options: --ssl-cert, --ssl-key, --ssl-ca, --ssl-verify-server-cert
Common Issue: SSL permission errors due to certificate file permissions
Disable Option: ssl_disabled = True in config (not recommended for internet connections)

SSH Tunneling

Use Case: When VPN breaks everything else
Syntax: --ssh-host jumpbox.company.com --ssh-user youruser
Initial Setup: "Pain in the ass the first time" but works reliably after configuration
Authentication: Supports both password and key-based authentication

Credential Management

Security Warning: Never put passwords on command line
Best Practice: Use mysql_config_editor or ~/.my.cnf
Shell History: Prefix command with space to avoid password logging

Operational Intelligence

Production Deployment Considerations

Schema Size Limitation: Performance degrades significantly with large table counts
Update Risk: Regular updates may break existing workflows
Script Usage: Not recommended for automation (use standard mysql client)
Debugging Sessions: Particularly valuable during 3am troubleshooting

Common Failure Scenarios

Large Schema Performance: 500+ tables cause sluggish auto-completion
Version Conflicts: Package manager versions lag behind pip
SSL Warnings: Improper SSL configuration creates noise
Connection Issues: Network timeouts during metadata loading
Unicode Issues: Windows encoding problems with configuration file

Quality Indicators

Community: Active GitHub issues (171 open) with responsive maintainers
Update Frequency: v1.38.4 released September 2025, regular maintenance
Documentation: Comprehensive and actually explains functionality
Support Channels: GitHub issues, discussions, and active community

Decision Criteria Matrix

Choose MyCLI When:

Interactive MySQL work required
Table names are long and difficult to remember
Syntax highlighting prevents costly mistakes
SSH tunneling needed for remote connections
Enhanced error messages improve productivity

Avoid MyCLI When:

Schema has 500+ tables (performance issues)
Automation/scripting requirements (use standard client)
Windows environment with Unicode complications
Minimal resource usage critical
Dependency management complexity unacceptable

Migration and Compatibility

Zero Migration Cost: Uses same connection protocols as standard MySQL client
Existing Setup: Works with current MySQL users, privileges, and configurations
Backward Compatibility: Can coexist with standard MySQL client
Risk Assessment: Low risk adoption with high productivity benefits

Resource Investment Analysis

Learning Curve: Minimal for MySQL users (enhanced familiar interface)
Setup Time: 5-15 minutes for basic installation
Troubleshooting Time: Potentially hours if hitting dependency conflicts
Productivity Gain: Significant for interactive database work
Maintenance Overhead: Low once properly configured

Useful Links for Further Investigation

Essential Resources and Documentation

Link	Description
MyCLI Website	The official homepage with installation instructions, feature overview, and getting started guide.
Documentation Hub	Documentation covering configuration, auto-completion, keybindings, logging, and advanced features. Actually explains things instead of assuming you're psychic.
GitHub Repository	Source code, issue tracking, releases, and community contributions. Over 11.7k stars and active development.
Installation Guide	Installation instructions that won't leave you googling dependency hell for 3 hours.
Configuration Reference	Guide to the ~/.myclirc file so you can make MyCLI work how you want instead of how someone else thinks it should.
Color Themes Gallery	Colors that don't look like someone threw up rainbow SQL all over your terminal.
Keybindings Documentation	Reference for Emacs and Vi keybinding modes and customization options.
Auto-completion Guide	How the magic tab completion works and when it doesn't (spoiler: large schemas).
Favorite Queries	How to save, organize, and use templated queries with parameters.
Multi-line Mode	Understanding and configuring multi-line query behavior.
Logging Configuration	Setting up query logging for audit trails and debugging.
SSH and SSL Connections	Secure connection setup including SSL certificates and SSH tunneling.
GitHub Issues	Bug reports, feature requests, and community discussions. 171 open issues - at least the maintainers actually respond unlike most projects.
GitHub Discussions	Community forum for questions, tips, and general discussion about MyCLI usage.
Contributing Guide	Guidelines for contributing code, reporting bugs, and participating in development.
pgcli	PostgreSQL equivalent with similar features and interface design.
Python Prompt Toolkit	The underlying library that powers MyCLI's interactive features.
dbcli Organization	Parent organization maintaining MyCLI, pgcli, and other database CLI tools.

MyCLI: MySQL Terminal Client - AI-Optimized Technical Reference

Overview

Critical Configuration Requirements

System Prerequisites

Installation Methods (Priority Order)

Configuration File Management

Performance Characteristics and Failure Modes

Auto-completion Performance

Connection Reliability

Resource Requirements

Feature Implementation Reality

Auto-completion Intelligence

Syntax Highlighting

Enhanced User Experience vs Standard MySQL Client

Security and Connection Considerations

SSL Configuration

SSH Tunneling

Credential Management

Operational Intelligence

Production Deployment Considerations

Common Failure Scenarios

Quality Indicators

Decision Criteria Matrix

Choose MyCLI When:

Avoid MyCLI When:

Migration and Compatibility

Resource Investment Analysis

Useful Links for Further Investigation

Essential Resources and Documentation

Related Tools & Recommendations

MySQL Workbench Performance Issues - Fix the Crashes, Slowdowns, and Memory Hogs

MySQL HeatWave - Oracle's Answer to the ETL Problem

MySQL to PostgreSQL Production Migration: Complete Step-by-Step Guide

MySQL Workbench - Oracle's Official MySQL GUI (That Eats Your RAM)

PostgreSQL vs MySQL vs MariaDB - Developer Ecosystem Analysis 2025

MariaDB - What MySQL Should Have Been

MariaDB Performance Optimization - Making It Not Suck

PostgreSQL Performance Optimization - Stop Your Database From Shitting Itself Under Load

PostgreSQL Logical Replication - When Streaming Replication Isn't Enough

Set Up PostgreSQL Streaming Replication Without Losing Your Sanity

DBeaver Community - If You Work With Databases and Don't Want to Pay for DataGrip

DBeaver Performance Optimization - Stop Waiting 30 Seconds for Your Database to Load

Microsoft Drops 111 Security Fixes Like It's Normal

Fix TaxAct When It Breaks at the Worst Possible Time

jQuery - The Library That Won't Die

Microsoft Windows 11 24H2 Update Causes SSD Failures - 2025-08-25

phpMyAdmin - The MySQL Tool That Won't Die

Migrate JavaScript to TypeScript Without Losing Your Mind

CPython - The Python That Actually Runs Your Code

Python - The Language Everyone Uses (Despite Its Flaws)