AiChat MCP Server
OfficialRelated Servers
Alternatives to AiChat MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server for Grok (xAI) that enables chat, reasoning, vision, and video generation using the AceDataCloud API.81MIT
- AlicenseBqualityDmaintenanceAn MCP protocol server that supports multi-AI personality summoning and collaboration, which can be used for intelligent collaboration in multiple scenarios such as code analysis and product design.41Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that enables AI applications to access 20+ model providers (including OpenAI, Anthropic, Google) through a unified interface for text and image generation.230MIT
- AlicenseAqualityAmaintenanceMCP server for DeepSeek AI models (Chat + Reasoner). Supports multi-turn sessions, model fallback with circuit breaker, function calling, thinking mode, JSON output, multimodal input, and cost tracking.3335 npm19MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol server for OpenAI API access via AceDataCloud, enabling chat completions, image generation, text embeddings, and more from MCP-compatible clients.111MIT
- AlicenseNot gradedqualityDmaintenanceMulti-model MCP server enabling code generation, visual analysis, and complex reasoning via Qwen3 models.MIT
TDQS
Scored across 4 tools
The two conversation creation tools (aichat_create_conversation and aichat_create_conversation_v2) overlap heavily and leave it unclear when to use which, despite the v2 suffix. The list_models and usage guide tools are distinct, but the primary workflow has ambiguous entry points.
All tools share the aichat_ prefix and follow a consistent verb_noun pattern: create_conversation, create_conversation_v2, list_models, get_usage_guide. The v2 suffix is a clear and predictable variant.
Four tools is a reasonable size for a focused chat API server. However, one tool is a usage guide rather than a functional operation, and create_conversation_v2 appears redundant, making the effective count feel slightly padded.
The core capabilities of listing models and creating/continuing conversations are present, but there is no explicit way to retrieve conversation history, manage prior conversations, or delete them. The domain is simple enough that these may not be required, but the v2 tool suggests unfinished coverage.