MCP Tools
MCP is an open protocol that standardizes how applications provide context to large language models (LLMs). Think of MCP as the USB-C port for AI applications. Just as USB-C provides a standardized way to connect various peripherals and accessories to your devices, MCP offers a standardized way for AI models to connect to different data sources and tools.
Why Choose MCP?โ
MCP helps you build agents and complex workflows on top of large language models (LLMs). LLMs often need to integrate with data and tools, and MCP provides:
- A growing list of pre-built integrations that your LLM can directly access
- Flexibility to switch between LLM providers and vendors
- Best practices for securing data within your infrastructure
How to Create?โ
In the Digital Expert workspace, select the MCP tool type and click the card to create a new MCP toolset.
As shown in the image below, fill in the required fields such as the name, enter the MCP service configuration into fields like commands and parameters, and click "Connect" to attempt loading the tool list with the current configuration.

In open-source code versions, MCP tools run using "commands" will trigger a security prompt: "Commands" are executed directly on the backend server, which may pose security risks. Upgrading to the Pro version ensures that "command" tools are securely run in a sandbox container.
After loading the MCP toolsetโs tool list, users can enable or disable individual tools. You can also set "Default Disabled Tools," meaning tools not explicitly enabled will be turned off by default.
Examplesโ
Sequential Thinking: An MCP server implementation that provides tools for dynamic and reflective problem-solving through a structured thinking process.
{
"mcpServers": {
"sequential-thinking": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
}
}Playwright: A Model Context Protocol (MCP) server using Playwright to provide browser automation capabilities. This server enables large language models (LLMs) to interact with web pages through structured accessibility snapshots, without requiring screenshots or visually optimized models.
{
"mcpServers": {
"playwright": {
"transport": "stdio",
"command": "npx",
"args": [
"-y",
"@playwright/mcp@latest",
"--headless"
]
}
}
}Blender: BlenderMCP connects Blender to Claude AI via the Model Context Protocol (MCP), allowing Claude to directly interact with and control Blender. This integration supports prompt-based 3D modeling, scene creation, and manipulation.
{
"mcpServers": {
"blender": {
"command": "uvx",
"args": [
"blender-mcp"
]
}
}
}More at MCP.so
Transport Protocolsโ
MCP (Model Context Protocol) has two primary communication modes: Standard Input/Output (stdio) command mode and HTTP Server-Sent Events (SSE) mode.
Standard Input/Output Modeโ
This is the standard input/output communication mode, running the server as a local process and interacting via standard input (stdin) and standard output (stdout). Itโs suitable for development and testing scenarios, requiring no network connection.
HTTP SSE Modeโ
This is the remote communication mode, where the client connects to the serverโs HTTP endpoint, receiving real-time events via SSE and sending commands via HTTP POST. Itโs ideal for applications requiring remote access and real-time data streaming.
Mode Comparisonโ
The table below summarizes the differences between the two modes to help understand their use cases and characteristics:
Feature | Standard Input/Output Mode | HTTP SSE Mode |
---|---|---|
Communication | Local stdin/stdout | HTTP POST (commands) + SSE (events) |
Use Case | Local development, testing | Remote access, real-time data streaming |
Network Needs | Local server network | Connects to other servers via network |
Real-Time | Synchronous, suitable for blocking ops | Asynchronous, supports real-time event push |
Security | Local ops, lower network risks | Requires network authentication/authorization |
Example Tools | Quarkus MCP stdio extension | Supergateway, Cloudflare remote deployment |
Code MCP Toolsโ
Code MCP tools offer a more flexible approach, allowing users to write backend logic code for MCP tools directly online and run it using the MCP protocol. This enables developers to call external APIs, perform logic processing, and more without deploying servers or building full projects, greatly enhancing the scalability and efficiency of MCP tools.
When creating an MCP tool, select the โCodeโ type to access the online editor page. The editor supports Python syntax (with JavaScript support planned) and provides basic templates for quick starts.

Development Experienceโ
Code MCP tools are essentially custom-implemented MCP server code, hosted and run by the system in a sandbox container, automatically exposing MCP-compliant interfaces. You can focus on writing business logic, including but not limited to:
- Calling third-party APIs, such as weather queries, stock market data, or translation services
- Interfacing with internal enterprise systems like ERP or CRM
- Implementing data processing logic, such as format conversion, filtering, or aggregation
- Converting structured inputs to natural language outputs, or vice versa
Debugging and Testingโ
- The editor includes a testing panel to simulate parameter calls, enabling real-time debugging of tool logic.
- All runtime environments are isolated sandbox containers, ensuring secure execution.
Multi-Tool Supportโ
A single code MCP tool can register multiple MCP tools using multiple @mcp.tool()
decorators. The system automatically recognizes and generates a tool list for model invocation.
MCP Tools Marketplaceโ
The MCP Tools Marketplace offers a rich set of tool integration modules, enabling users to quickly extend model perception and action capabilities without writing complex code. With one-click installation, you can add various MCP tools to your agentโs toolset, instantly enabling external data retrieval, third-party service calls, and data processing.

Diverse Tool Categories for Various Scenariosโ
The MCP Tools Marketplace supports multiple tool types, covering the following typical use cases:
- Agent Support: Tools like
Sequential Thinking
provide structured reasoning chains, supporting multi-step reasoning and task planning for agents. - System Tools: Tools like
Memory Server
offer runtime data caching and context state management, supporting continuous conversation memory for AI systems. - Browser Operations: Tools like
Playwright MCP
support browser automation for tasks like web scraping and login operations. - Map Services: Tools like
Baidu Map
andAMap
are MCP-compatible, supporting coordinate resolution and route planning. - Utility Tools: Tools like
Time MCP Server
support timezone conversion,Fetch
enables web content retrieval and conversion, andFirecrawl
supports advanced crawling. - Document Processing: Tools like
Perplexity
enable document Q&A and search engine access, whileGitHub MCP
supports repository searches and code reading. - Dify Tool Integration: Includes
Dify Knowledgebase
,Dify Workflow
,Dify Chatflow
, and more, offering seamless integration with the Dify platform.
Diverse Tool Formats: SSE, Stdio, and Codeโ
Each MCP tool supports the following formats:
- SSE: Configures existing SSE interface MCP tool services.
- Studio Tools (STUDIO): Uploaded, hosted, and registered by developers in the official MCP service, ready for direct user installation.
- Code Tools (CODE): Custom-created by developers within the platform using online code, offering greater flexibility for enterprise-specific tools.
Quick Activation and Searchโ
- Filter tools quickly by category (e.g., Agent, Workflow, Utils, Analysis).
- Support for keyword search and tag navigation to locate tools efficiently.
- Tool pages display details like call frequency, developer, supported tags, and parameters for easy selection.
The MCP Tools Marketplace ensures that AI agent capabilities are no longer limited to the model itself but can connect to business systems, data services, and the real world through a rich tool ecosystem. In the future, it will support more community and enterprise developers to join the ecosystem, further enriching the toolset and enhancing the practical effectiveness of AI agents.