Skip to content

Add workflow MCP authoring and device-flow support#1981

Open
Y1fe1Zh0u wants to merge 19 commits intodataelement:feat/2.4.0from
Y1fe1Zh0u:feat/bisheng-mcp
Open

Add workflow MCP authoring and device-flow support#1981
Y1fe1Zh0u wants to merge 19 commits intodataelement:feat/2.4.0from
Y1fe1Zh0u:feat/bisheng-mcp

Conversation

@Y1fe1Zh0u
Copy link
Copy Markdown
Collaborator

@Y1fe1Zh0u Y1fe1Zh0u commented Apr 14, 2026

Summary

Expose Bisheng workflow capabilities to external agents through MCP, so outside agents can discover, read, author, and invoke workflows through a standardized protocol instead of relying only on the Bisheng product UI. This change also adds the key pieces needed for real usage, including workflow authoring, condition-node compatibility, authentication, and device-flow login, making external integration both practical and controlled.

通过 MCP 向外部 Agent 开放 Bisheng 工作流能力,使外部智能体可以通过标准化协议发现、读取、编排并调用工作流,而不再只能依赖 Bisheng 站内页面完成操作。此次改动同时补齐了工作流 authoring、条件节点兼容、鉴权与 device flow 登录等关键能力,让外部接入在可用性和安全性上都达到可落地状态。

Testing

  • src/backend/.venv/bin/python -m pytest -q src/backend/test/test_mcp_device_flow.py src/backend/test/test_external_workflow_service.py
  • src/backend/.venv/bin/python -m pytest -q src/backend/test/test_workflow_mcp_e2e.py

Y1fe1Zh0u and others added 19 commits March 17, 2026 18:44
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
# Conflicts:
#	src/frontend/client/src/routes/index.tsx
…t 开放 Bisheng 工作流能力

Expose Bisheng workflow capabilities to external agents through MCP, so outside agents can discover, read, author, and invoke workflows through a standardized protocol instead of relying only on the Bisheng product UI. This change also adds the key pieces needed for real usage, including workflow authoring, condition-node compatibility, authentication, and device-flow login, making external integration both practical and controlled.
通过 MCP 向外部 Agent 开放 Bisheng 工作流能力,使外部智能体可以通过标准化协议发现、读取、编排并调用工作流,而不再只能依赖 Bisheng 站内页面完成操作。此次改动同时补齐了工作流 authoring、条件节点兼容、鉴权与 device flow 登录等关键能力,让外部接入在可用性和安全性上都达到可落地状态。

Constraint: Need a clean commit boundary before switching to upstream/2.5.0-PM / 切换到 upstream/2.5.0-PM 前需要一个清晰的提交边界
Rejected: git stash | less visible and less durable than a branch-local checkpoint commit / 拒绝使用 git stash:可见性和持久性都不如分支内检查点提交
Confidence: medium / 中
Scope-risk: narrow / 范围窄
Reversibility: clean / 可干净回退
Directive: Curate or squash this checkpoint before merge if a cleaner history is required / 如需更干净的历史,请在合并前整理或压缩这个检查点提交
Tested: src/backend/.venv/bin/python -m pytest -q src/backend/test/test_mcp_device_flow.py src/backend/test/test_external_workflow_service.py; src/backend/.venv/bin/python -m pytest -q src/backend/test/test_workflow_mcp_e2e.py / 已验证:上述 MCP 相关后端测试
Not-tested: Full frontend build and manual end-to-end environment verification / 未验证:完整前端构建与手工端到端环境联调
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant