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
aichat_create_conversation and aichat_create_conversation_v2 appear to serve the same core purpose, with the v2 tool lacking a clear description of how it differs. An agent cannot reliably choose between them, though list_models and get_usage_guide are distinct.
All tools use a consistent aichat_ prefix and mostly follow a verb_noun pattern such as create_conversation, get_usage_guide, and list_models. The _v2 suffix is a minor deviation but still readable and consistent with versioning conventions.
Four tools is a reasonable count for a lightweight chat API wrapper, but one of them is a duplicate/versioned variant and another is a meta usage guide rather than a core operation. The set feels slightly thin and unevenly scoped.
The surface covers creating conversations, listing models, and getting usage guidance, but lacks clear operations for retrieving, listing, or deleting existing conversations. The v2 tool may fill some gaps, but its vague description leaves lifecycle coverage uncertain.