AceDataCloud MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level. | INFO |
| PLATFORM_API_BASE_URL | No | Management API base URL. | https://platform.acedata.cloud |
| PLATFORM_REQUEST_TIMEOUT | No | Request timeout in seconds. | 30 |
| ACEDATACLOUD_PLATFORM_TOKEN | Yes | Your AceDataCloud platform token (starts with platform-). Required. |
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 |
|---|---|
| acedatacloud_list_blog_postsB | List published articles or videos. No account or blog permission required. |
| acedatacloud_get_blog_postA | Read a published article or video with localized source fields. |
| acedatacloud_get_serviceA | Get one service's full detail: title, description, type, unit, free_amount
and its display pricing ( |
| acedatacloud_get_pricingA | Get billing unit, free amount and display cost rules. Public contact-only datasets also return pricing_mode and any reference_quote, not checkout prices. No token required. |
| acedatacloud_get_public_usage_packagesA | Get one service's public Usage packages for Credit-to-USD pricing. The pricing reader returns Credit cost rules, but not the package amount/price pairs. Package ladders can differ between services, so the generic model catalog's ladder must not be substituted for this service. Fail closed if the public service detail cannot be read. |
| acedatacloud_list_apisA | List API endpoints, optionally scoped to one |
| acedatacloud_get_api_specA | Get one API endpoint's OpenAPI spec ( |
| acedatacloud_list_datasetsA | List downloadable datasets (title, price, download/preview URLs). No token required. |
| acedatacloud_list_integrationsA | List third-party integrations (title, options, stage). No token required. |
| acedatacloud_search_docsA | Full-text search the AceDataCloud documentation. Returns matching docs with alias, title, snippet and url. No token required. |
| acedatacloud_list_docsA | Browse documentation pages (newest/ranked), optionally filtered by |
| acedatacloud_get_docA | Fetch one documentation page's full content by its UUID. No token required. |
| acedatacloud_get_usage_guideA | Get a guide for using the AceDataCloud platform management tools. Explains the available tools, the write-confirmation model, and the authentication requirements. |
| acedatacloud_get_services_apisC | Get services apis. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_get_services_proxiesC | Get services proxies. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_list_site_home_sections_publicC | List site home sections public. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_get_apis_idC | Get apis id. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_get_apis_usageC | Get apis usage. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_get_datasets_idC | Get datasets id. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_get_integrations_idC | Get integrations id. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_get_documents_openapi.jsonC | Get documents openapi.json. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_get_recharge_cards_allocations_tokenC | Get recharge cards allocations token. Backend account permissions and ownership checks apply. Required permissions: applications:read |
| acedatacloud_get_coin_policies_idC | Get coin policies id. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_list_showcasesC | List showcases. Backend account permissions and ownership checks apply. Required permissions: public |
| acedatacloud_list_model_catalogA | List the model catalog with provider, modality and per-model credit pricing. Returns the modality counts plus matching models. No token required. |
| acedatacloud_get_modelA | Look up models by id/name (case-insensitive substring) with their credit pricing and capabilities. No token required. |
| acedatacloud_list_servicesA | List the services available on the AceDataCloud platform. |
| acedatacloud_list_announcementsA | List published platform announcements (newest first). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| acedatacloud_guide | Guide for managing an AceDataCloud account via the platform tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Several tools overlap heavily around APIs, docs, services, datasets, and integrations: for example, list_apis vs get_services_apis vs get_apis_id vs get_api_spec, or list_docs vs search_docs vs get_doc vs get_documents_openapi.json. Multiple autogenerated-looking get_*_id tools have vague descriptions that do not clearly distinguish them from their list_* counterparts. This creates real misselection risk.
All tools use the acedatacloud_ prefix and snake_case, which is consistent, but the noun patterns are uneven and sometimes awkward. Names like get_apis_id, get_services_apis, list_site_home_sections_public, and get_documents_openapi.json break from a clean verb_noun convention. The set remains readable but not fully predictable.
With 28 tools, the set is heavy for the apparent scope and includes several autogenerated or low-value endpoints that feel redundant. The count exceeds the typical well-scoped range and likely burdens tool selection. A leaner surface focused on core platform resources would be more appropriate.
The server covers many read-oriented platform areas: services, APIs, pricing, docs, blog posts, datasets, integrations, models, announcements, and showcases. However, it lacks clear write/update/delete lifecycle coverage despite references to a write-confirmation model, and some resources only have odd partial access points. Notable gaps remain for an agent trying to manage the platform end-to-end.