> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinba.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

<img src="https://mintcdn.com/jinba/B0KuFPdq9oF6s05P/images/jinba_app_neo/en/connectors-library.png?fit=max&auto=format&n=B0KuFPdq9oF6s05P&q=85&s=8ae9c22d90d4bba0635d9819e3abb379" alt="Connectors page" style={{ width: '100%', borderRadius: '8px', margin: '32px 0' }} width="1500" height="950" data-path="images/jinba_app_neo/en/connectors-library.png" />

The page opens as a card grid — switch between "**Card view**" and "**List view**" with the toggle in the header. Click a card to open its details.

## Types of connections

<CardGroup cols={2}>
  <Card title="Personal connectors" icon="user-lock" href="/en/pages/jinba_app_neo/connectors/personal-connectors">
    Connect your own accounts — Gmail, Slack, Google Calendar, Notion, and more — and let the AI act on your behalf
  </Card>

  <Card title="jinba-flow integration" icon="diagram-project" href="/en/pages/jinba_app_neo/connectors/jinba-flow">
    Call jinba-flow workflows as tools for the AI, or turn on AI operation to let it operate Jinba on your behalf. Connecting, listing and running all happen on the "Flow" page
  </Card>

  <Card title="Custom MCP" icon="server" href="/en/pages/jinba_app_neo/connectors/custom-mcp">
    Register any MCP server, such as an internal system, for the AI to use
  </Card>
</CardGroup>

## Related pages at a glance

| Page           | Location            | Purpose                                                                                                                                                                                        |
| -------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Connectors** | Sidebar > Configure | Managing external tool integrations: personal connectors, custom MCP, and more                                                                                                                 |
| **Flow**       | Sidebar             | Everything jinba-flow: one-click workspace connect, the AI operation toggle, the list of connected workspaces and their published flows, and a console for running one 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's configuration panel. 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                                                                                                                                              |
| **Organization-managed** | MCP servers your organization's administrator registered. They appear on the Connectors page in a read-only "**Organization connectors**" group, marked "**Org-managed**" — see [Custom MCP](/en/pages/jinba_app_neo/connectors/custom-mcp) |

## 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. Approving saves the addition right away, and in most cases the card then reads "**Ready to use in this chat**" — otherwise it takes effect from your next chat
* When a service you need is not connected yet — or an existing connection has stopped working — the AI can show a connect (or reconnect) card right in the chat. Complete the authorization there and the conversation picks up where it left off. Both [personal connectors](/en/pages/jinba_app_neo/connectors/personal-connectors) and [jinba-flow workspaces](/en/pages/jinba_app_neo/connectors/jinba-flow) support this

## Managing connections

* **Refresh** — refetch the tool list from a jinba-flow connection: in the workspace's index on the Flow page, or beside the connection in an agent's Flow connectors section. jinba-flow connections also re-sync automatically when you open the Flow page or the composer's connector picker, so the manual action is mostly a fallback
* **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
* **Blocked by your organization** — depending on your organization's policy, some connectors show "**Your organization has blocked this connector.**" A blocked connector cannot be connected, and even one that was connected earlier is not used by the AI while it stays blocked. Contact your organization's administrator