+
+## Integration with Claude Desktop
+
+To connect your Dify app to Claude Desktop, you'll need to add a Claude integration. Go to your Claude Profile \> Settings \> Integrations \> Add integration. Replace the Integration URL with your Dify app's Server URL.
+
+## Integration with Cursor
+
+For Cursor, create or edit the `.cursor/mcp.json` file in your project root:
+
+```json
+{
+ "mcpServers": {
+ "your-server-name": {
+ "url": "your-server-url"
+ }
+ }
+}
+```
+
+Simply replace the URL with your Dify app's MCP Server address. Cursor will automatically detect this configuration and make your Dify app available as a tool. You can add multiple Dify apps by including additional entries in the `mcpServers` object.
+
+## Practical Considerations
+
+- Descriptiveness
+
+ When designing descriptions for your tool and its input parameters, think about how an AI would interpret them. Clear, specific descriptions lead to better invocations. Instead of "input data," specify "JSON object containing user profile with required fields: name, email, preferences."
+- Latency
+
+ The MCP protocol handles the communication layer, but your Dify app's performance still matters. If your app typically takes 30 seconds to process, that latency will be felt in the client application. Consider adding progress indicators or breaking complex workflows into smaller, faster operations.
+
+{/*
+Contributing Section
+DO NOT edit this section!
+It will be automatically generated by the script.
+*/}
+
+---
+
+[Edit this page](https://github.com/langgenius/dify-docs/edit/main/en/guides/application-publishing/publish-mcp.mdx) | [Report an issue](https://github.com/langgenius/dify-docs/issues/new?title=Documentation%20Issue%3A%20sh-&body=%23%23%20Issue%20Description%0A%3C%21--%20Please%20briefly%20describe%20the%20issue%20you%20found%20--%3E%0A%0A%23%23%20Page%20Link%0Ahttps%3A%2F%2Fgithub.com%2Flanggenius%2Fdify-docs%2Fblob%2Fmain%2Fen/guides/application-publishing%2Fpublish-mcp.mdx%0A%0A%23%23%20Suggested%20Changes%0A%3C%21--%20If%20you%20have%20specific%20suggestions%20for%20changes%2C%20please%20describe%20them%20here%20--%3E%0A%0A%3C%21--%20Thank%20you%20for%20helping%20improve%20our%20documentation%21%20--%3E)
+
diff --git a/en/guides/extension/README.mdx b/en/guides/extension/README.mdx
deleted file mode 100644
index c2c8af52..00000000
--- a/en/guides/extension/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Extension
----
-
-
-In the process of creating AI applications, developers face constantly changing business needs and complex technical challenges. Effectively leveraging extension capabilities can not only enhance the flexibility and functionality of applications but also ensure the security and compliance of enterprise data. Dify offers the following two methods of extension:
-
-| Header | -Value | -Desc | -
|---|---|---|
| `Content-Type` | -application/json | -The request content is in JSON format. | -
| `Authorization` | -Bearer `{api_key}` | -The API Key is transmitted as a token. You need to parse the `api_key` and verify if it matches the provided API Key to ensure API security. | -
- ![]()
- ![]()
-
-
-Additionally, you can use the `npm run dev` command to deploy locally for testing.
-
-```bash
-npm install
-npm run dev
-```
-
-Related output:
-
-```bash
-$ npm run dev
-> dev
-> wrangler dev src/index.ts
-
- ⛅️ wrangler 3.99.0
--------------------
-
-Your worker has access to the following bindings:
-- Vars:
- - TOKEN: "ban****ool"
-⎔ Starting local server...
-[wrangler:inf] Ready on http://localhost:58445
-```
-
-After this, you can use tools like Postman to debug the local interface.
-
-## Other Logic TL;DR
-
-### About Bearer Auth
-
-```typescript
-import { bearerAuth } from "hono/bearer-auth";
-
-(c, next) => {
- const auth = bearerAuth({ token: c.env.TOKEN });
- return auth(c, next);
-},
-```
-
-Our Bearer authentication logic is as shown above. We use the `hono/bearer-auth` package for Bearer authentication. You can use `c.env.TOKEN` in `src/index.ts` to get the Token.
-
-### About Parameter Validation
-
-```typescript
-import { z } from "zod";
-import { zValidator } from "@hono/zod-validator";
-
-const schema = z.object({
- point: z.union([
- z.literal("ping"),
- z.literal("app.external_data_tool.query"),
- ]), // Restricts 'point' to two specific values
- params: z
- .object({
- app_id: z.string().optional(),
- tool_variable: z.string().optional(),
- inputs: z.record(z.any()).optional(),
- query: z.any().optional(), // string or null
- })
- .optional(),
-});
-```
-
-We use `zod` to define the types of parameters. You can use `zValidator` in `src/index.ts` for parameter validation. Get validated parameters through `const { point, params } = c.req.valid("json");`. Our point has only two values, so we use `z.union` for definition. `params` is an optional parameter, defined with `z.optional`. It includes a `inputs` parameter, a `Record
+
+Click **Add MCP Server (HTTP)** to connect a new external tool provider:
+
+**Server URL**: The HTTP endpoint of the MCP server (e.g., `https://api.notion.com/mcp` for a Notion integration).
+
+**Name & Icon**: Give it a name that describes what tools it provides. Dify auto-fetches icons when ever it can from the server domain, or you can choose your own.
+
+**Server Identifier**: A unique ID (lowercase, numbers, underscores, hyphens, max 24 characters) that Dify uses to track this server.
+
+
+
+**Re-authorize**: Click on the authorization status to renew permissions.
+
+**Edit Configuration**: Change server details.
+
+
+
+**Remove Server**: Disconnects the server. Applications using its tools will show errors until you reconnect or remove those tools.
+
+## Using MCP Tools in Your Applications
+
+Once a server is configured, its tools appear in the tool selection interface when building:
+
+### Agent Applications
+
+- MCP tools appear alongside built-in tools in the agent configuration
+- Tools are organized by server: "Notion MCP » Create Page", "Linear MCP » Create Issue"
+- "Add All" option lets you quickly enable all tools from a server
+
+### Workflow Applications
+
+- MCP tools appear as available node types when building workflows
+- Each tool node shows which server it comes from (helpful for troubleshooting)
+- Complex tool parameters get JSON input interfaces for structured data
+
+### Agent Nodes in Workflows
+
+- MCP tools can be selected within agent nodes, just like in standalone agents
+
+## Customizing MCP Tools for Your Use Case
+
+When you add an MCP tool to an agent node or agent, you can customize how it behaves:
+
+
+
+### Tool Description
+
+You can override the default description that comes from the MCP server. This is useful for making the description more specific to your use case.
+
+### Parameter Configuration (Reasoning Config)
+
+For each tool parameter, you can choose between:
+
+**Auto**: Let the AI model determine the parameter value based on context (default behavior)
+
+**Fixed Value**: Set a specific value (can be a static value or a variable) that will always be used, removing the parameter from AI inference
+
+This is powerful for:
+
+- Setting consistent configuration values (like `numResults: 10` for search tools)
+- Pre-filling parameters that shouldn't change (like specific API endpoints or format preferences)
+- Simplifying tool usage by reducing the number of parameters the AI needs to handle
+
+For example, with a web search tool, you might:
+
+- Keep `query` on "Auto" so the AI determines what to search for
+- Set `numResults` to a fixed value like "5" to limit response size
+- Set other parameters like search filters to fixed values for consistent behavior
+
+## Application Portability
+
+When you export Dify applications that use MCP tools:
+
+**DSL Export**: The exported DSL includes references to MCP servers by their IDs.
+
+**Environment Migration**: To use the application elsewhere, add the same MCP servers with identical IDs in the target environment.
+
+**Sharing Applications**: Document which MCP servers your application depends on, including URLs and required server IDs.
+
+## Troubleshooting Integration Issues
+
+**"Unconfigured Server"**: Authorization failed or no tools found. Check server URL and re-authorize.
+
+**Missing Tools in Applications**: Hit "Update Tools" - the external service may have changed its offerings.
+
+**Broken Applications After Server Changes**: If you modified server IDs or removed servers, applications will show tool errors. Re-add servers with original IDs to restore functionality.
+
+## Best Practices
+
+**Consistent Server IDs**: Use descriptive, permanent IDs like `github-mcp` or `salesforce-api`. Never change them once applications depend on them.
+
+**Environment Consistency**: Keep the same MCP server configurations across development, staging, and production environments.
+
+**Tool Customization**: Take advantage of parameter configuration to make tools behave consistently in your applications. Set fixed values for configuration parameters and let the AI handle dynamic inputs.
+
+**Tool Documentation**: Document which external tools your applications use, what customizations you've made, and what they do. This helps team members understand application dependencies.
+
+**Gradual Updates**: When external services update their MCP servers, test tool changes in development before updating production integrations.
+
+**Backup Plans**: Consider how your applications will behave if an external MCP server becomes unavailable.
+
+{/*
+Contributing Section
+DO NOT edit this section!
+It will be automatically generated by the script.
+*/}
+
+---
+
+[Edit this page](https://github.com/langgenius/dify-docs/edit/main/en/guides/tools/mcp.mdx) | [Report an issue](https://github.com/langgenius/dify-docs/issues/new?title=Documentation%20Issue%3A%20&body=%23%23%20Issue%20Description%0A%3C%21--%20Please%20briefly%20describe%20the%20issue%20you%20found%20--%3E%0A%0A%23%23%20Page%20Link%0Ahttps%3A%2F%2Fgithub.com%2Flanggenius%2Fdify-docs%2Fblob%2Fmain%2Fen/guides/tools%2Fmcp.mdx%0A%0A%23%23%20Suggested%20Changes%0A%3C%21--%20If%20you%20have%20specific%20suggestions%20for%20changes%2C%20please%20describe%20them%20here%20--%3E%0A%0A%3C%21--%20Thank%20you%20for%20helping%20improve%20our%20documentation%21%20--%3E)
+
diff --git a/en/guides/tools/types-of-tools.mdx b/en/guides/tools/types-of-tools.mdx
new file mode 100644
index 00000000..43643f2f
--- /dev/null
+++ b/en/guides/tools/types-of-tools.mdx
@@ -0,0 +1,33 @@
+---
+title: "Types of tools"
+description: "Tools are defined services that can be used within workflows and by agents alike."
+---
+
+