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.

Yida MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Yida
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Yida through Vinkius, pass the Edge URL in the `mcps` parameter and every Yida tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Yida Specialist",
    goal="Help users interact with Yida effectively",
    backstory=(
        "You are an expert at leveraging Yida tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Yida "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Yida MCP Server

Empower your AI agent to orchestrate your enterprise operations with Yida, the premier low-code platform under the DingTalk ecosystem. By connecting Yida to your agent, you transform complex form management and data orchestration into a natural conversation. Your agent can instantly list your forms, retrieve field schemas, manage data records (create, update, delete), and even monitor workflow approval timelines without you needing to navigate the complex DingTalk interface. Whether you are managing administrative approvals, inventory tracking, or customized business processes, your agent acts as a real-time operations assistant, keeping your data accurate and your workflows moving.

When paired with CrewAI, Yida becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Yida tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Form Orchestration — List all accessible forms and retrieve detailed field schemas for your Yida applications.
Data Operations — Manage form instances (records) with full support for creating, listing, and granular updates.
Workflow Monitoring — Check the current status and approval timeline for any workflow instance.
Schema Auditing — Retrieve internal form schemas to understand data structures and field IDs.
User Coordination — Access application user lists to manage assignments and participation effectively.

The Yida MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Yida to CrewAI via MCP

Follow these steps to integrate the Yida MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Yida

Why Use CrewAI with the Yida MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Yida through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Yida + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Yida MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Yida for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Yida, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Yida tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Yida against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Yida MCP Tools for CrewAI (10)

These 10 tools become available when you connect Yida to CrewAI via MCP:

create_record

Create a new form record

delete_record

Delete a form record

get_form_schema

Get form field schema

get_instance_timeline

Get workflow instance timeline

get_record_details

Get record detailed data

list_data_ids

List data instance IDs

list_forms

List all forms in the Yida application

list_users

List application users

list_workflows

List application workflows

update_record

Update an existing record

Example Prompts for Yida in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Yida immediately.

"List all forms in my Yida application."

"Show me the last 5 instance IDs from the 'Purchase Request' form."

"What is the approval timeline for purchase request 'REQ-2026-042'?"

Troubleshooting Yida MCP Server with CrewAI

Common issues when connecting Yida to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Yida + CrewAI FAQ

Common questions about integrating Yida MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.