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 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.