mcpField
C
Console Chat Gpt

Console Chat Gpt

github.com/amidabuddhaDesktop Apps158Updated 1d ago

About Console Chat Gpt

console-chat-gpt is a Python command line chat client for models from OpenAI, Anthropic, Google AI, Ollama and other OpenAI SDK compatible providers. It can load MCP servers from a config file for use in chat sessions. The README marks it as deprecated, with tellm named as its successor.

Key features

  1. 01Multiple providers via OpenAI SDK compatible endpoints
  2. 02Local models run through Ollama
  3. 03AI Managed mode selects a model per prompt
  4. 04MCP servers loaded from mcp_config.json
  5. 05Saved conversation history that can be resumed

Use cases

  1. 01Comparing answers from different providers in a terminal
  2. 02Chatting with local Ollama models from the command line
  3. 03Using existing MCP servers inside a command line chat

MCP support

The project acts as an MCP client. It reads server definitions from mcp_config.json and connects to those servers during chat sessions.

Details

From the project README

Deprecated / successor: For new installs, use tellm instead. It is a small Rust Telegram assistant for Claude, GPT/Grok, Gemini, compatible endpoints, and local Ollama, with per-room model selection and keychain-backed secrets.

console-chat-gpt v6

Your Ultimate CLI Companion for Chatting with AI Models

Enjoy seamless interactions with OpenAI, MistralAI, Anthropic, xAI, Google AI, or any other OpenAI SDK compatible LLM providers (such as DeepSeek, Alibaba, Inception, Moonshot AI, OpenRouter, etc.) or Ollama-hosted models directly from your command line.
Elevate your chat experience with efficiency and ease.

Homepage | Examples

Released under the Apache license. Working on Python 3.11+ README image README image README image README image

Table of Contents


DISCLAIMER: The intention and implementation of this code are entirely unconnected and unrelated to OpenAI, MistralAI, Anthropic, xAI, Google AI, nor any other LLM lab or related parties. There is no affiliation or relationship with OpenAI, MistralAI, Anthropic, xAI, Google, any other LLM lab or their subsidiaries in any form.


Features

  • :new: Support conversations via a Telegram bot, including Bot API 10.1 rich message formatting when available. How to create one: From BotFather to 'Hello World' :new:
  • :star: OpenAI image generation via Responses API. :star:
  • :star: OpenAI Responses API supported. :star:
  • :star: Run any OpenAI SDK compatible - just add the model structure with the relevant model_name and base_url to the config.toml file. :star:
  • :star: Run Ollama hosted models locally. Ollama should be installed and the selected models already downloaded :star:
  • :star: Anthropic Prompt caching Fully supported :star:
  • :star: Model Context Protocol (MCP) supported! If you are already using MCP servers just copy your claude_desktop_config.json to the root directory and rename to mcp_config.json to start using with any model! :star:
  • Unified chat completion function separated as independent library to be used in any application for seamless cross-provider API experience. The source code is available in Python and TypeScript
  • Streaming with all supported models, disabled by default, may be enabled in settings menu
  • OpenAI Assistants Beta supported
  • AI Managed mode Based on the complexity of the task, automatically determines which model to use.
  • Configuration File: Easily customize the app's settings through the config.toml file for complete control over how the app works. Also supported in-app via the settings command.
  • Role selection: Users can define the role of the AI in the conversation, allowing for a more personalized and interactive experience.
  • Temperature Control: Adjust the temperature of generated responses to control creativity and randomness in the conversation.
  • Command Handling: The app responds to various commands entered by the user for easy and intuitive interaction.
  • Image input: with selected models.
  • Error Handling: Clear and helpful error messages to easily understand and resolve any issues.
  • Conversation History: Review previous interactions and save conversations for future reference, providing context and continuity.
  • Graceful Exit: Smoothly handle interruptions, ensuring conversations are saved before exiting to avoid loss of progress.
  • A nice team: Actively adding features, open for ideas and fixing bugs.

Overall, this app focuses on providing a user-friendly and customizable experience with features that enhance personalization, control, and convenience.


Installation and Usage

The script works fine on Linux and MacOS terminals. For Windows it's recommended to use WSL.

  1. Clone the repository:

    git clone https://github.com/amidabuddha/console-chat-gpt.git
    
  2. Go inside the folder:

    cd console-chat-gpt
    
  3. Install the necessary dependencies:

    python3 -m pip install -r requirements.txt
    
  4. Get your API key from OpenAI, MistralAI, Anthropic, xAI, Google AI Studio, or the relevant platform, depending on your selected LLM.

  5. The config.toml.sample will be automatically copied into config.toml upon first run, with a prompt to enter your API key/s. Feel free to change any of the other defaults that are not available in the settings in-app menu as per your needs.

  6. Run the executable:

    python3 main.py
    

    Pro-tip: Create an alias for the executable to run from anywhere.

  7. Use the help command within the chat to check the available options.

  8. Enjoy


Configurable Options in config.toml
[chat.defaults]Main properties to generate a chat completion/response.
temperatureWhat sampling temperature to use, between 0 and 2. Higher values like 0.8 will make the output more random, while lower values like 0.2 more focused. May be set for each new chat session if adjust_temperature in [chat.features] is true.
system_roleA system (or developer) message inserted into the model's context. Should be one of the listed in [chat.roles] section. May be set for each new chat session if role_selector in [chat.features] is true.
modelModel ID used to generate the chat completion/response, like gpt-4o or o3. Should be listed in the [chat.models] section, with relevant parameters. May be set for each new chat session if model_selector in [chat.features] is true.
[chat.managed]Settings dedicated to the AI Managed mode. Not available to be edited from within a chat session.
assistantThe preferred model that will evaluate your prompt and select the best available model out of the four configured below to handle it. Should be listed in the [chat.models] section, with relevant parameters.
assistant_roleCustom instruction to the evaluation model. Change this only if you know exactly what you are doing!
assistant_generalistYour preferred general purpose model, typically the one you use the most for any type of queries. Should be listed in the [chat.models] section, with relevant parameters.
assistant_fastWhen speed is preferred to accuracy. Should be listed in the [chat.models] section, with relevant parameters.
assistant_thinkerA reasoning model for complex tasks. Should be listed in the [chat.models] section, with relevant parameters.
assistant_coderYour preferred model to handle Coding and Math questions. Should be listed in the [chat.models] section, with relevant parameters.
promptWhen AI Managed mode is used frequently the Y/N prompt may be disabled by changing this to false.
[chat.features]Configurable options of the chat application. Some are accessible from within a chat session via the settings command.
model_selectorA selection list of models available in section [chat.models] of config.toml. When true this list may be modified at the beginning of each new chat session.
adjust_temperaturePrompt to change the temperature for each chat session. When true the temperature value may be modified at the beginning of each new chat session.
role_selectorA selection list of roles available in section [chat.roles] of config.toml. When true this list may be modified at the beginning of each new chat session.
save_chat_on_exitWhen true automatically save the chat session upon using the exit command in chat.
continue_chatWhen true offers a list of previously saved chat sessions to be continued in a new session. The list may be modified from within a chat session via the chats command.
debugApplication logging - not yet implemented.
disable_intro_help_messageAll chat commands available in help are printed upon chat initialization. This is targeted at new users and may be disabled by setting to false.
assistant_modeEnable Open AI Assistants API as an available selection upon chat initialization.
ai_managedEnable AI Managed mode to allow a model to automatically select the best model according to your prompt. Detailed settings below.
streamingIf set to true, the model response data will be streamed to the terminal client. Telegram mode always sends completed replies.
mcp_clientSetting to false will prevent the default initialization of MCP servers for each chat if not needed.
[chat.telegram]Enable Telegram UI for cnversations.
enabledIf set to true, starts Telegram bot polling loop instead of the terminal chat UI.
bot_tokenTelegram bot token from BotFather, in the format <digits>:<token>.
allowed_chat_idsList of chat IDs allowed to use the bot. Pairing mode activates when this list is empty and no model room mappings (telegram_chat_id/telegram_chat_ids) are configured: the bot prints a one-time code in its terminal, and the chat that sends /pair <code> is claimed and saved here; all other chats are denied. The code rotates every 10 minutes and repeated wrong attempts lock the offending chat out temporarily.
admin_chat_idsList of chat IDs allowed to run admin-only commands such as /shutdown.
debug_contextIf true, prints Telegram session/memory debug snapshots to terminal logs for troubleshooting context issues.
max_concurrent_updatesMaximum number of Telegram updates processed in parallel. Default is 8 when omitted. Different chats run concurrently, while each chat remains strictly ordered and isolated.

Telegram replies are sent through sendRichMessage when the Bot API supports it, so model Markdown can render as rich headings, lists, tables, quotes, formulas, details blocks, and similar structured output. If rich message delivery is unavailable or Telegram rejects a malformed rich block, the bot falls back to the classic sendMessage path.

Per-model Telegram room mapping is also supported inside each model block via:

  • telegram_chat_id = <chat_id>
  • telegram_chat_ids = [<chat_id_1>, <chat_id_2>]

When a chat room is mapped to a model, that room is pinned to this model (model switching commands are disabled there), while all other commands (/mode, /role, /reasoning, /websearch, /webfetch, etc.) remain available.

Adding your OpenAI SDK supported model

Add an entry at the end of your config.toml file. Use the following example structure:

[chat.models.{{model name that makes sense to you}}]
api_key = "YOUR_API_KEY"
base_url = {{the custom base URL, for example "https://api.deepseek.com/v1"}}
model_input_pricing_per_1k = 0.015 (currently the price is not calculated but you may adjust this for your reference)
model_max_tokens = 32000 (the suported context window of the selected model)
model_name = {{model name exactly as specified in the relevant API reference, for example "deepseek-reasoner"}}
model_output_pricing_per_1k = 0.075 (currently the price is not calculated but you may adjust this for your reference)
reasoning_effort = (the desired value if supported, such as "medium", otherwise false)

Examples

  • Prompt example:

    example_python

  • Markdown visualization example:

    example_markdown

  • Settings and help:

    example_settings

You can find more examples on our Examples page.


Contributing

Contributions are welcome! If you find any bugs, have feature requests, or want to contribute improvements, please open an issue or submit a pull request.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.