tianyan-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIANYAN_MCP_HOST | No | ASGI监听地址 | 127.0.0.1 |
| TIANYAN_MCP_PORT | No | ASGI监听端口 | 8000 |
| TIANYAN_LIVE_TEST | No | 只有值为1时才启用真实只读Smoke Test | 0 |
| TIANYAN_MCP_API_KEY | Yes | HTTP模式必填，去除首尾空白后至少32字符 | |
| TIANYAN_MCP_ALLOWED_HOSTS | No | 逗号分隔的主机名，不包含端口 | 127.0.0.1,localhost,::1 |
| TIANYAN_MCP_ALLOWED_ORIGINS | No | 逗号分隔的精确Origin；空值拒绝所有带Origin的请求 | |
| TIANYAN_HTTP_TIMEOUT_SECONDS | No | 天衍云请求超时，范围(0,60]秒 | 10 |
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 |
|---|---|
| list_available_quantum_backendsA | 查询当前运行中的天衍云量子计算机和量子仿真机。 backend_type 可为 all、quantum_computer 或 simulator。 每次调用都会实时读取天衍云公开列表接口，不使用缓存。 |
| get_quantum_backendA | 按资源 id 或 code 精确查询天衍云量子资源详情。 先匹配 id，再忽略 code 大小写进行完全匹配；不进行名称或模糊搜索。 |
| submit_quantum_experimentA | Submit and run one QCIS experiment circuit. This creates an experiment and consumes Tianyan cloud resources. Repeated calls may create duplicate tasks. The host must show the backend, circuit name, lab name, and shots to the user and obtain confirmation before submitting. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing backends, getting a specific backend's details, and submitting an experiment. There is no overlap or ambiguity between them.
All tool names follow a consistent snake_case verb_noun pattern: list_available_quantum_backends, get_quantum_backend, submit_quantum_experiment. This makes the naming predictable and clear.
With only 3 tools, the server is on the smaller end but still covers the primary actions needed for the domain. It is slightly thin but not problematically so.
The server supports listing backends, getting backend details, and submitting experiments, but there is no way to track experiment status, retrieve results, or cancel a submission. This leaves a significant gap in the experiment lifecycle.