Unichat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNICHAT_MODEL | Yes | The Unichat model to use (e.g., gpt-4o-mini) | |
| UNICHAT_API_KEY | Yes | Your API key for the selected model's provider (OpenAI, MistralAI, Anthropic, xAI, Google AI or DeepSeek) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unichatC | Chat with an assistant. Example tool use message: Ask the unichat to review and evaluate your proposal. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code_review | Review code for best practices, potential issues, and improvements |
| document_code | Generate documentation for code including docstrings and comments |
| explain_code | Explain how a piece of code works in detail |
| code_rework | Apply requested changes to the provided code |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'unichat' has a clear and distinct purpose of chatting with an assistant.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'unichat' follows a simple, readable pattern without any conflicting conventions.
A single tool is too few for most server purposes, as it severely limits functionality and scope. While it might be appropriate for a minimal chat interface, it feels thin and lacks the depth expected for a typical MCP server, which usually requires multiple tools to handle different operations or resources.
For a chat assistant domain, the single tool 'unichat' covers the core action of chatting, but there are notable gaps. It lacks operations for managing chat history, configuring settings, or handling multiple sessions, which are common in chat systems. However, the basic functionality is present, allowing agents to perform the primary task.