Skip to main content
Coffee Chats is an AI networking platform that helps students reach alumni and professionals with personalized outreach and turn conversations into career opportunities. These docs cover the Chrome extension, applying to jobs, plans and Coffee Credits, and Coffee Chats MCP, which the rest of this page introduces.

Coffee Chats MCP

MCP stands for Model Context Protocol. It is an open standard that lets one program ask another service to run a single named action, such as reading your contacts. Each named action is called a tool. Coffee Chats MCP lets a program such as Claude call those tools on your Coffee Chats account for you, and that program is called an agent. This page defines the words the rest of the documentation uses, gives the addresses you need, and points you at the page that answers your question. After reading it you will know what a connection is, what it can reach, and where to start. A connection carries only the permissions you granted. You can end a connection at any time.
Across the whole tool catalogue, three tools send an email and three tools spend credits. One sends a thank-you message you already drafted, to the address stored on the contact linked to that meeting, and only after you read the exact message in your browser and approve it. One sends one outreach draft you already wrote. One queues a table of drafts for contacts you already have, after each row is checked. An agent cannot invent a recipient. One tool that spends credits starts research on your contacts, and only after you approve the batch, its cost and your balance in your browser. The other two write a resume, or a tailored resume and cover letter, and use credits as soon as the agent calls them, under their own permission.
The quickstart has the setup steps. Six applications can connect: Claude on the web and Claude Desktop, the Claude Code command-line tool, ChatGPT, the Codex command-line tool, Cursor web agents and the Cursor desktop app. The compatibility page lists each one with the client identifier it uses.

The words this documentation uses

The same word means the same thing on every page.

Service endpoints

You use the first two addresses yourself. Your agent host reads the last two on its own when it signs you in, and you never have to open them. The last two addresses hold configuration that your agent host reads automatically during sign-in. They contain no account data, and you do not need to understand them to use the connector. Give the connector address to your agent host. Open the connections page yourself to see what is connected and to end a connection.

What reading this documentation does

Reading these pages installs nothing. It does not start sign-in, and it does not grant an agent anything on your behalf. Only the Authorize access page does that, and only after you sign in to Coffee Chats yourself.

Next steps

Connect an agent

Add the connector, sign in, choose what to share, and make a first call.

What an agent can do

What the tools reach, and the parts of Coffee Chats no tool reaches.

Permissions

How the Authorize access page works, and what each permission buys.

Tool reference

Every tool, generated from the connector’s own catalogue.