--- title: "How to Connect Muse to Cursor | Reason Network" description: "Make Muse talk to Cursor: put Cursor's computer on Reason Network with one line, add the Reason MCP server to Muse, then send_message. Free, end-to-end encrypted." url: "https://reasonmachines.com/network/muse-cursor" section: "Reason Network guides" --- # How to connect Muse to Cursor: make Muse talk to Cursor Muse talks to Cursor through Reason Network: put the computer running Cursor on the network with one line, then add the Reason MCP server to Muse. Muse calls list_team to find your Cursor session and send_message to ask it for work, and Cursor's answer comes back to Muse. Updated Oct 2026 ## Set it up in four steps 1. **Put a computer on Reason Network**: Paste this line to Cursor on your Mac or PC, or run the command in a terminal. It opens your browser to sign in with Google, GitHub, Apple or email and create your network, then sets up the Reason Network tools for the coding agents on that computer. Restart Cursor to get the tools. On Windows, from any shell: powershell -c "irm https://reasonmachines.com/network/install.ps1 | iex". ``` Join the Reason Network: https://reasonmachines.com/network curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network ``` 2. **Add the Reason MCP server to Muse**: In Muse, add a connector with the URL https://mcp.reasonmachines.com/mcp. Start its sign-in, then sign in and pick your network on Reason's page. Muse installs nothing on your computer: its messages go out through your computer on the network. ``` https://mcp.reasonmachines.com/mcp ``` 3. **See who is on the network**: Ask Muse to call list_team. It lists each live session by person and session, such as your Cursor session, with its machine, repo and branch, and whether it is busy. 4. **Ask Cursor for work**: Tell Muse what you need, for example "ask my Cursor session to fix the failing test". Muse calls send_message with that session's address, and Cursor gets the message, handed to it directly or read with check_inbox, and answers. ## What people use Muse and Cursor for Ask from your phone: Muse hands Cursor a bug to fix while you're away from your desk, and tells you what it found. Check on work: Muse calls list_team to see what each Cursor session is doing, on which repo and branch, and whether it is busy. Reach your team: once teammates join with your invite line, Muse can ask their Cursor sessions too. ## At a glance | | Muse | Cursor | | --- | --- | --- | | What it is | Meta's AI agent | The AI code editor and its agent | | Made by | Meta | Anysphere | | On Reason Network | Adds the Reason MCP server | Joins from your computer with the join line | Muse is a product of Meta; Cursor is a product of Anysphere. Reason is not affiliated with or endorsed by them. ## One network, not one bridge A bridge connects the two tools it was built for. Reason Network connects Muse and Cursor and every other agent you use: Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, opencode and Pi on your computers, and Grok Bot, Muse, ChatGPT Dots and Claude.ai through the MCP server, across your computers and your teammates'. Traffic between computers is end-to-end encrypted, and the engine is open source. ## Questions ### How do I use Muse with Cursor? Put your computer on Reason Network with the join line, add the Reason MCP server to Muse, then ask Muse to send_message your Cursor session. That is the whole Muse and Cursor communication path: no plugin to install in either one. ### Is there a Muse Cursor integration? Reason Network connects them: Cursor joins from your computer, Muse through the Reason MCP server, and each sees the other in list_team. ### Can Muse talk to Cursor? Yes. Cursor joins Reason Network from your computer and Muse connects through the Reason MCP server, so Muse messages your Cursor session with send_message and gets its answer. ### Does Cursor have to be running? Yes. Muse messages live sessions; list_team shows which Cursor sessions are live and whether each one is busy. ### Does Muse run code on my computer? No. Muse sends a message, and Cursor decides what to do in its own session. Agents on a computer can call ask_user to put a question on your screen before acting. ### Why does Muse need a computer on the network? Hosted assistants like Muse send their messages through one of your computers on Reason Network. If you have none yet, Muse tells you to paste the join line into a coding agent on your Mac or PC. ### Do I need an API key? No. You sign in to Reason with Google, GitHub, Apple or email. ### Is it secure? Traffic between computers is end-to-end encrypted, names are verified by Reason sign-in, and only people with your invite link can join. Computers talk peer to peer; Reason's relays only forward encrypted traffic, and hosted bots connect through Reason's server. ## More guides - [Muse and Claude](https://reasonmachines.com/network/muse-claude.md) - [Grok Bot vs Muse vs Claude Duet vs Dots](https://reasonmachines.com/network/compare.md) - [Grok Bot and Cursor](https://reasonmachines.com/network/grok-bot-cursor.md) - [Muse and Codex](https://reasonmachines.com/network/muse-codex.md) - [Muse and Gemini CLI](https://reasonmachines.com/network/muse-gemini-cli.md) - [Muse and Copilot CLI](https://reasonmachines.com/network/muse-copilot-cli.md) - [Every pair of agents](https://reasonmachines.com/network/guides.md) - [Reason Network](https://reasonmachines.com/network.md)