SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Dify MCP with Atomic Agent

Connect Atomic Agent to Dify MCP. Run dify workflow to process ticket, fetch dify workflow run history, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Dify logoDify
Api Key

Dify is a platform for running and managing published workflow apps via a Service API. Use it to execute workflows and inspect configuration and run history quickly.

4 Tools

Introduction

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including Dify.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Dify account. See the Atomic Agent documentation for installation instructions.

Also integrate Dify with

ChatGPTClaude CoworkHermes

How Atomic Agent connects to Dify

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect Dify to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in Dify. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your Dify account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

What is the Dify MCP server, and what's possible with it?

The Dify MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dify account. It provides structured and secure access to your published Dify Workflow app, so your agent can inspect its configuration, run workflows, review run history, and check execution results on your behalf.

  • Published workflow execution: Have your agent run the latest published version of your Dify workflow with the inputs you provide and return its results.
  • Workflow configuration review: Let the agent inspect your workflow app's identity, input form, upload limits, tool icons, and hosted site settings.
  • Run history monitoring: Direct your agent to list recent workflow runs and filter them to find the executions you want to review.
  • Execution result inspection: Instruct your agent to check a workflow run's status, inputs, outputs, errors, and performance metrics.

Use Dify from Atomic Agent

With your account connected, ask Atomic Agent to work with Dify in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

TOOLS

Supported Tools

Every Dify action and event your agent gets out of the box.

Get Workflow App Configuration

Return the connected Workflow app's identity, declared input form and upload limits, tool icons, and hosted-site settings.

Get Workflow Run

Return one workflow run's status, inputs, arbitrary outputs, error, and execution metrics by run ID.

List Workflow Runs

Return one page of run summaries for the connected Workflow app, with filters and a continuation cursor for older or additional runs.

Run Workflow

Run the connected app's latest published workflow in blocking mode and return its app-defined outputs.

FRAMEWORKS

How to build Dify MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Dify MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Dify MCP with Claude Cowork

Hermes logo

Hermes

Use Dify MCP with Hermes

FAQ

Frequently asked questions

With a standalone Dify MCP server, the agents and LLMs can only access a fixed set of Dify tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dify and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Atomic Agent fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Dify tools.

Yes, absolutely. You can configure which Dify scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Dify data and credentials are handled as safely as possible.

Start with Dify.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Dify tool your agent needs.Free to start.

Start building