Feishu MCP integration for AI agents.
Connect AI agents to Feishu through 396 structured actions, including batch get messages, add approval cc, batch delete base records, and apply drive permiss…
- ACTION CONTRACTS
- 396
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Feishu integration exposes
The Feishu Agent App exposes 396 provider-backed actions for communication, productivity, and storage work. Its current contract lets an authorized agent fetch up to 50 feishu messages by message id in one request, add cc recipients to an active approval instance, and delete up to 200 records in one feishu base request. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Feishu account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Feishu capabilities.
Showing 12 of 396 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
batch_get_messagesREADFetch up to 50 Feishu messages by message ID in one request.
INPUTS: messageIds
add_approval_ccWRITEAdd CC recipients to an active approval instance.
INPUTS: instanceCode / userIds / comment / userIdType
batch_delete_base_recordsHIGH IMPACTDelete up to 200 records in one Feishu Base request.
INPUTS: appToken / tableId / recordIds
apply_drive_permissionREVIEWApply to a Feishu document owner for view or edit permission on behalf of the current user.
INPUTS: token / type / permission / remark
add_chat_membersWRITEAdd users or bots to a Feishu chat.
INPUTS: chatId / memberIdType / memberIds
add_drive_permissionWRITEGrant a collaborator permission on a Feishu Drive resource.
INPUTS: token / resourceType / memberId / memberType / permission
add_sign_approval_taskWRITEAdd users before, after, or alongside the current approval task.
INPUTS: instanceCode / taskId / userIds / addSignType / approvalMethod
add_task_commentWRITEAdd a text comment to a Feishu task.
INPUTS: taskGuid / content / userIdType
add_task_to_tasklistWRITEAdd a Feishu task to a tasklist.
INPUTS: taskGuid / tasklistGuid / userIdType
add_wiki_memberWRITEAdd a member to a Feishu Wiki space.
INPUTS: spaceId / memberId / memberType / memberRole / notify
apply_minutes_permissionREVIEWApply for view or edit permission on one Feishu Minutes record.
INPUTS: minuteToken / permission
approve_approval_taskWRITEApprove a pending approval task with optional form controls.
INPUTS: instanceCode / taskId / form / comment
INPUT CONTRACTS
Know what the action needs before it runs.
batch_get_messages
messageIdsREQUIRED- The Feishu message IDs.
add_approval_cc
instanceCodeREQUIRED- The approval instance code.
userIdsREQUIRED- The users to add as CC recipients.
commentOPTIONAL- An optional approval comment.
userIdTypeOPTIONAL- The type used by all user IDs in this request.
batch_delete_base_records
appTokenREQUIRED- The Base app token from a Feishu Base URL.
tableIdREQUIRED- The Base table ID, usually starting with `tbl`.
recordIdsREQUIRED- The record IDs to delete.
apply_drive_permission
tokenREQUIRED- A bare Drive token or a Feishu document URL from which the token and type can be inferred.
typeOPTIONAL- The target type used by Drive permission and secure-label APIs.
permissionREQUIRED- The permission to request.
remarkOPTIONAL- An optional note shown to the document owner.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Batch Get Messages
Fetch up to 50 Feishu messages by message ID in one request. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
batch_get_messagesControl Add Approval Cc
Add CC recipients to an active approval instance. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_approval_ccVerify with Add Approval Cc
Add CC recipients to an active approval instance. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_approval_ccSAFETY BOUNDARY
Operate Feishu with explicit limits
- Authorize Feishu with OAuth 2.0 and grant only the provider access required by the selected actions.
- 172 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `batch_delete_base_records`, `cancel_approval_instance`, and `cancel_message_flag` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `approval:instance:write`, `im:chat.members:write_only`, `docs:permission.member:create`, and `approval:task:write`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Feishu task completed successfully.
CONNECTION MODEL
OAuth 2.0
Feishu uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 160
- WRITE SIGNALS
- 127
- HIGH IMPACT
- 45
- REVIEW SIGNALS
- 64
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Feishu.