The Model Context Protocol (MCP) establishes a standardized communication channel between large language models and external tools. With MCP, developers no longer need to write custom integrations for each external tool—Alibaba Cloud Bailian applications can seamlessly connect to a vast ecosystem of third-party tools.
One Key Service
The Bailian MCP Plaza offers a One Key Service experience—you only need one Bailian API Key to invoke One Key MCP services in the Plaza.
- No Secondary Activation: One Key MCP services require no separate activation or subscription—they take effect on first invocation.
- Unified Authentication: Use your Bailian API Key (DASHSCOPE_API_KEY) to access all One Key MCP services without obtaining separate keys for each service.
- Pay-As-You-Go: Billed by actual usage with no upfront fees or resource packages required. Some services include free quotas that automatically activate on first use.
How to Use MCP
Alibaba Cloud Bailian supports the following two types of MCP services, which can be integrated into Bailian Agents, Workflows, and other applications, or invoked remotely via Endpoint:
- Plaza MCP: Services listed in the MCP Plaza, visible to all users, including One Key MCP (no activation needed, API Key authentication) and MCP services that require manual activation. See Plaza MCP Services.
- Custom MCP: Deploy your own MCP services or integrate from open-source communities, visible only to yourself. See Custom MCP Services.
Billing Information
Plaza MCP
Plaza MCP services (including One Key MCP) have billing models that vary by service. For specific pricing details, please refer to the corresponding service card in the MCP Plaza. Some services are provided by third-party vendors through the Cloud Marketplace, with metering data pushed by the service provider to the Cloud Marketplace.
Custom-Deployed MCP Services
Bailian offers two billing models for custom-deployed MCP services, depending on the service's response latency:
| Basic Mode | Ultra-Fast Mode | |
|---|---|---|
| Deployment Fee | None | ¥0.000036/sec |
| Invocation Rate | ¥0.000156/sec | ¥0.000156/sec |
| Billing Rule | No charges when idle; billed by duration during invocation | Billed for deployment duration when idle; additional invocation charges during use |
| Use Case | Infrequent invocations, startup latency acceptable | Long-running, high-frequency invocation scenarios |