fast-h3yun
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fast-h3yun list all apps in my H3 Yun workbench"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Log in with your own H3Yun account and turn the apps, forms, and records in the web workbench into FastMCP tools. Use them for queries from Cursor, OPC Feed, or other MCP clients.
This is not an official H3Yun product, nor the official OpenAPI. The session comes from web login: phone number + password → JWT + EngineCode. What you can see depends on the permissions of the logged-in user.
What it can do
Tool | Purpose |
| Log in with phone number and password. |
| Current user and engine |
| App list |
| Forms under a given app |
| Search forms by name |
| Query records with pagination |
| Get one record by ObjectId |
First version is read-only: no create, modify, delete, or approval.
Related MCP server: Feishu MCP Server
Getting started
Requires Python 3.12+ and uv. It is recommended to use a read-only H3Yun account with narrowed permissions.
git clone https://github.com/ironfrancis/fast-h3yun.git
cd fast-h3yun
cp .env.example .env
uv sync --extra dev
uv run fast-h3yunDefault address: http://127.0.0.1:8765/mcp
You can prefill H3YUN_MOBILE / H3YUN_PASSWORD in .env. It can also start without them; after connecting, call h3yun_login first.
Connecting to an MCP client
{
"mcpServers": {
"h3yun": {
"url": "http://127.0.0.1:8765/mcp"
}
}
}OPC Feed goes through mcp_connection_parse → probe → propose. For Cursor, configure the same URL in the MCP settings. Keep the account and password in this service; do not write them into the client repository.
Environment variables
Variable | Description |
| Login phone number. If not set, |
| Login password. If not set, |
| Specify the engine for multi-engine accounts |
| Fallback JWT when a captcha blocks password login |
| Default |
| Default |
Limitations
The web
/v1has no official stability guarantee; H3Yun releases may change fields.Too many wrong password attempts will lock the account; this service caches the token and rate-limits login.
Online password login may trigger an Alibaba Cloud captcha. For unattended use, switch to an already-logged-in
H3YUN_TOKEN+H3YUN_ENGINE_CODEfrom the browser.The MCP service itself does not authenticate callers. By default it only listens on localhost; do not expose the port to the public internet.
Do not commit
.env, tokens, or EngineSecret. Tool return values strip password / token.
uv run pytestLicense
MIT. Feel free to check out CONTRIBUTING.md and SECURITY.md.
Available Tools
7 toolsh3yun_get_recordA
Load one business record by ObjectId.
Inputs: object_id (required), schema_code (required). Returns: object
h3yun_list_appsB
List applications visible to the signed-in user.
Inputs: no named parameters. Returns: object
h3yun_list_formsB
List form nodes under one application.
Inputs: app_code (required), forms_only. Returns: object
h3yun_loginA
Sign in to H3 Yun with mobile and password. Required before other tools unless env credentials are set.
Inputs: mobile (required), password (required), engine_code. Returns: object
h3yun_query_recordsA
Query business records for one form. Respects the signed-in user's data scope.
Inputs: schema_code (required), keyword, page_size, page_index. Returns: object
h3yun_search_formsB
Search forms by keyword across the current engine.
Inputs: keyword (required). Returns: object
h3yun_session_infoA
Return the signed-in H3 Yun user and current engine (tenant).
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Find, document and execute authenticated API calls across 1000+ apps via one MCP server
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Governed MCP gateway for business apps: roles, previews, approvals and one audit log.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables to operate a WeChat Official Account via MCP tools, including searching and executing API workflows and uploading files.MIT
- FlicenseAqualityCmaintenanceEnables reading, creating, updating, and appending Feishu documents, as well as querying and updating Bitable fields and records via the MCP protocol.12-
- FlicenseCqualityCmaintenanceEnables read-only querying of Kingdee's Three-Effect project management system, covering projects, reimbursements, loans, payments, working hours, and budgets, via MCP tools.28-
- FlicenseNot gradedqualityCmaintenanceEnables read-only queries of i桂航 campus data, including schedules, classes, terms, and campus information through MCP tools.-