# Yida MCP > Yida MCP connects your AI agent to an enterprise low-code platform for managing business processes. Use it to list forms, retrieve field schemas, and manage data records—all within complex approval workflows. Your agent handles everything from inventory tracking to onboarding paperwork by talking directly to the underlying system. ## Overview - **Category:** industry-titans - **Price:** Free - **Tags:** low-code, workflow-automation, form-builder, business-process-management, data-orchestration, enterprise-apps ## Description Managing internal company operations often involves clicking through dozens of dashboards just to get one piece of status information. This MCP lets your AI agent do that work for you, turning complicated form and data management into a natural conversation. You can ask your agent to find all current forms used across the organization, then retrieve the specific field structure needed for a new project. Need to update an employee record? Your agent handles the full process: it pulls the necessary data, makes the changes, and even tracks the approval timeline for that instance. When dealing with critical business approvals, you need absolute trust; Vinkius ensures every tool call generates a cryptographically signed audit trail, giving you proof of exactly what happened and when. This means whether you're tracking inventory or managing HR requests, your data remains accurate and auditable. It’s an operations assistant that keeps all your core business processes moving without needing to log into the complex internal portal. ## Tools ### create_record This tool creates a brand new submission record for any specified form. ### delete_record The agent permanently removes an existing form submission record. ### get_form_schema This tool reads the structure of a form, showing exactly which fields and data types it contains. ### get_instance_timeline It pulls a full history of an instance, detailing every step taken in the workflow approval process. ### get_record_details The agent retrieves all the stored data from a specific form submission record. ### list_data_ids This tool provides a list of unique identifiers for existing data instances. ### list_forms It retrieves an inventory of all forms available in the Yida application. ### list_users The agent pulls a list of every user account configured within the platform. ### list_workflows This tool lists all defined approval and business workflows available for use. ### update_record The agent modifies specific data points on an already existing form submission record. ## Prompt Examples **Prompt:** ``` List all forms in my Yida application. ``` **Response:** ``` I've retrieved the forms for your Yida application. You have 4 forms: 'Purchase Request', 'Inventory Audit', 'Employee Onboarding', and 'Travel Expense'. Which one would you like to view data for? ``` **Prompt:** ``` Show me the last 5 instance IDs from the 'Purchase Request' form. ``` **Response:** ``` I've listed the last 5 instance IDs for 'Purchase Request'. They include REQ-2026-001 through REQ-2026-005. Would you like to see the detailed field data for any of these requests? ``` **Prompt:** ``` What is the approval timeline for purchase request 'REQ-2026-042'? ``` **Response:** ``` The purchase request 'REQ-2026-042' is currently pending with the Finance Director. It was approved by the Department Head at 10 AM today. Should I send a follow-up notification? ``` ## Capabilities ### List available forms The agent retrieves a list of every accessible form within the Yida application. ### Get data structure details You can ask for the specific field schemas to understand what data points a particular form collects. ### Create or modify records The agent handles creating new form submissions or updating existing data instances based on your instructions. ### Check workflow progress You get the current status and full approval timeline for any given workflow instance ID. ### Retrieve specific record content The agent pulls detailed data from a specified form instance, giving you all the filled-in details in one go. ## Use Cases ### Handling delayed expense reports The department manager asks the agent: 'What’s up with PRX-452?' The agent uses `get_record_details` and then `get_instance_timeline`, reporting that it's stuck waiting for Finance, saving the manager from calling three people. ### Onboarding new employees The HR lead needs to submit a form. They ask the agent to 'create an onboarding record using these details.' The agent uses `create_record`, ensuring all required fields are populated correctly before submission. ### Auditing data changes An IT admin suspects data was altered improperly and asks the agent for the full history of a specific record ID. The agent runs `get_instance_timeline`, providing an immutable log of all state changes. ### Updating department contact info When a key person changes their phone number, instead of having them manually edit the form, the team lead asks the agent to 'update record XYZ with new contact details,' using `update_record` for immediate change. ## Benefits - Stop digging through dashboards. Instead of manually checking a status page, your agent uses `get_instance_timeline` to tell you exactly where an approval stands and who's holding it up. - Need to know what fields are available? Use `list_forms` first to get the names, then use `get_form_schema` to see the exact data structure before writing a single line of code. - Data changes don’t have to be manual. You can tell your agent to update key details using `update_record`, automating the process instead of requiring someone to open and edit the form themselves. - Don't lose track of who has access to what. The agent uses `list_users` and `list_workflows` together so you know which people are assigned to which automated processes. - When dealing with sensitive submissions, every change matters. Because Vinkius manages all tool calls through a zero-trust proxy, your credentials never sit on disk; they only pass in transit. ## How It Works The bottom line is that you treat complex business processes—like tracking an approval or updating a record—as simple conversations with your agent. 1. Subscribe to this MCP and provide your specific DingTalk credentials (App Key, App Secret, Yida App Code). 2. Connect your preferred AI client. The agent now has access to the platform's APIs. 3. Ask a natural language question like, 'What is the status of purchase request REQ-2026-042?' and get the real-time answer. ## Frequently Asked Questions **How do I list all forms using the Yida MCP?** You use `list_forms`. This tool reads and returns every accessible form name, giving you an inventory of what data sources your agent can interact with. **Can I check if a record ID is valid before trying to update it? (Using Yida MCP)** Yes. Before running `update_record`, you should use `list_data_ids` or `get_record_details`. This confirms the ID exists and that data can actually be retrieved, preventing errors. **Is tracking the workflow timeline secure with Yida MCP?** The platform handles this securely. Every tool call, including checking the status via `get_instance_timeline`, produces a cryptographically signed audit trail, so you always know who accessed what and when. **If I need to delete data, is it safe using the Yida MCP?** The agent uses the dedicated `delete_record` tool. However, because this action is irreversible, we recommend running `get_form_schema` first so you know exactly what type of record you are deleting. **How do I use the `get_form_schema` tool to check a form's available fields?** It retrieves the detailed field schema for any specified Yida application. This lets you see every field name, required status, and data type without having to manually inspect the complex DingTalk interface. **What information does `list_users` provide about application users?** This tool provides a list of all active users assigned to your Yida application. You can use this data for auditing purposes or coordinating assignments before you run other operations like updating records. **How can I use the `list_data_ids` tool to get a bulk list of record identifiers?** The tool generates a comprehensive list of existing instance IDs for quick reference. This is essential if you need to process or audit dozens of records at once, rather than querying them one by one. **What does `list_workflows` do if I need to know about available business processes?** It lists all the defined workflows within your Yida application. This lets you discover which approval paths or automated processes are ready for your agent to monitor and interact with. **How do I find my DingTalk App Key and Secret?** Log in to the DingTalk Developer Backend, create or select an 'Internal Enterprise Application', and you will find the App Key and App Secret under the 'Credentials' section. **Where can I find the Yida 'App Code'?** Open your Yida application, go to [Settings] → [Deployment and O&M], and you will find the 'App Code' (Application Code) there. It is required for all Yida API calls. **Can I see the approval history of a record?** Yes. Use the `get_instance_timeline` tool with the form instance ID. It will return the full approval history, including who approved it and at what time.