MCP Client Console
geomux/mcp-client-console
Cliente MCP com CLI para acessar ferramentas remotas via LLM
Ver no GitHubCliente MCP em linha de comando que se conecta a servidores MCP remotos, backends LLM (API ou modelos locais) e arquivos de configuração presets. Permite interagir com ferramentas remotas através de linguagem natural via CLI, com suporte a autenticação e configuração centralizada.
Instalação
npx convez-ai geomux/mcp-client-console1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Conectar a servidores MCP remotos via CLI
- Executar ferramentas remotas com processamento de linguagem natural
- Integrar backends LLM locais ou por API em clientes MCP
- Gerenciar múltiplos servidores MCP através de configuração centralizada
Veredito

Ferramenta sólida para quem precisa acessar servidores MCP remotos via CLI com LLM. Projeto ainda em desenvolvimento (sem suporte remoto/TLS completo), adequado para ambientes de rede local ou experimentação. Boa escolha para integrações que exigem abstração de ferramentas remotas.
README
A tradução para o português deste README ainda está na fila.
mcp-client-console
MCP client that connects to a remote MCP server, LLM backend (API key or local model) and preset configuration files.
Remote MCP System Architecture Flowchart
{user} <--> mcp-client-console <--> network <--> {box} <--> mcp-server-remote <--> tools
mcp-client-console Architecture Flowchart
{user} <--> cli.py <--> client.py <--> mcp SDK <--> * <--> mcp-server-remote
User Guide | Installation
Users: install commands
:~$ pipx install mcp-client-console
:~$ mcp-client-console
Developers: install commands
git clone https://github.com/geomux/mcp-client-console.git
cd mcp-client-console
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
User Guide | Configuration
First run will create a default config.toml file and print the filepath to the config file.
Navigate to the filepath, edit the config file- populate with server name, url, token.
The client reads from "config.toml" to locate and access remote MCP server.
EXAMPLE:
[server]
name = "Box_1"
url = "http://127.0.0.1:9000/mcp"
OS Config Filepath
Linux: ~/.config/mcp-client-console/config.toml macOS: ~/Library/Application Support/mcp-client-console/config.toml Windows: %LOCALAPPDATA%\mcp-client-console\config.toml
/config command may be used to print filepath within the termianl chat.
User Guide | Operation
Start your MCP server first, see related / requires repos below.
Confirm the MCP client is configured to connect to the remote server location.
The client connects, performs MCP handshake, lists the available tools via the server.
Use LLM natural language processing in CLI to access tools on remote box.
EXAMPLE:
:~$ mcp-client-console
Connected to Box_1 @ http://127.0.0.1:9000/mcp
___
How may I help you today?
Related / Required Repos
mcp-server-remote
https://github.com/geomux/mcp-server-remote
mcp-gateway-remote
https://github.com/geomux/mcp-gateway-remote
--
Project Status
--
- Create MCP client repo
- Connect to MCP server locally
- LLM backend (API / local Ollama) added to client
- Connect to MCP server remotely with TLS + bearer auth