Skip to content

Share an MCP connection without the API key

How to share an MCP connection without the API key in Elaichi: grant a teammate use of a connected account, and take that access back.

Raajshekhar Rajan 7 min read
A connected account row in Elaichi showing a sharing list with a team granted use access, and the stored credential hidden

The situation

Someone on your team connected an account. Now a colleague needs the same tools in Claude or ChatGPT, and the shortcut everyone reaches for is to paste the API key into a second setup. That is how one credential ends up in three places with no record of who holds it.

In Elaichi you share an MCP connection without the API key instead. A connection is a single stored row that the organization reuses through sharing grants. It is not something each toolbox or team re-authenticates separately. The same connection can be pinned into any number of toolbox entries. A grant can extend it to a user, a team, or the whole organization, without reconnecting. MCP is the protocol that lets an AI client call tools in your apps; a grant is the record that says who may use a given resource.

The credential never travels with the grant. Connector secrets are not kept in Elaichi's main data. A separate credential service holds every connected account's secrets in encrypted form. Elaichi fetches them into memory only for the call that needs them. Encryption at rest is AES-256-GCM, and the key can be rotated without re-encrypting old rows. Nobody has to hand an AI client a personal key to get work done.

This is the shape the protocol expects. The MCP specification puts authorization on the OAuth 2.1 model, where a client holds a token issued for the server rather than a credential belonging to an upstream app (modelcontextprotocol.io, checked November 2026).

What does it mean to share an MCP connection without the API key?

It means granting access to the connection row, not to the secret behind it. The grantee calls tools through that connection. They never see, copy or export the token or key.

Connections, toolboxes, templates and connectors are all shared through one mechanism: a grant row on that resource. A grant is one of three levels. View lets someone see the resource. Use lets them call tools through it. Edit lets them change it. The grantee of a connection shared at use runs tools through it the same way they would run any other tool they hold use on.

One consequence matters more than the rest. Every call through a connection fetches credentials from that one connection's bound account, whoever is calling. The caller's own identity plays no part in whose credential is used. So a shared connection acts in the third-party app as its owner's sign-in, for everyone it is shared with.

That is the real trade-off. Settle it before you share anything. If the app on the other end should see each person as themselves, a shared connection is the wrong tool. Each person connects their own account instead. Each rep's own Salesforce access, in ChatGPT walks through the per-person shape.

Who can share a connection, and on which plan

The connection's owner shares it. Creating a shared connection needs the connection:share permission, which the built-in Member role holds. An edit grantee can share it too, with the same permission.

Sharing is a Gold feature. On the free Personal plan the share routes and the share operations are refused, and a non-empty share list on create is refused as well. Personal is for one person, so there is nobody to share with. Removing a grant is never plan-gated, so a workspace that drops to Personal can always take back what it set.

A connection with no grants at all is private to its owner. Any grant row, direct, team or organization-wide, makes it reachable by someone else.

How to share a connection with a team

In the console, each connection's row has a Manage access action. The same choice appears when a connection is first added: an optional Share with field that starts at Private, only you can use this connection.

  1. Open the connection and choose Manage access.
  2. Pick the grantee: one member, one team, or the whole organization.
  3. Pick the level. Use is the one that lets them run tools. View only shows them the connection exists.
  4. Save.

The grantee does not reconnect, does not approve anything at the app, and does not get a key. On their next call the connection's tools are in reach. Under an "Everything I can use" grant, a member reaches every active connection they own or hold use or edit on as plain tools, through their All tools toolbox.

What a grantee cannot see is who else holds a grant. Only a resource's owner or an edit-level grant holder may see the share list. A view or use grantee cannot.

How to take a share back

Remove the grant. For tool calls, Elaichi reads toolboxes, shares and connections from the organization's data store on every request. In Elaichi, revoking a share or disconnecting an account takes effect on the caller's next call.

That is a different clock from the one role and restriction changes run on. A role change, a team membership change, a restriction edit or an access grant change reaches every surface within about two minutes, because the resolved context is cached briefly. A share revocation is not cached that way. The next call fails.

Deleting the connection outright is the heavier option. Deleting a connection deletes Elaichi's stored credential for it. Elaichi makes no call to the app to revoke the token, so the token stays valid at the app until it expires or someone revokes it there. If you are removing access because the credential itself is suspect, rotate or revoke it in the app as well. OAuth's own guidance expects revocation to happen at the authorization server that issued the token (RFC 7009, checked November 2026).

One more thing to check after revoking. Toolbox entries pinned to that connection do not vanish. If an entry's delegator loses use on the pinned connection, the entry resolves as unmet for everyone who opens or calls the toolbox, its owner included. It stays listed but is not advertised or runnable. Someone with edit on the toolbox who holds use on the connection re-pins it, and becomes its new delegator.

What connection:manage does not let an admin do

This is the question that trips people up during a security review. State it plainly.

Holding the connection:manage permission does not, by itself, let a member reconnect, delete or transfer a connection they do not own and hold no edit-level grant on. The connection routes never check that permission on any connection route. The permission's own description says the same: it reaches only a connection you own or hold an edit share on, never one merely shared with someone else.

The wider rule behind it: a member, including an Org Owner or Org Admin, sees only what they own or what has been explicitly shared with them. No organization permission widens a listing or confers revoke, manage or transfer rights on a shareable resource, for any owner or admin.

So an Org Admin cannot quietly take over a colleague's connected account. If the organization needs that, the connection has to be shared with them at edit, or transferred. Keeping credentials out of the hands of anyone who merely holds an admin role matches the OAuth security guidance on limiting where a credential can travel (RFC 9700, checked November 2026).

Transferring a connection before its owner leaves

If a team depends on one person's shared connection, move it before that person leaves. A transfer rewrites exactly one thing: the connection's owner. The new owner must already be an active member.

Every existing grant stays as it was. The grant rows are a separate table the transfer never touches. The outgoing owner can be given their own use share in the same call, as an explicit choice, which keeps the entries they pinned working.

The credential does not move with the row. A transfer never rebinds the connection to the new owner's account, so the connection keeps acting in the third-party app as whoever was signed in when it was connected. If the departing member connected the app with their own login, deprovision or reconnect that account separately. Elaichi also makes no call to the app to revoke anything on transfer.

Timing matters. Outside offboarding, only a connection's owner can transfer or delete a connection. A shared connection left without an action during a removal stays owned by the removed member. After the removal, no remaining member can transfer or delete it. Transfer it as part of the removal, or, better, have the owner transfer it themselves first, with Keep my access, so the toolbox entries they pinned keep resolving.

When a shared connection is the wrong answer

Three cases where you should not share the connection at all.

Per-person identity in the app. If the app should attribute the action to the person asking, each person connects their own account. A shared connection cannot do it, because the credential is the connection's, not the caller's.

You want to lock an argument. To hold an argument fixed for a team, keep the connection unshared, pin it into a toolbox entry with the frozen value, and share the toolbox at use. Anyone who can use the connection directly has the same tool without the lock. Lock AI agent tool arguments covers the mechanics.

You want to limit which tools they get. Sharing is not a tool filter. A use grantee reaches the connection's tools. Narrowing to a subset is a restriction, written on a role or on one member, naming connectors and tools. Restrict one AI tool or the whole app? works through the choice. Narrowing a whole team to reads is the same mechanism, covered in read-only access to your company apps.

Sharing a toolbox is a different shape again, with its own delegation rules. Share an AI tool setup with a team, once is the post for that.

For the access model underneath all three, see Resource ACL view use edit, and browse what is connectable at /connectors/.

FAQ

Frequently asked questions

Does sharing a connection in Elaichi expose the API key or OAuth token?

No. In Elaichi a connection is a stored row, and sharing grants access to that row rather than to the secret behind it. Connector secrets live in a separate credential service in encrypted form, encrypted at rest with AES-256-GCM. Elaichi fetches them into memory only for the call that needs them. A person granted use of a connection runs tools through it and never sees, copies or exports the credential.

Whose account does a shared connection act as in the third-party app?

The connection's own. Every call through a connection in Elaichi fetches credentials from that one connection's bound account, whoever is calling, so a shared connection acts in the third-party app as its owner's sign-in for everyone it is shared with. If the app should see each person as themselves, each person connects their own account instead of sharing one.

How quickly does revoking a connection share take effect?

On the next call. For tool calls, Elaichi reads toolboxes, shares and connections from the organization's data store on every request. In Elaichi, revoking a share or disconnecting an account takes effect on the caller's next call. This is faster than a role, team or restriction change, which reaches every surface within about two minutes.

Can an Org Admin manage or delete a connection someone else owns?

Not by permission alone. Holding the connection:manage permission does not let a member reconnect, delete or transfer a connection they do not own and hold no edit-level grant on. In Elaichi a member, including an Org Owner or Org Admin, sees only what they own or what has been explicitly shared with them, and no organization permission widens that for a shareable resource.

What happens to a shared connection when its owner leaves the organization?

Transfer it before the removal. A transfer rewrites only the connection's owner and leaves every existing grant as it was. The credential is not rebound, so the connection keeps acting in the app as the account that was signed in when it was connected. A shared connection left without an action during a removal stays owned by the removed member, and no remaining member can transfer or delete it afterwards.

Put AI to work in your own apps

14 days of Black, no credit card. Start with one app and one team.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot