link-cli mcp doctor: 'StdioServerTransport is not a constructor' — MCP server fails to start

[AndrewAcomb]

Summary

@stripe/link-cli@0.8.2 cannot start as an MCP stdio server. link-cli mcp doctor fails immediately:

ok: false
toolCount: 0
tools: []
warnings: []
errors[1]{code,message}:
  MCP_SERVER_FAILED,StdioServerTransport is not a constructor

This blocks any MCP-based integration of link-cli, including the recommended setup path:

link-cli mcp add --agent claude-code

The MCP server registers in the agent's config but fails to start at session boot.

Reproduction

npx --yes @stripe/link-cli mcp doctor

Expected

ok: true with the tools enumerated (auth/login, spend-request/*, mpp/pay, etc.).

Likely cause

StdioServerTransport is not a constructor typically means the import is hitting an object-shaped re-export rather than the class constructor. Most commonly this happens after an @modelcontextprotocol/sdk major-version bump that changes between default and named exports — the published dist/ may have been built against an older SDK shape.

A quick check of dist/ for how StdioServerTransport is imported (and a rebuild against the current @modelcontextprotocol/sdk) should resolve it.

Environment

• @stripe/link-cli 0.8.2
• node v22.22.0
• macOS arm64

Scope

Isolated to the MCP transport. All other CLI subcommands work fine in this same install:

• auth login / auth status — succeeds
• spend-request create / request-approval / retrieve — succeeds
• mpp pay (with an approved spend request) — succeeds end-to-end against a real merchant

Only the mcp doctor / mcp add path is broken.

[myjorneyflies-spec]

Map

[myjorneyflies-spec]

Authorize

[Kiog-Aser]

Most MCP transport errors like this come down to version drift in the SDK. If a rebuild against the latest @modelcontextprotocol/sdk doesn't fix it, check the ESM/CJS dance between the CLI and the server. Nice work on link-cli. Getting Stripe tools into the MCP ecosystem is a huge win.

[levon-stripe]

Thank you for alerting us to this issue, I'm able to reproduce it. Our team will investigate and update you once it's fixed.

[myjorneyflies-spec]

The server I used is to help you to see the issue. As there were several instances of suppository on same thing.

[sylwang-stripe]

Thanks for reporting this. I tried to reproduce the issue within the same environment but mcp doctor completed successfully and listed the available tools. Could you try the latest release (0.10.0) and let us know whether the issue still occurs?