How to Use the Dify MCP in Cursor

Q: Can Cursor run Dify chats in agent mode?

Yes, Cursor's agent mode can invoke the chat tool to interact with your Dify applications. This allows the editor to run test queries and write code based on real-time responses.

Q: Does the Dify integration in Cursor support file uploads?

Yes, the uploadfile tool lets your agent send images or text files directly to your Dify workspace. This is useful for testing multi-modal pipelines without leaving your coding environment.

Q: Can I inspect Dify app configurations inside Cursor?

You can use the getparameters tool to fetch active variables. This helps you confirm that your Cursor agent is writing code against the correct backend configuration.

Q: How secure is my Dify API key inside Cursor?

Your API key and conversation logs from listmessages are stored locally in your Cursor configuration files. They are transmitted securely via HTTPS directly to your Dify instance, with zero external logging or retention on the Vinkius gateway.

Inject live Dify agent context and conversation history directly into your Cursor editor using this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Dify MCP to Cursor

Create your Vinkius account to connect Dify to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Dify with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate code using live Dify MCP Server data

Cursor's agent mode can execute the `chat` tool to test backend responses while you write your application code. This lets you build UI components against actual API outputs instead of relying on stale mock objects. The editor feeds the live payload directly into your active file. You get to see exactly how your backend responds, helping you catch structural mismatches immediately.

Pull history logs directly into your editor

Stop leaving your workspace to check why an agentic loop failed. Running `list_conversations` and `list_messages` lets your editor fetch the exact sequence of events from your Dify backend. You can ask Cursor to analyze these raw logs to pinpoint where a prompt went wrong. It speeds up debugging cycles since the error context is right next to your code.

Inspect active application parameters in Cursor

Use `get_parameters` to check which variables and features are currently configured on your Dify app. This keeps your local development environment aligned with your remote settings. Upload test assets directly to the server using the `upload_file` tool. After that, run `feedback` to log how well your code handled the run.

Setup guide

Set up Dify MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Dify MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Dify transactions." If the MCP tools are loaded correctly, Cursor will call the Dify tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "dify-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Dify. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Dify now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Dify MCP in Cursor

Create a .cursor/mcp.json file in your project root. Define the Dify server under your mcpServers configuration block to activate it inside your editor.

Yes, Cursor's agent mode can invoke the `chat` tool to interact with your Dify applications. This allows the editor to run test queries and write code based on real-time responses.

Yes, the `upload_file` tool lets your agent send images or text files directly to your Dify workspace. This is useful for testing multi-modal pipelines without leaving your coding environment.

You can use the `get_parameters` tool to fetch active variables. This helps you confirm that your Cursor agent is writing code against the correct backend configuration.

Your API key and conversation logs from `list_messages` are stored locally in your Cursor configuration files. They are transmitted securely via HTTPS directly to your Dify instance, with zero external logging or retention on the Vinkius gateway.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript