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_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_blogs_categoriesB | List blogs categories. 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 tool clusters are hard to separate: get_services_apis vs list_apis vs get_api_spec vs get_apis_id, list_datasets vs get_datasets_id, list_integrations vs get_integrations_id, and get_model vs list_model_catalog all appear to return overlapping catalog data. A few descriptions do disambiguate well (search_docs vs list_docs, get_pricing vs get_public_usage_packages), but the path-derived tools ("Get apis id", "Get coin policies id") give an agent no way to choose between them and their list counterparts.
The acedatacloud_ prefix and snake_case are applied uniformly, but the verb_noun convention collapses in the auto-generated REST-path names: get_apis_id, get_services_apis, get_coin_policies_id, and acedatacloud_get_documents_openapi.json (which even embeds a filename extension). Entity-first names (list_blog_posts, get_blog_post) coexist with path-derived names, so the pattern is not predictable from a tool name alone.
28 tools exceeds a comfortable surface for what is essentially one read-only catalog domain, and several tools are thin one-to-one wrappers over backend endpoints rather than distinct capabilities. The count is inflated by redundant list/get pairs that could be consolidated into parameterized tools.
The public browsing surface (services, models, APIs, datasets, integrations, docs, blog, announcements, pricing) is broad and covers most discovery needs with no obvious read gap. However, the guide references a "write-confirmation model" while no create/update/delete or invocation tools exist, and there is no account, usage-consumption, or checkout path beyond the isolated recharge-card/usage-query tools.