u/Desperate_Hat_9561

https://reddit.com/link/1t0xr5g/video/pwm2mbnqujyg1/player

Hey folks, Prathmesh from MCPJam here.

In my last few posts, I've been showing coding agent workflows using the MCPJam's CLI to e.g. find and fix OAuth client registration issues.

Here’s that same workflow using MCPJam’s OAuth Debugger in our Inspector: every step of the MCP OAuth flow is logged, tied back to the spec, explained, and sequenced in the UI. When something fails, you can see exactly which part of the flow broke.

In this example, the server fails for dynamic client registration. MCPJam surfaces the raw error, points to the failed OAuth step, and lets you rerun the flow until the server connects.

You can test your server against every protocol version across all client registration methods.

This was my personal favorite feature when it dropped in October, back when I was the technical champion for MCPJam at Asana. Check it out here.

Connect, audit client registration, debug, run conformance

Hey folks, Prathmesh from MCPJam.

Sharing a CLI workflow that I think MCP server authors will find useful: a coding agent driving mcpjam end-to-end on your MCP server.

The agent connects, runs OAuth handshakes, hits a client registration error, proposes a fix from the structured output, and re-runs against our protocol and OAuth conformance suites.

Along the way, no tokens were exchanged with the agent directly. Our CLI writes a credentials file (0600, secrets redacted from stdout) so the agent can chain follow-up commands without you pasting an access token into a prompt. Our CLI also supports credentials files.

CLI install commands here.

Give it a whirl and do let us know if you have feedback.

https://reddit.com/link/1sz5ior/video/2ydt352lz5yg1/player

Hey folks, Prathmesh here from MCPJam with a CLI use-case.

Show coding agents your MCP Apps UI with:

mcpjam tools call --ui

As you folks know: coding agents are good at reading JSON. But, MCP Apps also expose interfaces that end-users can actually see and interact with.

With MCPJam Inspector, an agent can call a tool and see the returned UI rendered live, right in the Inspector. That means it can validate the actual end-user experience.

Try it out with the CLI.

https://reddit.com/link/1sybvt7/video/qgu8jtzphzxg1/player

Hey folks, Prathmesh here from MCPJam.

We released CLI v2.0 and you can use it to inspect your MCP servers today with one command: mcpjam 

Our new MCPJam CLI brings the core Inspector workflows you're used to to your terminal: connect to servers, call tools, debug OAuth, and run protocol conformance.

It also lets your coding agent debug MCP Apps by rendering tool results in the MCPJam UI.
 
Our skill will also let your coding agent dive deeper and y'all can get jamming here:
https://docs.mcpjam.com/cli/overview

npm i -g @mcpjam/cli

Give it a spin, looking forward to feedback from you MCP server authors & devs 🙏🏽