mcp-client-console
MCP client that connects to a remote MCP server, LLM backend (API key or local model) and preset configuration files.
Intended for use within private network for Cybersecurity purposes.
System: {user} <--> mcp-client-console <--> network <--> {box} <--> mcp-server-remote <--> tools
Client: {user} <--> cli.py <--> client.py <--> mcp SDK <--> * <--> mcp-server-remote
User Guide | LLM Backend Setup
Skip this section if using an API LLM connection. For a local model, set up Ollama before installing the client:
curl -fsSL https://ollama.com/install.sh | sh # Linux. macOS: brew install ollama. Windows: winget install Ollama.Ollama
ollama pull qwen2.5:14b # default model in config_default.toml
ollama list # confirm Ollama is running and the model is pulled
To use a different model, pull it the same way and update model under [llm.local] in your config.toml to match the tag exactly. host under [llm.local] must include the full scheme: http://127.0.0.1:11434... not 127.0.0.1:11434.
User Guide | Installation
Users:
pipx install mcp-client-console
mcp-client-console
Developers:
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 .
mcp-client-console
User Guide | Configuration
First run creates a default config.toml and prints its filepath (the /config command in the terminal chat prints it too). Edit it... populate with server name, url, token:
[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 |
User Guide | Operation
Start your MCP server first (see repos below) and confirm the client is configured to reach it. The client connects, performs the MCP handshake, and lists the server's tools. Use LLM natural language in the CLI to access tools on the remote box:
$ mcp-client-console
Connected to Box_1 @ http://127.0.0.1:9000/mcp
How may I help you today?
Related / Required Repos
Project Status
- Create MCP client repo
- Connect to MCP server locally
- LLM backend (API / local Ollama) added to client
- Connect to MCP server remotely (e.g. over the internet)
- Add TLS + bearer auth as requirement
1 maintainer
Release files for mcp-client-console 0.4.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_client_console-0.4.3.tar.gz | 42.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_client_console-0.4.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.3 kB
Release files / mcp_client_console-0.4.3.tar.gz
| Download URL | mcp_client_console-0.4.3.tar.gz |
|---|---|
| Size | 42.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d10485f31710c0d5966c648b69008d4660b5d98a0bd6169ec64dce8c3e8e7a7
|
|
BLAKE2b-256 checksum How to use checksums |
36e72c54706d6586440677bcda393f88df65d35301cf4e028ef4a5d9817bd1de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency logRelease files / mcp_client_console-0.4.3-py3-none-any.whl
| Download URL | mcp_client_console-0.4.3-py3-none-any.whl |
|---|---|
| Size | 54.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d2bea3ee9dd5bea3871c4dfe8c4876aabf366f44889c5b1a70fa9c065049dd7
|
|
BLAKE2b-256 checksum How to use checksums |
0a87cca38d9ec9a57270214938a9f3f9db1e5f68c89c88e31599cba89d91f33b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency log
