Skip to main content
Cogno runs an MCP server for your own AI apps. Add its URL to ChatGPT, Claude, Claude Code or Codex, approve the connection on a Cogno page, and the app works with Tasks in one workspace as you. Open Settings → MCP to copy the server URL and disconnect apps. The steps for each app are below.

​
What a connected app can do

The app acts with your role. A viewer can search and read but not create or update. Your role is checked on every call, so a role change or leaving the workspace takes effect immediately.
A connected app can see every Task in the workspace you choose, and the Tasks it reads (titles, descriptions, people, dates) are sent to that app’s provider.

​
Connect an app

  1. In Claude, open Customize → Connectors, choose + Add, then Add custom connector.
  2. Name it Cogno, paste the URL from Settings → MCP and choose Continue.
  3. Choose Connect, then approve on the Cogno page.
On Team and Enterprise plans an owner adds the connector in Organization settings → Connectors first.

​
Approve the connection

The Cogno page shows the app’s name, what it may do, and where your answer is sent. Choose the workspace and Allow. If the answer goes to localhost or 127.0.0.1, it is a program on your computer, such as Claude Code or Codex: allow it only if you started the connection yourself. If the page says the app’s name is not verified, the app named itself: allow it only if the destination shown is the app you meant to connect.

​
Disconnect

In Settings → MCP, choose Disconnect next to the app. Its access ends immediately. Each approval is its own connection, so the same app on two computers shows twice and each one disconnects on its own. If you are removed from a workspace, your connections there stop working and do not come back if you are added again.

​
How it works

The server is at /mcp/user on the Cogno API and follows the MCP authorization spec: OAuth 2.1 with PKCE, Protected Resource Metadata, dynamic client registration and Client ID Metadata Documents. Access tokens last one hour; refresh tokens rotate on every use. A refresh token used again within a minute (an app retrying) gets new tokens; used again later, it ends the connection.