Messenger and Google Chat are temporarily hidden from the integration list in workspaces without an active connection. Existing connections remain visible and unchanged. Google Chat also remains visible in the review workspace when enabled by the server.
How the page is laid out
GitHub’s status comes from Workspace GitHub App connections. Google Calendar shows Connected when at least one calendar account is connected. Personal GitHub sign-in is managed separately in Account → Profile → GitHub.
For services that open browser authorization, choose Connect once in the list. After confirmation, Cogno opens their settings. Direct visits to an unconnected service page still offer Connect and Setup guide; longer information on connected service pages is under Details.
The Microsoft Teams row reads the current connection and your unfinished setup for this Workspace:
While the state is loading, the button is disabled. If loading fails, Retry checks again instead of treating the connection as absent. Starting or resuming setup requires permission to manage integrations.
Teams settings shows the connected Team and tenant names. Connect and Resume start Microsoft sign-in in a popup on the web, or in the system browser when using the Cogno desktop app. When approval is needed, choose Open admin approval or Copy approval link to share it with your Microsoft tenant admin. After approval, use Select a Team to choose one Team, then Connect Team to confirm. In Channels, choose Start importing or Stop importing for each channel and review its current status. In Chats, choose Verify Microsoft account if prompted, then Include the group or meeting chats where the Cogno app is installed; each Project selects channels and included chats in its own Integrations settings. Existing tenant-wide connections retain their Event listening controls in compatibility mode until they are disconnected.
On the Free plan you can connect up to 3 integrations. Connecting a
fourth shows an upgrade message instead of starting the connection — upgrade
to Business to connect more. See Billing.
Set up an integration
PostHog and Sentry connect through their own hosted MCP servers. Select the app on Integrations, then complete its browser sign-in. Adding it to the Workspace requires permission to manage integrations; each member connects their own account. Open the connected app to review Agent tools and their Block, Ask, or Allow permissions. See Connect Sentry. For these hosted apps, Ask requires an updated Engine that enforces approval on every call. Older Engines and managed cloud execution refuse Ask calls; update the Engine or use a supported machine. Do not change Ask to Allow to bypass this restriction. Block remains blocked on every execution path. Other vendor-hosted MCP apps and custom server URLs are not available in production. Existing native integrations are unchanged. Where Add a custom app by URL is available, choose Only me under Available to to register an MCP server for your own runs, including Cloud runs. Other members cannot see or manage that registration. Enter the MCP server address, optionally a name, then choose Add and complete sign-in if requested. A server registered only on your computer does not automatically become available to Cloud runs. Members with integration management permission can instead choose Workspace to make an app available for members to connect their own accounts. You manage tool permissions for your own Only me registration; shared Workspace apps retain their existing integration management permission. For these hosted MCP apps, changing a tool to Block stops subsequent calls, including calls from a run already in progress. Changing Allow to Ask also blocks that running grant; start a fresh run to use the new approval setting. Changing Ask to Allow does not remove the current run’s approval requirement. If your sign-in expires and cannot be renewed, reconnect your own account from the link returned by the app. Under Agent tools, use a group’s dropdown to change all its tools together. To change only one tool, expand Set permissions per tool and choose that tool’s Block, Ask, or Allow setting. Other tools keep their settings. Mixed means the group contains different permissions; choosing a group setting replaces them all. Connect WhatsApp Business from Integrations → WhatsApp using Meta sign-in. New conversations can enter the Workspace’s Task workflow. See WhatsApp setup for requirements and the API reference for deployment and webhook details. These are the integrations you can connect today. Each has its own page with the connect steps.Slack
Turn channel activity into workspace context and get task notifications as
DMs.
Microsoft Teams
Use selected Team channels and explicitly bound chats as Project context.
LINE WORKS
Connect a Bot, assign rooms and DMs to Projects, and send Cogno replies.
Discord
Connect servers, channels, and messages for workspace context.
Google Chat
Bring Google Chat space messages in as workspace context.
ChatWork
Receive room messages and mentions for workspace context.
Messenger
Receive Facebook Page messages as workspace context.
GitHub
Import issues as tasks, sync repos and members, and track pull requests and
CI.
Turn new WhatsApp Business conversations into Tasks when work needs
attention.
Notion
Share selected Notion pages and databases with Cogno.
Jira
Choose the Jira projects each Project works in, and let agents read and
update their issues.
Linear
Choose the Linear teams each Project works in, and let agents read and
update their issues.
Google Calendar
Add Cogno Notetaker to supported video meetings from your calendar. Each
member connects their own account.
Set Workspace Tool permissions
Slack, Microsoft Teams, Jira, and Linear connection settings list the agent capabilities that Cogno manages. Choose Block, Ask, or Allow for each capability. This Workspace value is the security ceiling: a Project can inherit or reduce it for the same connection, but cannot increase it. On a current Engine, Ask applies to autonomous work too: a call that needs approval is not executed until the person explicitly agrees to that call, then Cogno can retry it. With nobody in the conversation, Cogno asks in the Slack or Teams thread the work came from and waits; an earlier agreement does not count, and without a yes it does not run or retry. Autonomous work does not require Allow merely because nobody is sitting at the machine. If an older Engine does not support this flow, update the Engine and verify the active version rather than widening permissions to bypass approval. Each capability names the Tools it grants. Under the choice, Tools lists every Tool an agent may call through it —slack_search_messages,
slack_send_message, and the rest — so the choice is not read from the
description alone. A Tool carries a check when the current mode runs it without
asking, a question mark on a dashed outline when the mode asks first, and a
struck-through name when the mode blocks it.
Coding agents
Claude Code and Codex are not listed on Integrations — there’s nothing to connect. Choose the coding agents a computer runs in Settings → Computers. See Run an agent on a task for how agent runs work and how to follow them.Your connectors
Open Account → Connections to control your personal MCP servers. Settings follow your account across machines and projects. On an updated local Engine, Cogno can look up your selected coding agent account’s connectors when needed. The starting instructions describe how to look them up; the full list is fetched only when requested. The lookup reports connector names, connection states and your saved permissions, helping Cogno avoid unnecessary reconnection or consent requests. Required approvals still apply. Claude Code and Codex both report live connection state when their runtime provides it; unavailable state remains unknown. Other members’ accounts and other coding agents are not included. Configuration and credentials are excluded, and connector lookup results are omitted from the shared conversation journal. The selected agent’s private transcript still contains its tool result. On Desktop versions that support only a shared switch, Enable / disable all controls Claude Code and Codex together. Off prevents personal connector use in Cogno runs. On uses each CLI’s existing settings and permissions; it does not force every configured connector to connect or grant new service access. Rows show Reject when off and Uses CLI settings when on. The shared switch remains usable without a Desktop update. A new shared choice replaces previous per-connector choices for both CLIs. Separate Claude/Codex bulk controls and individual MCP settings require a Desktop version that supports individual control. Those choices are not shown as editable on an older Desktop. On a supporting Desktop, expand Claude Code or Codex. The All connectors row places Enable all and Disable all above the indented server list. Both groups default to on when no preference has been saved.
Changing Claude Code does not change Codex. Individual edits show Some
connectors enabled when the group has mixed settings. You can allow one server
after switching everything off, or reject one after switching everything on.
New servers follow the group’s last bulk choice until individually edited.
Saved changes apply from the next turn, including the next turn of an existing
conversation. They do not cancel a tool call that is already running. Connection
errors, sign-in requirements, and provider permissions still apply. Connector
credentials stay with Claude Code or Codex. Ask before use also applies in a
full-access Session. Refresh
re-reads the machine’s server inventory; it does not change permissions.
Use the desktop app to read this computer’s servers. The page explains which
controls your installed Desktop supports; shared on/off remains available on
versions without individual connector control.
Choose how Cogno uses each MCP and Tool
Choose one usage setting beside an MCP server:
Expand Set individual tools to make an exception for a Tool. Each Tool displays
its effective behavior, including when it inherits the MCP setting. Open its menu
and choose a setting for that Tool, or Same as MCP to follow the MCP setting.
Tool names and descriptions come from the connected
coding agent; you do not need to write instructions or edit an MCP configuration
file. These choices follow your account, including when a server with the same
name appears on another machine.
Ask for others’ requests is contextual agent guidance, not a guaranteed
prompt-injection barrier. Cogno checks the Task and conversation to judge your
intent and asks the owner of the personal connection when confirmation is needed.
If Tool details are unavailable, you can still set the MCP-wide choice. Refresh
retries discovery. Previously retrieved Tool lists are labeled when stale; a failed
lookup is not presented as an empty list. Older Engines may show no Tool details.
Not listed
The page lists only integrations you can connect today. Planned integrations are not shown, so the list never promises a date the product has not set.Vercel has no self-serve connect flow. It appears, as
Connected, only when your workspace already has a connection.
Related docs
- Concepts — how sources and actions feed the loop.
- Work with Tasks — where a connected source shows up on the task it created.
- Run an agent on a task — hand a task to a coding agent on your machine.
- Getting started with Cogno — set up the loop end to end.