Skip to content

Share, fork, and pull

Share a custom connector with teammates, fork a connector to edit your own copy, and pull the original's changes into your fork without redoing your work by hand.

Where to find it: Connectors → open a connector → Manage access, Fork or Pull from upstream.

Before you start

You need Why
Owner or Edit access on the connector, plus connector:share Share a custom connector with a new member, team or the organization.
connector:create and a plan that includes custom connectors Fork a connector.
Edit access on the fork Pull from upstream.

Share a connector

A custom connector is private to its owner until the owner shares it. Only the owner and the people it is shared with can see it. Sharing decides who can see, use and change the connector's definition. It never shares any connected accounts, because everyone connects with their own credentials.

  1. Open the connector and choose Manage access.
  2. In Add people or teams…, pick one or more members or teams, or Everyone.
  3. Choose a level.
  4. Choose Share.
Level What the person can do
View See the connector and its configuration. With connector:create, fork it.
Use Do everything in View, and connect accounts to the connector.
Edit Do everything in Use, and change the connector's configuration, documentation and sharing. Pull upstream changes.

To remove a share, remove that member or team from the list in the same dialog.

If a share is removed from someone who connected accounts through the connector, those connections are blocked, and Elaichi flags them. They are not deleted. You can still delete them.

The connector's page shows a Shared access summary to people who can manage it.

Fork a connector

Forking gives your organization an editable copy of a connector's configuration and documentation. The original does not change.

  1. Open the connector, or open its row's actions menu in the list, and choose Fork.
  2. Check the Name. Elaichi suggests the original's name followed by "(Fork)".
  3. Check the Slug. Elaichi suggests the original's slug followed by -fork. Use lowercase letters, numbers and hyphens. The slug must be unique in your organization.
  4. Choose Fork.

Your fork opens as a custom connector that you own. A fork records where it came from, and that record is what makes Pull from upstream possible.

Fork is absent when you cannot fork the connector: a restriction blocks it, your plan does not include custom connectors, you lack connector:create, or the connector is a remote MCP server, whose address and sign-in cannot be copied.

Pull changes from the original

When the connector you forked from gains new tools or fixes, you can review them and choose which ones to bring into your fork.

  1. Open your fork and choose Pull from upstream.
  2. Wait for Comparing with upstream… to finish. If nothing changed, Elaichi shows You're up to date with upstream.
  3. Review the changes, grouped as in the table below.
  4. Select the changes you want. Select defaults restores the suggested selection, and Clear deselects everything.
  5. Optional: expand a change and choose Compare sides to see Your fork next to Upstream.
  6. Choose the Pull button, which shows the number of selected changes.

Your fork changes only for the selected items. Unselected changes stay as they are on your fork.

Group What it means Selected by default
New tools Added upstream since you forked Yes
Updated tools Changed upstream while your fork still matches the earlier upstream version, so the update is safe Yes
Config changes Changes to how the connector is set up, such as base URL, sign-in, credentials, pagination and rate limit Yes when safe or new from upstream. No when both sides changed.
Conflicts Changed upstream and also changed on your fork, or different with no shared starting point No
Removed upstream No longer in the original No
Warning

Selecting a Conflicts or Removed upstream item overwrites or deletes that piece on your fork. Read each one before you select it.

A fork made before Elaichi recorded where forks came from may not show Pull from upstream. A member with connector:manage and Edit access to the fork can link it to its original with the API call POST /connector/{slug}/link-upstream, giving the original's slug. After that, pull works like it does for any fork. Without the link, Elaichi refuses a pull.

What to know

  • You cannot edit a catalog connector. Fork it first.
  • Sharing with a team needs a team to exist. Create one under Settings → People → Teams.
  • A fork does not name its original if you cannot see the original.
  • Pull is selective. Elaichi applies only the changes you select.