AiChat MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACEDATACLOUD_API_TOKEN | Yes | Your AceDataCloud API token |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aichat_create_conversationA | Create an AI conversation using the AiChat API. |
| aichat_create_conversation_v2C | Create/manage conversations via AiChat v2 endpoint. |
| aichat_list_modelsA | List all available AI models for the AiChat API. |
| aichat_get_usage_guideA | Get a comprehensive guide for using the AiChat tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| aichat_guide | Guide for choosing the right AiChat tool and model for AI conversation tasks. |
| aichat_workflow_examples | Common workflow examples for AiChat tasks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.