Skip to main content
Six applications can connect to the Coffee Chats connector at https://mcp.coffeechats.me/mcp. After reading this page you will know which applications those are, the client identifier each one uses, and why some of them need no identifier at all. Any application that is not on this list is refused before it reaches a sign-in page.

​
The six applications

“Published address” means the application sends the address of its own Client ID Metadata Document as its client identifier, which is what Claude’s Use Claude’s published identity option does. The short identifier still works for each of those applications. To connect one of them, follow the setup steps for it in the quickstart.

​
How each application receives its authorization code

Claude Code, the Codex command-line tool and the Cursor desktop app are native clients. Each one receives its authorization code on a loopback address on your own machine. For Claude Code and Codex the address is matched on scheme, host and path with the port ignored, because each tool picks a free port when it runs. The Cursor desktop app names a fixed port on its own documentation page, and that is the address registered for it. The Claude entry for the web and the desktop, the ChatGPT entry and the Cursor web agents entry are web clients. Each one receives its authorization code at a fixed address on its own vendor’s site. Cursor is two entries rather than one because Cursor uses a different return address for each surface a student signs in from, and one registration carries one kind of address. All six are public clients that use PKCE. PKCE means the application proves, when it exchanges the authorization code, that it is the same program that asked for the code. None of them holds a shared secret with Coffee Chats, because a program installed on many machines cannot keep one.

​
Documentation search and the connector are two different things

The Coffee Chats connector at https://mcp.coffeechats.me/mcp is the one that reaches your account. Account access needs its own authorization, with the permissions you approve on the Authorize access page. No page in this documentation carries account data, because student data is not allowed in it.

​
Next steps

Connect an agent

The setup step for each of the six applications.

Sign-in and credentials

The sign-in paths, the credentials a connection holds, and how long each one lasts.