Skip to main content
Glama
Sign In
dify-canvas-mcp

dify-canvas-mcp

by elegant01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dify_setup

Add or update a Dify instance using an alias and site URL, with credentials taken from your local Chrome login instead of account passwords.

Instructions

添加或修改一个 Dify 实例。只需要 alias 和站点地址（例如 https://dify.example.com）；凭据是本机 Chrome 的登录态，不需要账号密码。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "alias": "<alias>",
      "baseUrl": "<baseUrl>"
    },
    "name": "dify_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYes实例别名，例如 prod。
baseUrlYesDify 站点地址，例如 http://dify.example.com。
poolPortNo可选。chrome-pool 端口，默认 3333；0 表示禁用并直连 Chrome。
debugPortNo可选。直连 Chrome 的调试端口；省略时自动探测。
descriptionNo可选备注。
makeDefaultNo设为默认实例。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose the non-obvious auth model: credentials come from the local Chrome login state, no username/password. It does not say whether an existing alias is overwritten, whether a connection is validated on save, or what happens to the Chrome pool when the instance is re-registered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses, front-loaded with the action and followed by the minimum required inputs, so every sentence earns its place. The inline URL example slightly duplicates the schema's own example, which is the only redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation/configuration tool with no annotations and no output schema, the description covers the essential surprises: only alias and baseUrl are required, and authentication is inherited from the local Chrome session. Remaining gaps (overwrite semantics on re-registration, post-save validation) are moderate rather than blocking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters including poolPort, debugPort, and makeDefault are already documented in the schema. The description adds only the required-parameter reminder and the credentials origin, not new semantics for any individual parameter; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb + resource pair ('添加或修改一个 Dify 实例' / add or modify a Dify instance), which is clearly distinct from read-only siblings like dify_instances and dify_apps. It does not name a sibling explicitly, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when the tool applies by stating the minimal inputs ('只需要 alias 和站点地址'), which tells the agent this is the registration/update step. There is no explicit when-not-to-use guidance and no pointer to dify_instances or dify_browser_launch for related setup or verification steps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools