Skip to main content

​
Overview

Connectors let Stella, your AI teammate, use the tools you already work in. A connector is a remote MCP server. The catalog has vetted ones: Slack, GitHub, Linear, Notion, HubSpot, Attio, Apollo and Stripe. You can also add any remote MCP server by URL as a custom connector. It works like connectors in Claude and ChatGPT. Manage them under Settings → AI → Connectors.

​
Connect one

  1. Go to Settings → AI → Connectors.
  2. Find the connector under Browse and choose Connect.
    • Every catalog connector signs in: it opens the provider’s own consent screen in your browser. Approve it and you’re back where you started, connected.
    • API-key connectors are custom ones added with a key. Custral lists the server’s tools with it before saving, so a bad key never saves.
  3. That’s it. Stella can use its tools on your next message.
You can also connect from where you already are:
  • A provider’s page. The Slack channel and integration pages show Let Stella use Slack, with a one-click Connect.
  • Inside Stella. Ask about something a connector covers that isn’t connected (“what did the team say in Slack about Acme?”), and Stella shows a Connect card instead of saying it can’t.

​
Who connects

  • Each person connectors (Slack, GitHub, Linear, Notion, HubSpot, Attio, Apollo): every member connects their own account, and Stella sees only what that person can. Any member can connect their own.
  • Workspace connectors (Stripe): one shared connection that an admin sets up.

​
Your private messages stay yours

A per-person connector runs as you, so Stella can read your DMs and private channels, and nobody else’s Stella can use your connection. Once Stella has read from one of your per-person connectors in a chat, it asks before writing anything back into Custral (a record, a note, a task, an email), even in Auto mode and even if you set “Always allow” for that tool. The approval card says the write uses content only you can see, because anyone who can open the record will see what’s written there.

​
Add a custom connector

Admins can add any remote MCP server:
  1. Choose Add custom connector.
  2. Enter a name and the remote MCP server URL (https://…).
  3. Open Advanced settings if the server needs it:
    • Authentication: Sign in (OAuth; the default, using dynamic client registration), API key (optionally in a named header such as X-API-Key), or None.
    • Who connects: each person, or the whole workspace.
    • OAuth client ID and secret, for servers that don’t support dynamic client registration.
  4. Choose Add, then connect it.
Only add servers you trust. Stella sends a connector whatever you ask it to look up there. Custral only calls public https addresses. It refuses localhost, private networks and cloud metadata addresses, and re-checks every request and redirect.

​
Point Stella at one

Type / in Stella and pick a connector (for example /slack). It becomes a chip on your message, and Stella uses that connector’s tools first. Without a chip, Stella picks connected tools when your question fits.

​
Configure

Choose Configure on a connected row:
  • On: hide its tools from Stella without disconnecting.
  • Let Stella use write tools: off by default, so connectors start read-only. When on, Stella can use tools that change data (for example, create an issue). It asks for your approval before every one. Tools the server marks destructive are never used.
  • Tools: every tool the server offers, marked Read, Changes data or Destructive. Turn off any you don’t want Stella to use.
  • Inbound events: create a URL the connected system can post events to. Each post fires the Connector Event Received workflow trigger (see Triggers). The URL contains its own secret, so it’s shown once. Replace it if you lose it.
  • Disconnect removes your connection and its stored credential. Remove connector (custom connectors, admins) disconnects it for everyone.

​
Troubleshooting

  • Stella says a connector isn’t connected. Connect it, or turn it back on under Configure.
  • A row says Reconnect. The key was revoked or a sign-in expired. Choose Reconnect.
  • “That URL was refused.” Custom connectors must be public https addresses.
  • A tool is missing. It may be a write tool (turn on writes), turned off under Tools, or marked destructive by the server.
  • Sign-in fails for a custom connector. The server may not support dynamic client registration. Add its OAuth client ID and secret under Advanced settings.