MCPorter 0.9.0 brings TypeScript, CLI, and sturdier shutdowns

Peter Steinberger has just rolled out MCPorter 0.9.0, adding easier MCP calling via TypeScript or a CLI. The update also delivers per-server tool filtering, improved stdio shutdowns, a Windows OAuth quoting fix, and clearer OAuth docs.

tool cover

TL;DR

  • Peter Steinberger announced MCPorter 0.9.0, focused on easier MCP calls from TypeScript or CLI
  • Per-server tool filtering: New control for limiting available tools per server; widely praised in replies
  • Reliability updates: Sturdier stdio shutdowns and Windows OAuth URL quoting fix for real-world failures
  • Tool call behavior: Schema-declared string coercion added for tool calls
  • Documentation updates: OAuth config docs included alongside other documentation updates

Peter Steinberger has announced MCPorter 0.9.0, a new release aimed at making it easier to call MCPs from either TypeScript or a CLI. The update bundles a handful of practical fixes and quality-of-life improvements that, judging by the replies, target the kinds of failures that show up once tooling moves beyond demos.

Steinberger’s post points to new functionality and several reliability-focused changes, alongside updated documentation.

What’s new in MCPorter 0.9.0

According to the announcement, MCPorter 0.9.0 includes:

  • Calling MCPs from TypeScript or as a CLI
  • Per-server tool filtering
  • Sturdier stdio shutdowns
  • A Windows OAuth URL quoting fix
  • OAuth config docs
  • Schema-declared string coercion for tool calls

The release link shared in the post is https://t.co/aywv0xs0Hf.

Early reactions: tool filtering and shutdown behavior stand out

Among the replies, per-server tool filtering is the most consistently praised addition. One developer called it “the piece I’ve been waiting for,” while another noted that filtering is “underrated” because “things get messy fast without it.”

Reliability work also got a callout. “Sturdy shutdowns finally, devs been waiting,” one reply said, and another commenter highlighted the pairing of “sturdier stdio shutdowns” with the Windows OAuth quoting fix as a sign the release focuses on “annoying real world failures.”

Light analysis: the unglamorous work that makes tooling stick

A few commenters implicitly point at the same underlying dynamic: MCP tooling is becoming more infrastructure-like, and infrastructure lives or dies on predictability. It’s telling that the headline items here aren’t new connectors or flashy capabilities, but filtering, shutdown behavior, and Windows quoting—small details that tend to surface only when real-world workflows start piling up.

Not everyone is convinced, though. One reply jokes that MCPorter is “another abstraction layer to debug when everything breaks,” which is a familiar critique for any tool that sits between apps and the systems they orchestrate.

Source: https://x.com/steipete/status/2046192869497622529

Continue the conversation on Slack

Did this article spark your interest? Join our community of experts and enthusiasts to dive deeper, ask questions, and share your ideas.

Join our community