[BUG] Remote Control: MCP tool permission prompts do not propagate to mobile app — session silently stalls
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When using Claude Code via Remote Control (/rc) from the Claude mobile app (iOS), MCP tool permission prompts — specifically for integrations like Linear and Jira/Atlassian — do not appear in the mobile interface. The session silently stalls with no indication that user input is required. The permission prompt is only visible in the local terminal.
This effectively makes MCP-heavy workflows unusable via Remote Control, since the user cannot approve tool calls without returning to the terminal.
What Should Happen?
The MCP tool permission prompt should be forwarded to and rendered in the Claude mobile app, allowing the user to approve or deny the tool call remotely — the same way file edit and bash command prompts are (partially) shown.
Error Messages/Logs
Steps to Reproduce
- Start Claude Code with MCP servers configured (e.g., Linear, Atlassian/Jira)
- Enable Remote Control via
/rcand connect from the Claude iOS app - From the mobile app, ask Claude to perform an MCP tool action that requires permission — e.g., "Create a Linear issue titled 'Test issue' in team Company"
- Claude Code invokes the MCP tool (e.g.,
Linear - save_issue(...)) and displays the permission prompt in the terminal only:
```
Tool use
claude.ai Linear - save_issue(title: "Test issue", team: "Company", ...)
Do you want to proceed?
❯ 1. Yes
- Yes, and don't ask again for claude.ai Linear - save_issue commands in /workspaces/project
- No
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.87
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗