Connectors (MCP)

Connectors let Gluon use other services, such as Notion, Linear, your broker or a payments dashboard, through MCP servers. Each connection is yours: other members don’t see it, and your Gluon uses it in your private chats and your requests in groups. An artifact can read it only after you allow it; see Used by artifacts.

Add a connector

Open Settings → Connectors & tools. It lists Gluon’s built-in tools and your connected servers, and waits for your servers to load before saying none are connected:

• Discover servers, below your connected servers, lists popular servers you can connect in a click, such as Notion, Linear, Atlassian, Airtable, Canva, Dropbox, Zapier, Stripe, Razorpay and Indian brokers like Kite by Zerodha, Groww, Upstox and Dhan.
• Add server, at the top of the page, connects any MCP server by its HTTPS URL. Give it a name and, if the service needs an API key or token, add Headers, such as Authorization with Bearer <token>. Header values are hidden after saving; to change them, remove and add the server again.

Servers that use sign-in ask you to sign in to the service. Until a server is ready, its row shows Sign-in needed, Connecting… or Failed; once ready, its page shows how many tools it has.

Using connectors

Just ask: “Create a Linear issue for the login bug” or “What’s in my Notion reading list?” Gluon searches your connected servers for a suitable tool and calls it. Adding a connector doesn’t slow Gluon down or change its other tools. Gluon can use all of your connectors in every private chat; you can’t turn one off for a single chat.

Connector calls are free; you only pay for Gluon’s reply as usual.

When Gluon suggests a connector

If you ask for something a service in Discover servers would answer, such as “What’s in my Zerodha portfolio?” or “What’s on my Linear board?”, and you haven’t connected it, Gluon answers what it can and adds a card for that service, up to three at a time. The card shows the service’s icon, name, what it offers and its real address, from Gluon’s own list of Discover servers; Gluon can’t suggest any other server, so a message or web page can’t get it to show you a card for an unknown one.

• Connect adds the service to your account without leaving the chat. The card follows it: Connecting…, then Connected.
• If the service needs you to sign in, the card shows Sign in, which opens its sign-in page in a pop-up. If it failed, Fix opens its page, where you can reconnect or remove it.
• Once it’s connected, just reply, such as “done”, and Gluon uses it from your next message. The new connector is an ordinary one: it appears in Connectors & tools with its own default permissions.

Gluon doesn’t suggest a service you’ve already connected, one you turned down earlier in the chat, or one for something its built-in tools already do, such as searching the web.

In a group, your Gluon can suggest a service in its reply too. Every member sees the card, each with their own Connected or Connect for their own account; it never shows whether you have the service.

Ask about your connectors

In a private chat, your Gluon can tell you which servers you’ve connected, whether each one works or needs you to sign in again, and each tool’s permission: “Which connectors do I have?”, “Is my Kite connection working?”, “Does Linear’s create issue tool ask first?”. It shows each connector with a button to its page, and a button to Discover servers. It sees only each server’s domain, never its full address, headers or sign-in link.

Your Gluon can’t add, sign in to, reconnect or remove a connector, or change a tool’s permission: ask, and it gives you the button to the page where you do it, or, for a service in Discover, a card to connect it. It answers these questions only in your private chats, not in groups.

Permissions

Each connector tool has its own permission. When you connect a server, an AI check marks each tool Read (it only reads) or Write (it changes something, or it’s unclear). The server’s own labels are only a hint, because some servers get them wrong. Read tools get Allow, and write tools get Auto. If the check marked a tool wrongly, change its kind beside the permission on the server’s page, and its default follows.

Change any tool to Allow, Auto, Ask or Off on the server’s page. It lists the tools by title, with each tool’s own name in its info button, and works like the built-in tools’ page: search and a permission filter at the top, a dot on tools you changed, Saved beside each change and Loading permissions… until your saved choices arrive. Ask for everything switches every tool that isn’t already Ask or Off to Ask. Reset to defaults clears your permission changes for that server; kinds you corrected stay. If a server changes a tool’s definition, the tool gets a fresh default and your old setting for it is cleared.

Approval cards show the connector, the action and its exact input. A call that waits for approval re-checks the permission before it runs, so a tool changed while you were deciding can’t run under its old setting.

Suggest a server in a group

To tell a group about a server you use, open its page and choose Suggest in group. Gluon shows the exact address members will see; check it holds no key or token, pick the group and choose Suggest. Gluon posts a card in the group as you, naming only the server: never your sign-in, headers, tokens or permissions.

• The card shows a popular server’s name and icon only when its address exactly matches it. Any other server shows its real address, such as mcp.example.com, with “Custom server, added by” your name, so a lookalike name can’t pass as a service you know.
• Each member sees Connected if they already have that server, or Connect, which opens Add server with its address filled in and shows where it connects before anyone signs in. They connect it with their own account; if it needs a key, they add their own Headers.
• Their tools start from their own defaults, not your permissions.

Addresses that carry a key, such as ?apikey=…, are posted without it.

Agents and groups

• Custom agents use all your connectors, including ones you add later, or only the ones you choose in their settings. See Agents.
• In a group, your Gluon can use your connectors for your own requests, under your personal permissions. Its replies may show their results to the group, so it’s told not to share your private details unless you ask.

Used by artifacts

An artifact that uses your connections reads a connection only after you allow it. Each server’s page lists, under Used by artifacts, every artifact you allowed to read it: its title, or “An artifact you can no longer open”, who sees what it reads (“Only you” or “Everyone in” a group) and the tools you allowed. Withdraw stops that artifact’s reads at once. Anything it already saved stays until the artifact or its data is deleted. An artifact deleted since leaves the list the next time the page loads.

Artifact calls on one connection are limited to 120 a minute for each artifact, so one viewer reloading it over and over can’t use up your account’s own limits with the service.

Removing a connector

Remove a server from its page. Its name is never reused for another connection, so an old call can’t reach a different account. Removing it also ends every artifact’s consent to read it.