Skip to main content
Glama
fast-h3yun

fast-h3yun

by ironfrancis

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

h3yun_login

Log in with phone number and password. mobile / password required

h3yun_session_info

Current user and engine

h3yun_list_apps

App list

h3yun_list_forms

Forms under a given app

h3yun_search_forms

Search forms by name

h3yun_query_records

Query records with pagination

h3yun_get_record

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-h3yun

Default 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

H3YUN_MOBILE

Login phone number. If not set, h3yun_login must be called

H3YUN_PASSWORD

Login password. If not set, h3yun_login must be called

H3YUN_ENGINE_CODE

Specify the engine for multi-engine accounts

H3YUN_TOKEN

Fallback JWT when a captcha blocks password login

H3YUN_BASE_URL

Default https://www.h3yun.com

H3YUN_HOST / H3YUN_PORT

Default 127.0.0.1 / 8765

Limitations

  • The web /v1 has 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_CODE from 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 pytest

License

MIT. Feel free to check out CONTRIBUTING.md and SECURITY.md.

Available Tools

7 tools
h3yun_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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    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).

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      C
      quality
      C
      maintenance
      Enables read-only querying of Kingdee's Three-Effect project management system, covering projects, reimbursements, loans, payments, working hours, and budgets, via MCP tools.
      28
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only queries of i桂航 campus data, including schedules, classes, terms, and campus information through MCP tools.
      -