Integration

Dify integration

Dify is a self-hosted platform for building LLM applications. This is the application side of its Service API: send a message to a chat, agent or chatflow app and read the answer, run a workflow app and read its outputs or stop a running task, browse conversations, their messages, their variables and the files attached to them, upload a file for an app to use, transcribe audio or speak text, record per-message feedback, curate the annotated question and answer pairs an app replies from, read the app's own parameters, metadata and web-app settings, and answer a human-input form a paused chatflow is waiting on. The host is part of the credential: use api.dify.ai for Dify Cloud, or your own hostname for a self-hosted install. Authentication is an application API key sent as a bearer token in the Authorization header, and each key belongs to ONE app, so the app being called is the one the key was issued for. Knowledge base endpoints take a different key and live in the separate Dify Knowledge API.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Dify.Built from the 35 Dify tools below, on the connection you add once.

What you can do with Dify

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Annotation, 4 operations

  • create_annotationCreate annotationPOSTCreate Annotation.
  • delete_annotationDelete annotationDELETEDelete Annotation.
  • list_annotationsList annotationsGETList Annotations.
  • update_annotationUpdate annotationPUTUpdate Annotation.

Run, 3 operations

  • get_workflow_runGet workflow runGETGet Workflow Run Detail.
  • run_workflowRun workflowPOSTRun Workflow.
  • run_workflow_by_idRun workflow by idPOSTRun Workflow by ID.

Stop, 3 operations

  • stop_chat_messageStop chat messagePOSTStop Chat Message Generation.
  • stop_completion_messageStop completion messagePOSTStop Completion Message Generation.
  • stop_workflow_taskStop workflow taskPOSTStop Workflow Task.

Conversation, 2 operations

  • delete_conversationDelete conversationDELETEDelete Conversation.
  • list_conversationsList conversationsGETList Conversations.

Feedback, 2 operations

  • list_app_feedbacksList app feedbacksGETList App Feedbacks.
  • submit_message_feedbackSubmit message feedbackPOSTSubmit Message Feedback.

Human input, 2 operations

  • get_human_input_formGet human input formGETGet Human Input Form.
  • submit_human_input_formSubmit human input formPOSTSubmit Human Input Form.

Variable, 2 operations

  • list_conversation_variablesList conversation variablesGETList Conversation Variables.
  • update_conversation_variableUpdate conversation variablePUTUpdate Conversation Variable.

Annotation reply, 1 operation

  • configure_annotation_replyConfigure annotation replyPOSTConfigure Annotation Reply.

Audio to text, 1 operation

  • transcribe_audioTranscribe audioPOSTConvert Audio to Text.

Chat message, 1 operation

  • send_chat_messageSend chat messagePOSTSend Chat Message.

Completion message, 1 operation

  • send_completion_messageSend completion messagePOSTSend Completion Message.

End user, 1 operation

  • get_end_userGet end userGETGet End User Info.

Info, 1 operation

  • get_app_infoGet app infoGETGet App Info.

Log, 1 operation

  • list_workflow_logsList workflow logsGETList Workflow Logs.

Message, 1 operation

  • list_conversation_messagesList conversation messagesGETList Conversation Messages.

Meta, 1 operation

  • get_app_metaGet app metaGETGet App Meta.

Name, 1 operation

  • rename_conversationRename conversationPOSTRename Conversation.

Parameter, 1 operation

  • get_app_parametersGet app parametersGETGet App Parameters.

Preview, 1 operation

  • download_fileDownload fileGETDownload File.

Site, 1 operation

  • get_web_app_settingsGet web app settingsGETGet App WebApp Settings.

Statu, 1 operation

  • get_annotation_reply_job_statusGet annotation reply job statusGETGet Annotation Reply Job Status.

Suggested, 1 operation

  • list_suggested_questionsList suggested questionsGETGet Next Suggested Questions.

Text to audio, 1 operation

  • text_to_speechText to speechPOSTConvert Text to Audio.

Upload, 1 operation

  • upload_fileUpload filePOSTUpload File.

Use Dify from Claude Code, Cursor or Codex

Connect Dify in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Dify operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Dify

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Dify once

    Add your Dify connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Dify integration FAQ

What can you do with the Dify integration?

LiveContext exposes 35 operations on Dify, covering annotation, run, stop and conversation.

Popular integrations

Browse the whole catalog