[GH-ISSUE #127] MCP tools used inside Ralph don't recognize authorization #50

New issue

Closed

opened 2026-02-27 10:21:57 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 10:21:57 +03:00

Owner

Originally created by @XanderZhu on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/mikeyobrien/ralph-orchestrator/issues/127

I have Supabase MCP installed in my project to automatically apply DB migration to the Supabase project.
Supabase MCP authorized and work fine during plain Claude Code usage without Ralph Orchestrator.
But when I try to use Ralph Orchestrator I see in the iteration output that Supabase MCP is not authorized. Thus it can't be used.

Originally created by @XanderZhu on GitHub (Jan 28, 2026). Original GitHub issue: https://github.com/mikeyobrien/ralph-orchestrator/issues/127 I have Supabase MCP installed in my project to automatically apply DB migration to the Supabase project. Supabase MCP authorized and work fine during plain Claude Code usage without Ralph Orchestrator. But when I try to use Ralph Orchestrator I see in the iteration output that Supabase MCP is not authorized. Thus it can't be used.

kerem closed this issue

2026-02-27 10:21:57 +03:00

kerem commented

2026-02-27 10:21:58 +03:00

Author

Owner

@mikeyobrien commented on GitHub (Jan 28, 2026):

Odd, Claude should be running with --dangerously-skip-permissions.

Could you try adding this to your ralph.yml:

cli:
  backed: claude
  args: ["--dangerously-skip-permissions"]

@mikeyobrien commented on GitHub (Jan 28, 2026): Odd, Claude should be running with `--dangerously-skip-permissions`. Could you try adding this to your `ralph.yml`: ``` cli: backed: claude args: ["--dangerously-skip-permissions"] ```