Skip to content

Connector ​

A connector is an outside service, reached over MCP, that the tasks linked to it can use.

Syntax ​

text
connector id["Label"]@{ protocol: "mcp", url: "…" }

connector id["Label"]
id@{ protocol: "mcp", url: "…" }

The connector keyword is what makes it a connector. The label is optional.

Settings ​

SettingRequiredValueExample
protocolyes"mcp"protocol: "mcp"
urlyesa full addressurl: "https://example.com/mcp"

Where it can go ​

A connector sits at the top level of the workflow and holds nothing. Tasks in any flow can link to it.

ArrowIn fromOut to
Arrow (-->)——
Dotted link (-.-)tasktask

Rules ​

Example ​

Code:
mermaid
agentflow TB
  connector github["GitHub"]
  github@{ protocol: "mcp", url: "https://api.githubcopilot.com/mcp/" }

  flow triage["Issue triage"]
    read["Read issues"]@{ instruction: "List the open issues labelled bug." }
    label["Label issues"]@{ instruction: "Add a priority label to each bug." }
    read --> label
    read -.- github
    github -.- label
  end
Ctrl + Enter|

Common mistake ​

A connector written inside a flow.

Code:
mermaid
agentflow TB
  flow triage["Issue triage"]
    connector github["GitHub"]@{ protocol: "mcp", url: "https://api.githubcopilot.com/mcp/" }
    read["Read issues"]@{ instruction: "List the open issues labelled bug." }
    read -.- github
  end
Ctrl + Enter|

Connector "github" is inside flow "triage", but connectors belong at the top level of the workflow. Move it out of the flow.

Opens in mermaid.ai