Your Meeting Notes in Cursor, Windsurf and Codex

In Meetily Pro 1.11.0 or later, open Settings > PRO and turn on Integrations. In the new Integrations tab, click Connect next to Cursor and choose what it may do (new connections start read-only). Then turn on its Allow switch and restart Cursor so it loads the Meetily tools. Windsurf and Codex work the same way: each has its own Connect button when it is installed on the same computer, and Codex also needs its command-line tool installed.

Ask the editor’s assistant to work from what the meeting decided, for example:

• “Read Monday’s architecture review and list the API changes we agreed.”
• “Draft a migration plan from the decisions in yesterday’s sprint planning.”
• “Check this pull request against what the design review decided about error handling.”
• “Search last month’s meetings for everything said about the billing service.”

Meetily lists VS Code but cannot connect it from the app yet. You can still add the Meetily MCP server to VS Code, or to another MCP client, by hand: follow the up-to-date setup guide in the meetily-workflows repository. A client you set up by hand gets only the permissions of the key it uses.

The editor sees the meetings it reads when you ask, through the permissions you chose. Meetily serves them on your own computer; the editor then sends what it reads to its own AI provider along with the rest of your conversation. Connect the tools you already trust with your meeting notes. Transcription itself always runs locally.

Make sure the Automation API switch is on and the editor’s Allow switch is on in the Integrations tab, then restart the editor. After changing an editor’s permissions, restart it again so it picks them up. The built-in check, run in a terminal, confirms Meetily is reachable and your Pro license is active:

meetily-pro mcp doctor