Connectors

The Connectors page is where a workspace connects to the outside: mailboxes and calendars, GitHub and Slack, MCP servers and any service an agent reaches with a key. Open it from Connectors in the sidebar's Intelligence section, with Agents, Routines and Skills, or with the /mcp slash command.

The pageCopy Anchor Link

It follows the layout of the Agents and Routines lists: a title, then a bar with two tabs, a filter, a search and an Add menu, then a short explainer.

• Integrations holds the mailboxes, calendars, GitHub and Slack, synced into the app. MCP holds the MCP servers your agents open on demand. Each tab counts its connected cards.
• Connected shows a card per connector and per scope: your own accounts and the workspace's never share a card. A card says who it is for, For you or Shared with the workspace with the name of the member who connected it, how many accounts it holds, and Reconnect when the provider's grant has lapsed or the connection fails.
• To connect lists the connectors Standards offers. The filter narrows it by category. The + on a card connects it For me or For the workspace, and says who will get access.
• Add opens Custom MCP server, a form for a server by its address, or Connect with the agent.

For me connects the account for you alone; For the workspace shares it with every member and their agents. The workspace choice is offered to members who can read workspace connectors, and a shared mailbox or calendar asks for a confirmation first. GitHub and Slack connect for the workspace only. A connection's progress and failures show as notifications; a provider that refuses on its way back says why above the list.

Click a card to open its dialog:

• What agents can do with the connector.
• The connected accounts, each with a ⋯ menu: rename, trust, disconnect, reconnect, signature and authorize sending, as the connector allows. Connected mailboxes and calendars describes the access levels.
• Connect, to add another account for you or for the workspace.

Connect with the agentCopy Anchor Link

For a service the gallery does not list, the agent can connect it with an API key. Choose Add then Connect with the agent, or search for a name with no match and choose Connect "name" with the agent. Either opens a new conversation with an unsent message for you to send or edit: "Help me connect a service to Standards with an API key." from Add, and "Help me connect X to Standards with an API key." from the search, naming the service you typed.

The agent then:

1. checks how the service is reached;
2. asks for the key through a setup card, never in the chat;
3. tests the access;
4. loads or creates a skill for the service, so later conversations know how to use it.

When the setup would need an OAuth app, an admin console, or the service has no public API or needs a paid plan, the agent says so and does not try. When the service has a catalogue connector, it offers that instead.

Next stepsCopy Anchor Link

Connect GitHub, Slack or a mailbox or calendar, or grant a connector to an agent.

• Book a demo