fast-h3yun
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| H3YUN_HOST | No | 仅 --http：默认 127.0.0.1 | 127.0.0.1 |
| H3YUN_PORT | No | 仅 --http：默认 8765 | 8765 |
| H3YUN_TOKEN | No | 验证码挡住密码登录时的兜底 JWT | |
| H3YUN_MOBILE | No | 登录手机号。不填则必须调用 h3yun_login | |
| H3YUN_BASE_URL | No | 默认 https://www.h3yun.com | https://www.h3yun.com |
| H3YUN_PASSWORD | No | 登录密码。不填则必须调用 h3yun_login | |
| H3YUN_ENGINE_CODE | No | 多引擎账号时指定引擎 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| h3yun_loginA | Sign in to H3 Yun with mobile and password. Required before other tools unless env credentials are set. |
| h3yun_session_infoA | Return the signed-in H3 Yun user and current engine (tenant). |
| h3yun_list_appsB | List applications visible to the signed-in user. |
| h3yun_list_formsB | List form nodes under one application. |
| h3yun_search_formsB | Search forms by keyword across the current engine. |
| h3yun_query_recordsA | Query business records for one form. Respects the signed-in user's data scope. |
| h3yun_get_recordA | Load one business record by ObjectId. |
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 7 tools
Each tool targets a distinct concern: auth, session, app discovery, form discovery, record fetch, and record query. Even the similar list_forms and search_forms are clearly separated by scope (one app vs. keyword across engine).
Most tools follow an h3yun_verb_noun pattern (list_apps, list_forms, get_record, query_records). Login and session_info deviate slightly from the full verb_noun structure, but the prefix keeps the set predictable.
Seven tools is well-scoped for an H3 Yun integration: authentication, session context, app/form discovery, and record retrieval are all covered without redundancy or bloat.
The read-oriented workflow is well covered: login, discover apps/forms, search forms, and fetch/query records. Write operations like creating or updating records are absent, but the tool set appears intentionally read-only, with only minor missing metadata capabilities.