# Browse connectors

> Source: https://elaichi.ai/docs/guides/connectors/browse-connectors/

Explore the products Elaichi can connect to, see which operations become MCP tools, and decide what to connect next.

**Where to find it:** **Connectors → All**, or open any connector from the catalog

A **connector** describes a product — Slack, Jira, Salesforce — and the tools it offers. It’s the blueprint. Connecting an account turns it into a working [connection](/guides/connections/connecting-an-account).

## Catalog tabs

| Tab | What it lists |
| --- | --- |
| **All** | Public catalog connectors plus your organization’s custom ones |
| **Custom** | Only connectors authored or forked for your organization |

On either tab you can:

- **Search** by name (`Search connectors…`)
- **Filter by category** (or leave **All categories**)
- **Load more** when the catalog continues

Each row shows the connector label, short description, category, and type badges such as **Public**, **Custom**, or **Restricted**. With `connector:create` (and a plan that includes custom connectors), eligible rows also offer **Fork**.

## Open a connector

Open a row to see detail:

- Identifier, category, and authentication summary
- Badges for **Custom** / **Public**, **Restricted**, **Beta**, and fork lineage when relevant
- Shared access for custom connectors (**Can view** / **Can edit**)

Actions on the detail page (when allowed): **Pull from upstream**, **Fork**, **Share**, **Edit**, **Delete**. There is no **Connect** button on the connector page — connecting always starts from **Connections → Add connection**, where you pick this product.

## Tools = documented methods

The **Tools** section lists MCP tools available through this connector.

For catalog (public) connectors, Elaichi loads the derived tool list. For custom connectors, a method becomes a tool when it has a **non-empty description** in the documentation editor — empty descriptions are not MCP tools.

| Column | Meaning |
| --- | --- |
| **Tool name** | Name agents see |
| **Resource** / **Method** | Underlying API operation |
| **Description** | What the tool does (agents choose tools by reading this) |
| **Schemas** | Query / Body when present (custom connectors) |

Filter tools by search, resource, or method. The badge shows how many tools match when filters are on.

If the connector is **Restricted** for you, the tools list is empty with a restricted message. Governance can hide or block connectors even when your role has `connector:read` — see [Set restrictions](/guides/governance/set-restrictions).

## From catalog to connection

1. Browse **Connectors → All** (or **Custom**).
2. Open a connector and review its **Tools**.
3. When you’re ready, go to **Connections → Add connection**, select the same product, choose ownership scope, and complete authorization.

**You'll know it worked when:** The connection appears under **Connections** as **Active**, and a connection toolbox shows under **Toolboxes → My toolboxes**.

## Good to know

- You need `connector:read` to browse the catalog (built-in **Viewer** and above).
- Restricted connectors may appear with a badge but can’t be used until restrictions allow them.
- Missing product? [Build a custom connector](/guides/connectors/build-a-custom-connector) or [fork](/guides/connectors/sharing-and-forking) a close match.

## Related

- [Connect an account](/guides/connections/connecting-an-account)
- [Build a custom connector](/guides/connectors/build-a-custom-connector)
- [Share, fork, and pull](/guides/connectors/sharing-and-forking)