Connectors
Give Endless access to the tools you already use, with your own sign-in and under a workspace ceiling.
A connector gives Endless a way into a tool you already use — your issue tracker, your notes, your CRM — so a chat can read from it and act in it. The page is Settings → Connectors, headed "Connect the tools your team already uses", and every member of the workspace can open it.
A skill teaches Endless how you work. A connector gives it access to somewhere else. They're switched on and off the same way, which is the only thing they have in common — see skills and knowledge for the distinction.
Connecting one
Each connector is a card with its name, a line about what it does, and a + button labelled "Connect" followed by the tool's name. What happens when you press it depends on how that particular tool authorizes.
Sign in with the provider
Some tools authorize through the account you connect to Endless itself. You approve the permissions in the provider's own window and come back. You may be asked to re-verify your identity first — that's expected.
Authorize in a browser window
Most tools run their own authorization: you're sent to the tool, you approve the access there, and you land back on the connectors page with "Connector added".
No sign-in at all
A few — public documentation servers, mostly — need no account. The card's button simply switches them on for you.
Once connected, the card shows a check. Hover or focus it and the check becomes a × — that's the disconnect. Next to it sits a small health indicator that reports what the tool is actually doing: "Checking connection", then how many tools it offers, or "Not responding" if the server is down.
A couple of connectors depend on an application being registered with the provider on our side before anyone can complete the flow. Where that isn't in place yet, connecting fails with a "Couldn't connect" toast and retrying won't help — the fix isn't yours to make. If one specific connector refuses repeatedly while others work, that's the likely reason.
Finding one
The catalog is a searchable grid: a "Search marketplace…" box and a Sort menu that offers Featured or Name. Today it covers development and product tools, notes and meeting tools, CRM and payments, analytics, and documentation servers.
The list grows without anything being installed or updated on your side — what's on the page is what's available. Search it rather than trusting a list written down somewhere.
Two switches, not one
Connectors follow the same two-level model as skills, with one extra step of their own.
The workspace ceiling
A Workspace tab, visible only to people who can manage the workspace's tools — a governance permission admins hold by default and ordinary members do not. Its hint: "Turn a connector off here to remove it for everyone in the workspace. Members choose for themselves among the ones left on."
Your own choice
The My tools tab, which is what everyone else sees on its own. Where the workspace has turned something off, your card shows a locked "Off" badge instead of a button.
Your sign-in
The step skills don't have. Enabled is not connected. A connector left on for the workspace but never signed into does nothing at all — the credentials are yours personally, and nobody can grant them on your behalf.
Turning a connector off for the workspace removes it for everyone immediately, including people who had already connected it. Turning it on connects nobody — each person still signs in themselves.
Who holds the ceiling
The permission behind the Workspace tab, and which roles have it.
Per-person overrides
An admin can also set one person's connectors from their profile in Members, under Access — still capped by the workspace ceiling.
Adding a server of your own
Below the catalog sits "Custom MCP servers" — "Add your own MCP server (Slack, Granola, …) to use its tools inside chat." If a tool you use publishes an MCP endpoint, you can point Endless at it without waiting for it to appear in the catalog.
Describe it
A Server label (the example given is "Label (e.g. Granola)"), the Server URL, and
a Transport — http or sse, whichever the server documents.
Choose how it authenticates
Bearer token if the server takes a token you already hold — paste it and it's encrypted before it's stored. OAuth if the server runs its own sign-in: "You'll be redirected to the server to sign in after adding it."
Add it
"Add server", or "Add and connect" when the OAuth handshake follows immediately. The server then appears as a row you can Connect, Edit or Remove, with the same My tools and Workspace tabs — the workspace hint here reads "Turn a server off here to remove it for everyone in the workspace."
Adding a custom server needs permission to create content, which members and admins have by default and viewers don't. Editing or removing one someone else added needs the broader permissions for acting on other people's work.
An empty section says so: "No custom servers yet" / "Add an MCP server URL above to expose its tools to chat."
A custom server is a live connection to somewhere outside Endless, holding credentials you supplied. Add servers you trust, and remove ones you stop using rather than leaving them switched off.
Using them
In chat
A connected connector's tools are simply available. You describe what you want; Endless reaches for the right one.
In scheduled runs
A schedule's Tools control lists only the connectors you have actually connected — an unconnected one couldn't run unattended, so it isn't offered. Disconnect a connector and any schedule relying on it starts failing.
Narrowed per schedule
You can switch individual connectors off for one schedule without changing what's available to you everywhere else.