What can you do with this server?

The YingDao RPA MCP Server enables the execution and management of Robotic Process Automation (RPA) applications through two modes: * Local Mode: * Query RPA application parameters * Query the list of available RPA applications * Run specific RPA applications * Open API Mode (Enterprise Only): * Upload files to the RPA platform * Query RPA application parameters * Get a paginated list of RPA applications * Start RPA jobs * Query the status of RPA jobs * Query the list of available RPA robots (clients) This server allows other MCP Host tools, such as YingDao AI Power, to interact with YingDao RPA.

Which integrations are available for this server?

Integrates with GitHub for repository cloning and project management for the MCP server itself Provides a local mode to run RPA applications that have been previously executed at least once, using the local ShadowBot executable

How do I use YingDao RPA MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@YingDao RPA MCP Server run the daily sales report automation" 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.

YingDao RPA MCP Server

Official

by ying-dao

Overview Schema Related Servers Score Discussions

TypeScript

Hybrid

影刀RPA MCP Server

影刀RPA:一个RPA低代码平台，一款人人可用的RPA自动化产品，能够将人从重复的劳动中解放出来。影刀AI Power:一个AI低代码平台，能够快速创建AI智能体、AI工作流，帮助用户把AI用起来。

影刀 RPA MCP Server 基于 Model Context Protocol (MCP) 实现，为影刀AI Power及其他可作为MCP Host的工具(如 Claude Desktop、Cursor 等)提供调用RPA的能力。

同时支持SSE Server与Stdio Server两种模式。

如何开始

支持两种方式来运行影刀RPA

本地模式

设置环境变量注意：本地模式下，智能获取并运行“我获取的应用”并已经被至少执行过一次的应用

RPA_MODEL=local
SHADOWBOT_PATH={your_shadowbot_path} //影刀rpa的exe路径
USER_FOLDER={your_user_folder}       //影刀rpa的用户文件夹路径

影刀RPA的exe路径

Windows 注意：windows下在AI Power客户端中，路径要使用双斜杠

D://Program Files//{安装目录}//ShadowBot.exe

Mac

/Applications/影刀.app

影刀RPA的用户文件夹路径

在影刀RPA的设置中，找用户文件夹选项

Related MCP server: Integrator MCP Server

开放API模式 (仅支持企业用户)

设置环境变量

RPA_MODEL=openApi
ACCESS_KEY_ID={your_access_key_id}
ACCESS_KEY_SECRET={your_access_key_secret}

获取方式

企业管理员登录影刀RPA控制台获取，请参考影刀RPA帮助文档-鉴权

Stdio Server启动

在客户端中配置

{
  "mcpServers": {
    "YingDao RPA MCP Server": {
      "command": "npx",
      "args": ["-y", "yingdao-mcp-server"],
      "env":{
        "RPA_MODEL":"openApi",
        "ACCESS_KEY_ID":"{your_access_key_id}",
        "ACCESS_KEY_SECRET":"{your_access_key_secret}"
      }
    }
  }
}

SSE Server配置

构建

Clone the repository and build:

git clone https://github.com/ying-dao/yingdao_mcp_server.git
cd yingdao_mcp_server
npm install
npm run build

配置

添加.env文件，配置项参考以上描述

启动

npm run start:server

客户端配置

AI Power 客户端配置

{
  "mcpServers": {
    "YingDao RPA MCP Server": {
      "url": "http://localhost:3000/sse",
      "description": "影刀 MCP Server"
    }
  }
}

默认端口为3000

能力

本地模式

queryRobotParam: 查询RPA应用的参数
queryApplist: 查询RPA应用的列表
runApp: 运行RPA应用

开放API模式

uploadFile: 上传文件到RPA平台
queryRobotParam: 查询RPA应用参数
queryApplist: 获取分页RPA应用列表
startJob: 启动RPA作业
queryJob: 查询RPA作业状态
queryClientList: 查询调度RPA机器人列表

License

MIT

Available Tools

6 tools

queryApplistB

该接口用于分页获取RPA应用列表。

ParametersJSON Schema

Name	Required	Description	Default
`appId`	No	RPA应用UUID
`size`	No	一页大小	30
`page`	No	页码	1
`ownerUserSearchKey`	No	用户账号精确匹配
`appName`	No	RPA应用名称模糊匹配

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry full burden. It only states basic purpose of paginated listing. No disclosure of rate limits, authentication, ordering behavior, or error conditions. Lack of behavioral details limits transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no unnecessary words. Front-loaded with core purpose. Highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paginated list tool with 5 parameters, the description is too brief. It does not explain return structure, default ordering, or how pagination works. More context is expected despite good schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions. Description does not add extra meaning beyond what is in the schema; it just paraphrases the pagination concept. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it is for paginated retrieval of RPA app list. Uses specific verb '分页获取' (paginate and get) and resource 'RPA应用列表'. Different from sibling tools which operate on different resources (clients, jobs, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, exclusions, or context such as required permissions. Single sentence does not address usage conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

queryClientListC

该接口用于查询RPA机器人列表。

ParametersJSON Schema

Name	Required	Description	Default
`status`	No	状态,idle表示空闲,一般不指定关键字的情况下都是要查询空闲的机器人
`key`	No	关键字
`robotClientGroupUuid`	No	RPA机器人组uuid
`page`	No	页码	1
`size`	No	一页大小	30

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, and the description does not disclose behavioral traits like read-only nature, required permissions, or side effects. For a query tool, read-only is implied but not stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence is concise and avoids verbosity, but it is overly terse given the tool has 5 parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal but covers the basic purpose. Without output schema, more detail on return values or pagination behavior would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers all parameters with descriptions (100% coverage). The description adds no extra meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'query list of RPA robots,' which is a specific verb and resource. However, it does not distinguish it from sibling tools like queryApplist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., queryApplist, queryRobotParam), nor any prerequisites or context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

queryJobA

该接口用于查询RPA应用JOB状态。

ParametersJSON Schema

Name	Required	Description	Default
`jobUuid`	Yes	RPA应用运行uuid，必填

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description must convey behavioral traits. It implies a read-only query operation but does not disclose error handling, rate limits, or what happens if jobUuid is invalid. For a simple query, the lack of detail is acceptable but not exceptional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence that conveys the essential information with no wasted words. It is appropriately front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one param, no output schema), the description states the basic purpose but does not mention expected output format, error codes, or how the status is returned. The context from sibling tools helps partially, but additional detail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (the single parameter jobUuid is described). The description adds no additional meaning beyond the schema's 'RPA应用运行uuid，必填' (required uuid). Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('查询' - query) and the resource ('RPA应用JOB状态' - RPA application JOB status). It is specific and easily distinguishes from siblings like startJob (start) and uploadFile (upload).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage context or alternatives are provided. The description only states the function, without guidance on when to use this tool versus queryApplist, queryClientList, or queryRobotParam. No when-not-to-use notes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

queryRobotParamC

该接口用于查询RPA机器人参数。

ParametersJSON Schema

Name	Required	Description	Default
`robotUuid`	No	RPA应用UUID
`accurateRobotName`	No	精确匹配的RPA应用名称

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must bear full weight. It only indicates a read operation ('query') but lacks details on side effects, authorization needs, or behavioral constraints. The agent is left uninformed about what the tool does beyond the basic query.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence without superfluous information. It is front-loaded with the purpose, but being in Chinese may slightly hinder quick parsing by an English-oriented agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no output schema, the description fails to explain what the query returns. For a data retrieval tool, this is a significant gap. The description is too minimal to provide complete context for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both parameters already described in the schema. The tool's description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queries RPA robot parameters, using a specific verb and resource. It distinguishes from sibling tools like queryApplist and queryClientList, which target different resources. However, the description is in Chinese, which may reduce clarity for an English-preferring AI agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, nor any indication of prerequisites or context. The description simply states its function without helping the agent decide between queryRobotParam and sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

startJobC

该接口用于启动RPA应用JOB。

ParametersJSON Schema

Name	Required	Description
`robotUuid`	Yes	RPA应用uuid，必填
`accountName`	No	RPA机器人账号名称,要求机器人的状态为idle,和robotClientGroupUuid互斥，二选一即可
`robotClientGroupUuid`	No	RPA机器人组uuid,和accountName互斥，二选一即可
`waitTimeoutSeconds`	No	等待超时时间（秒）
`runTimeout`	No	运行超时时间（秒）
`params`	No	运行参数

TDQS

C2.4/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and the description gives no behavioral details (e.g., side effects, required permissions, idempotency). The word 'start' implies mutation but no specifics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence in Chinese. It is not overly verbose, but it is too minimal to be considered well-structured or fully informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, one required, nested 'params' object, and no output schema, the description is far from complete. It does not explain return values, error conditions, or how parameters interact (e.g., mutual exclusivity of accountName and robotClientGroupUuid).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 6 parameters. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (start) and resource (RPA application JOB). However, it does not differentiate from sibling tools like queryJob or queryClientList, which are query operations, but the name itself implies uniqueness.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, prerequisites, or context. The description only states the basic purpose without usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

uploadFileC

该接口用于上传文件到RPA平台。

ParametersJSON Schema

Name	Required	Description	Default
`file`	No	文件内容
`fileName`	Yes	文件名，支持txt、csv、xlsx格式，长度不超过100字符

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description lacks behavioral details beyond basic upload. No info on side effects, file size limits, authentication, or what happens after upload. Ambiguity in 'file' parameter type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, but under-specified. Missing critical details for a file upload tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Incomplete for a file upload operation. No info on return values, error conditions, or integration with RPA platform.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions (100% coverage). Description adds no extra meaning beyond schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action (upload) and resource (file to RPA platform). Siblings are query tools, so differentiation is obvious but not explicitly stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. No exclusions or context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

6 tool updatesv0.0.2Apr 29, 2026
- AddedqueryClientList
- AddedqueryJob
- ChangedqueryRobotParam2 fields changed
  - addedInput schema / properties / accurateRobotName
```
Added value: +{
+  "description": "精确匹配的RPA应用名称",
+  "type": "string"
+}
```
  - changedInput schema / properties / robotUuid / description
```
Previous value: -"schema.local.queryRobotParam.robotUuid"New value: +"RPA应用UUID"
```
- RemovedrunApp
- AddedstartJob
- AddeduploadFile
3 tool updatesv1.0.0Apr 25, 2025
- First observedqueryApplist
- First observedqueryRobotParam
- First observedrunApp

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Disambiguation5/5

Each tool targets a distinct resource or action: app list, client list, job status, robot parameters, job start, and file upload. There is no clear overlap between tool purposes.

Naming Consistency5/5

All tool names follow a consistent verb+noun camelCase pattern (e.g., queryApplist, startJob, uploadFile). The verbs are descriptive and the pattern is uniform.

Tool Count5/5

Six tools is a reasonable scope for an RPA server, covering essential queries, job execution, and file upload without being too sparse or overwhelming.

Completeness3/5

The set covers querying and starting jobs but lacks CRUD operations for apps/clients and job stop functionality. Notable gaps exist for a full lifecycle.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

mcp COAuth
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
216
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237
Bitrix24 BOAuth
io.github.bitrix24
MCP server enabling AI agents to manage Bitrix24 features via standardized protocol
ERP Systems Project Management Communication
2
Artificial Wit AIOAuth
com.artificialwit
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
ERP Systems CRM Knowledge & Memory
2

Related MCP Servers

DolphinScheduler MCP Server
Agent Orchestration Developer Tools
ocean-zhc
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that allows AI agents to interact with Apache DolphinScheduler through a standardized protocol, enabling AI-driven workflow management.
Updated a year ago (2025-05-14 08:44 UTC)
28
Apache 2.0
Integrator MCP Server
App Automation Agent Orchestration
boostspace
A
license
Not graded
quality
C
maintenance
A Model Context Protocol server that allows AI assistants to invoke and interact with Integrator automation workflows through an API connection.
Updated a year ago (2025-04-18 11:47 UTC)
27
MIT
HAP MCP Server
Code Execution Developer Tools App Automation
mingdaocloud
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that provides seamless integration with Mingdao platform APIs, enabling AI applications to perform operations like worksheet management, record manipulation, and role management through natural language.
Updated a year ago (2025-07-03 12:49 UTC)
28
MIT
YingDao RPA MCP Server
App Automation Autonomous Agents
catinair
A
license
Not graded
quality
D
maintenance
Enables AI to execute RPA applications and workflows through the Model Context Protocol, supporting both local and cloud modes.
Updated a year ago (2025-04-25 03:43 UTC)
14
1
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ying-dao/yingdao_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server