# WeCom MCP MCP > WeCom MCP connects your AI agent directly to China's enterprise communication system. It lets you manage complex corporate operations—from finding specific employees and listing organizational departments to tracking who checked in today and sending messages—all through natural conversation. ## Overview - **Category:** industry-titans - **Price:** Free - **Tags:** enterprise-messaging, team-collaboration, attendance-tracking, employee-management, internal-comms, api-integration ## Description This MCP lets your AI agent handle the heavy lifting of internal business management without you ever having to log into the WeCom Admin Backend. Instead of navigating deep menus, you just ask your client for what you need. You can immediately list departments or pull detailed employee profiles across the entire company structure. Need to know who belongs in a specific functional group? You can retrieve users based on tags. It even lets you check real-time attendance data—perfect for auditing staff activity quickly. If you're managing sensitive organizational records, your security is handled by Vinkius; credentials pass through a zero-trust proxy, meaning your keys are used only in transit and never stored on disk. Furthermore, you can manage internal apps or send messages directly to staff members. This means whether you’re coordinating cross-departmental communication or auditing who's working today, the AI acts as an instant operations assistant. ## Tools ### get_app_details Fetches specific configuration information about an internal application agent. ### get_attendance_data Retrieves employee check-in and clock-out records for a given period. ### get_department Gets detailed descriptive information about a single department unit. ### get_tag_users Finds all users who are assigned a specific organizational tag or group designation. ### get_user Retrieves full profile details for one specific user in the organization. ### list_departments Returns a complete list of every department currently set up in the company structure. ### list_menu Gets a breakdown of custom menus configured for an internal application agent. ### list_tags Lists all available organizational tags that can be applied to users or departments. ### list_users Provides a list of all employees who belong to a specified department. ### send_message Sends a direct text message to any user by name within the WeCom system. ## Prompt Examples **Prompt:** ``` List all departments in our organization. ``` **Response:** ``` I've retrieved the organizational structure for WeCom. You have 5 primary departments, including 'Engineering', 'Marketing', and 'Sales'. Which one would you like to see the users for? ``` **Prompt:** ``` Send a message to user 'Mario' saying 'The deployment is complete'. ``` **Response:** ``` Done! I've sent your message to Mario through the WeCom application. He has been notified that the deployment is complete. ``` **Prompt:** ``` Show me the attendance data for 'mario,renato' from today. ``` **Response:** ``` I've retrieved the check-in data for the specified users. Mario punched in at 9:00 AM, and Renato punched in at 8:45 AM. Both are currently marked as active in the system. ``` ## Capabilities ### Map out organizational structure List all company departments and fetch detailed information about specific users within those groups. ### Audit employee activity Retrieve real-time check-in data for employees to quickly track attendance records. ### Communicate with staff members Send direct text messages to any user within the organization through the chat interface. ### Identify specific employee groups Find and list users who belong to a particular organizational tag or group. ### Review internal applications Get metadata about custom company apps, including how their menus are configured. ## Use Cases ### The new hire needs onboarding resources. An Operations Coordinator asks the agent, 'Who are all the users in Marketing?' The agent uses `list_users` and then `get_tag_users` to find not just the people, but also those tagged as 'New Hire,' providing a complete list for the onboarding packet. ### Confirming team availability for a project. An HR Manager needs to know who is available next week. She asks for `get_attendance_data` for the Engineering department, quickly identifying any staff members who haven't logged in or have recorded leave. ### Addressing an urgent issue with a key employee. An IT Admin needs to talk to a specific user. They use `get_user` for the profile details, then immediately use `send_message` to alert that person about the system outage. ### Mapping out an entire division's hierarchy. A manager asks to see all reporting units. The agent uses `list_departments`, allowing the manager to then drill down department by department using `get_department` until they have a full organizational map. ## Benefits - Stop jumping between HRIS dashboards. Instead, ask your agent to run the `get_user` tool or `list_users`, and you get all the necessary employee data in one conversation. - Audit attendance records instantly. Use the `get_attendance_data` tool to pull check-in history without running complex reports in the Admin Backend. - Coordinate staff communication by using `send_message`. You can notify a group or an individual immediately, all from your client interface. - Understand your organization's structure faster. Use `list_departments` and then follow up with `get_department` to map out reporting lines in minutes. - Target users accurately. Instead of guessing names, use `list_tags` and `get_tag_users` to find everyone who fits a specific role or function. ## How It Works The bottom line is you get an AI layer that lets you manage complex corporate data using simple conversation. 1. Subscribe to this MCP and provide your required WeCom Corp ID, App Secret, and Agent ID. 2. Connect the MCP to your preferred client (Claude, Cursor, etc.). 3. Ask your agent a natural language question like, 'Show me the users in Engineering who are tagged as managers.' The agent then executes the necessary calls. ## Frequently Asked Questions **How do I check attendance data with get_attendance_data?** You tell your agent which users and what time frame you need. The agent runs the `get_attendance_data` tool and returns a list of who checked in and when. **Can I find all employees belonging to a specific group using get_tag_users?** Yes, that's exactly what it does. You give the tag name (e.g., 'Sales Lead'), and the agent uses `get_tag_users` to pull every employee assigned that label. **Is list_departments better than get_department?** They do different things. Use `list_departments` first if you want a master overview of all units in the company; use `get_department` when you know the name and need specific details about that single department. **How does send_message work with this MCP?** You simply tell your agent who to message. It uses the `send_message` tool, sending a direct text notification through the WeCom chat interface. **Before listing users, what information does the tool `get_app_details` provide about my application's current setup?** It returns the core configuration parameters for your WeCom app. This is useful for verifying that the API credentials and internal system settings are correct before running any data queries. **If I try to run `get_user` using a user ID or department name that doesn't exist, what kind of error should I expect?** The MCP will return a specific API error code detailing the invalid input. Your agent can then catch this error and prompt you to double-check the identifier instead of failing the entire workflow. **When dealing with very large departments, how does `list_users` handle pagination so I don't hit a limit?** The tool supports paginated retrieval. You pass the required page number and size parameters in subsequent calls to ensure you collect every single user record without running into rate limits. **How can I use `list_tags` to discover all available organizational tags before trying to filter users?** You simply call the tool with no parameters. It fetches a complete list of every tag currently used across your organization, letting you know exactly what criteria you can use later.