Skip to main content

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

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mcp_client_console-0.3.2.tar.gz (37.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

mcp_client_console-0.3.2-py3-none-any.whl (50.5 kB view details)

Uploaded Python 3

File details

Details for the file mcp_client_console-0.3.2.tar.gz.

File metadata

  • Download URL: mcp_client_console-0.3.2.tar.gz
  • Upload date:
  • Size: 37.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.5

File hashes

Hashes for mcp_client_console-0.3.2.tar.gz
Algorithm Hash digest
SHA256 6e32035f068f720659c120ebd1c461ceb70e0f64095a1c91877fc29d4db1698a
MD5 7995548f89e7674000c7cdc8679e7b3f
BLAKE2b-256 480034babd22438e61e577e3fd2245dd12589f2d8055eb946232bac695e5ded8

See more details on using hashes here.

File details

Details for the file mcp_client_console-0.3.2-py3-none-any.whl.

File metadata

File hashes

Hashes for mcp_client_console-0.3.2-py3-none-any.whl
Algorithm Hash digest
SHA256 553ebe8f36e722fe59d7a37b7ca9ef7c20ef8318fd38d46459a12f350bc41e4b
MD5 d5d1108b818e170cce03f0dc1d524504
BLAKE2b-256 7a7832e065a0461e7e523dcc7a6fe7683556e4a6036693cbccbef374601535b5

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page