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
- AlicenseAqualityFmaintenanceAn 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.3535 npm20MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server for OpenAI API access via AceDataCloud, enabling chat completions, image generation, text embeddings, and more from MCP-compatible clients.111,137 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceMulti-model MCP server enabling code generation, visual analysis, and complex reasoning via Qwen3 models.MIT
TDQS
Scored across 4 tools
aichat_create_conversation and aichat_create_conversation_v2 clearly overlap, and the v2 description ('Create/manage conversations via AiChat v2 endpoint') gives no guidance on when to prefer it over v1. An agent cannot reliably choose between the two, and the '_v2' variant's 'manage' scope is undefined.
All tools share the aichat_ prefix and a consistent verb_noun pattern (list_models, create_conversation, get_usage_guide). The only deviation is the _v2 suffix on one tool, which is a minor inconsistency.
Four tools is on the thin side for an AI chat API, and one of them (get_usage_guide) is a documentation helper rather than a functional operation. Reasonable but borderline under-scoped.
Core chat (create conversation) and discovery (list models) are covered, but conversation lifecycle is incomplete: no get/history, list, or delete conversation operations, and the 'manage' claim in v2 is not backed by distinct tools.