Connect Aide to Claude and ChatGPT

Your team can now add Aide to Claude and ChatGPT as a connector and sign in with their Aide account, no API key to copy. From a chat, they can search your knowledge, look up a customer's orders, read and reply to conversations, update them, and refund, cancel or approve order changes, all as themselves and within what their role allows in Aide.

How it behaves

Sign in with Aide: add Aide's MCP server address as a custom connector in Claude or ChatGPT. It sends you to Aide to sign in, shows which app is asking, the workspace it will connect to and what it may do, and connects once you approve. Nothing is shared if you decline.
Read-only or read and write: an app can ask to only read (knowledge, orders, conversations, analytics) or also to act (add notes, reply to customers, update conversations, request and approve order changes). You see which before approving.
As you, within your role: everything the app does is recorded as you, and it can only do what you can do in Aide. Agents don't see analytics; refunds above your approval limit wait for an admin, as they do in the inbox.
Replies and refunds ask first: tools that send a message to a customer or change an order are marked as such, so Claude and ChatGPT ask you to confirm before using them.
ChatGPT company knowledge: ChatGPT can search and cite your Aide knowledge base in its answers and deep research.
See and disconnect apps: Settings > Developers lists the apps you've connected, when each was last used, and a Disconnect button that cuts it off at once.
Stays connected: apps stay signed in for 30 days after they were last used. Leaving the workspace or being deactivated disconnects them.
Which apps: Claude (web, desktop and mobile) and ChatGPT, plus apps running on your own computer such as Claude Code. Other AI apps that sign in the same way will be added once checked.

Also in this change

The MCP server's tools now cover more of the Aide API: a conversation's orders and customer details, return eligibility, order changes waiting for approval, macros, topics, products, knowledge documents, teammates, and the analytics overview and satisfaction figures. Teammates are shown only the tools their role can use.
Finding conversations takes all the filters of the conversation list, and pages through results.

For developers

OAuth 2.1 authorization server for POST /mcp: RFC 9728 metadata at /.well-known/oauth-protected-resource/mcp, RFC 8414 metadata at /.well-known/oauth-authorization-server, RFC 7591 registration at POST /oauth/register (Claude, ChatGPT and loopback redirect URIs), GET /oauth/authorize (authorization code, PKCE S256, resource, iss in the response), POST /oauth/token (refresh tokens rotate), and POST /oauth/revoke. Scopes aide:read and aide:write. A 401 on /mcp carries WWW-Authenticate: Bearer resource_metadata="…".
OAuth access tokens last an hour and work only on POST /mcp and the API operations behind its tools.
New: GET /v1/connected-apps and DELETE /v1/connected-apps/:id, and the consent endpoints GET /v1/oauth-authorizations/:id, POST …/approval and POST …/denial (dashboard sign-in only).
MCP: 33 tools (from 12), search and fetch in the shapes ChatGPT uses for company knowledge, openWorldHint on tools that reach outside Aide. docs/mcp.md lists them.

All changes