MCP 연결에서 CLI 연동으로 이전하기
The Reki note MCP connection is scheduled for retirement. It still works during the migration window, but new integrations should use the CLI approach. This page explains the reasoning and the steps.
Last updated: September 30, 2026
Where MCP stands now
Section titled “Where MCP stands now”The MCP connection lets AI clients on this computer read meeting data (transcripts, minutes, tasks) and create, update, or delete tasks. Communication stays on this computer.
It is scheduled for retirement. It still works during the migration window, but plan to move to the CLI integration.
How the CLI integration differs
Section titled “How the CLI integration differs”The CLI integration uses the /reki-note command from Claude Code, Codex, and Cursor to review minutes and add tasks. You do not manage a connection URL or port as with MCP.
Even if you used the MCP connection, you can set up the CLI with one click from “Connect to AI agents via CLI”.
Migration steps
Section titled “Migration steps”Set up the new integration on the CLI side. You do not need to remove the MCP setup; they can coexist during the migration window.
Example prompt to verify the connection:
/reki-note what did we decide in yesterday's meeting?- Open Settings > AI > Connect to AI agents via CLI.
- Press “Set up CLI” to configure Claude Code, Codex, and Cursor together.
- Ask your AI client “/reki-note what did we decide in yesterday’s meeting?” to verify it works.
- Remove the MCP connection settings when you no longer need them.
Learn more
Section titled “Learn more”For details on the CLI integration and cloud MCP, see the “Work with AI agents” article.