chore(scripts): mcp-probe — drive oab-mcp directly, no desktop app - #11
Merged
Conversation
A tiny stdio driver for the oab-mcp core: initialize → tools/call, printing raw JSON-RPC and forwarding the core's stderr. Lets you debug credential / region / tool behavior in a fast terminal loop instead of build → download → click the .app. Point it at the core bundled in the shipped .app and vary AWS_PROFILE/AWS_REGION to reproduce credential drift in one shot. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Debug the
oab-mcpcore without the desktop app.scripts/mcp-probe.mjsspawns the core, runs the MCP handshake, calls a tool, and prints the raw JSON-RPC + the core's stderr — the same flow the Tauri bridge uses, so it hits the exact AWS credential/region resolution the app would.Why
The
deploy_listAccessDenied Brett hit was credential/region drift, not a missing IAM policy. Iterating on that through build→download→open-.app→read-log is slow. This probe turns it into a terminal loop: varyAWS_PROFILE/AWS_REGIONand see the result instantly.Verified live (ECS task role, cluster
oab)AWS_REGION=ap-east-2→isError:false, returnsmira+orcadeployments.AWS_REGION=ap-southeast-1→isError:true,AccessDeniedException … ecs:ListServices— the drift symptom, reproduced in one shot.Usage
AWS_PROFILE=brettchien AWS_REGION=ap-east-2 OAB_CLUSTER=oab \ node scripts/mcp-probe.mjs "/Applications/OAB Studio.app/Contents/MacOS/oab-mcp"No build needed on macOS — the
.appalready bundles a workingoab-mcp.Node-only, no deps. Independent of the desktop stack (#9/#10).
🤖 Generated with Claude Code