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

# Share a setup link

> Invite a client or third party to connect an MCP connector without giving them access to your workspace.

When adding a new MCP, you can generate a shareable link so that someone outside your workspace can complete the access setup on your behalf. This is useful when the account, credentials, or OAuth sign-in belong to a client, a partner, or a colleague in another team — for example, an agency connecting HubSpot on a client's CRM, or an IT team that prefers to enter a database password themselves.

The recipient opens the link, signs in through OAuth (for connectors like HubSpot or Slack) or fills in the credentials the connector asks for, and the values are saved to the draft MCP connection in your workspace. You can then resume the setup, select the tools your agents can use, and save the MCP.

***

### **How it works**

While adding a new MCP, the **Setup access** step shows a **Share link** button next to "Need someone else to connect …?". Generating the link returns a URL you can copy and send to the recipient.

<Steps>
  <Step title="Start adding a new MCP">
    Go to **Activate → [MCPs](https://app.nekt.ai/mcps)**, click **New MCP**, and choose the MCP connector you want to set up.
  </Step>

  <Step title="Name your MCP">
    Give the MCP connection a name and a description. Continuing creates it as a draft in your workspace, which is what the setup link fills in.
  </Step>

  <Step title="Generate the setup link">
    On the **Setup access** step, click **Share link**. Nekt returns a setup link you can copy and share.
  </Step>

  <Step title="Send the link to the recipient">
    Share the URL with the client or third party through your preferred channel (email, Slack, WhatsApp, etc.). They do not need a Nekt account.
  </Step>

  <Step title="Recipient connects the account">
    The recipient opens the link and sees a page identifying who requested the connection and which MCP connector is being set up. They sign in with the provider, or enter the credentials and click **Submit** — depending on what the connector requires.
  </Step>

  <Step title="Resume the setup">
    Once the recipient finishes, the credentials are saved to the draft MCP connection. Return to it in your workspace, continue to **Select tools**, choose which tools your agents can use, and click **Save**. The MCP becomes active and its tools are available through the Nekt MCP Gateway.
  </Step>
</Steps>

***

### **Partial information is allowed**

The recipient does not have to fill in every field. They can submit whatever information they have access to and leave the rest blank. You can complete the missing fields yourself afterwards, or send another setup link to a different person to fill in the remaining values.

***

### **Security and access**

The setup link is scoped strictly to the MCP connection it was generated for. The recipient cannot reach any other part of your workspace, see your other MCPs or their tools, or query catalog data. Credentials entered through the link are encrypted and stored by Nekt; your agents never see them.

<Warning>
  The setup link contains a token that **expires 24 hours after it is generated**. It also stops working once the MCP connection is active. If the recipient does not complete the setup in time, generate a new link from the same draft.
</Warning>

<Note>
  The recipient sees only the setup form for the specific MCP connector they were invited to connect. Access ends as soon as the token expires or the MCP connection is activated.
</Note>

***

### **When to use a setup link**

* A client owns the CRM, chat workspace, or ad account you want your agents to work with — and you need them to sign in or paste credentials.
* An IT or security team controls the credentials for an internal system, such as a database, and they prefer to enter the values themselves.
* A teammate without a Nekt seat needs to provide access details for an MCP you are setting up.

<Tip>
  Connecting one MCP per client? The same flow is available through the Platform API, with a callback webhook that tells you when each client is done. See [Connect an MCP with a setup link](/platform-api/mcp-connections/setup-link).
</Tip>

## Skills for agents

<Snippet file="agent-skills-intro.mdx" />

<Card title="Download Share setup link skills file" icon="wand-magic-sparkles" href="/mcps/share-setup-link.md">
  Share setup link documentation as plain markdown, for use in AI agent contexts.
</Card>