Connectors Overview

The external service connections that extend what the AI can do

A connector is a connection to an external service that extends what the AI can do. Through MCP (Model Context Protocol), an open standard, the AI can call external tools. Manage connectors on the “Connectors” page in the “Configure” section of the sidebar.

Types of connections

Personal connectors

Connect your own accounts — Gmail, Slack, Google Calendar, Notion, and more — and let the AI act on your behalf

jinba-flow integration

Call jinba-flow workflows as tools for the AI, or turn on AI operation to let it operate Jinba on your behalf. Includes the dedicated “Jinba Flow” page and the “Flow” run console

Custom MCP

Register any MCP server, such as an internal system, for the AI to use

Related pages at a glance

Page	Location	Purpose
Connectors	Sidebar > Configure	Managing external tool integrations: personal connectors, custom MCP, and more
Jinba Flow	Linked from the Flow console	One-click workspace connect, the AI operation toggle, and the list of connected workspaces and their published flows
Flow	Sidebar	A run console for executing published flows from a form, on the spot

Where connections live

Location	Description
Workspace shared	Managed on the Connectors page. Multiple agents can attach and use them
Agent-specific	Registered from the agent detail page’s Connectors tab. Used by that agent only; not shown in the catalog
Personal	Personal connectors (Gmail, etc.) are used only in chats by you, the person who connected them

Using connectors from chat

• The AI automatically selects and runs the tools of connectors attached to the agent, based on the conversation
• You can also name a specific tool or flow with # in the composer
• When the AI spots a connection that would be useful given the conversation, it may show a “Connector addition proposed” card (additions take effect from your next chat)

Managing connections

• Re-sync — refetch the tool list from the connection (run this after publishing or updating flows on the jinba-flow side, for example)
• Disconnect — remove the connection. The associated MCP server and its tools are deleted too
• No access — connections that have lost access on the jinba-flow side show “No access.” Ask the Flow workspace owner to invite you as a member or add an external access rule