Compatibility answer · checked 2026-07-16

Does VS Code work with Stripe MCP?

Conditional. The connection requirements intersect, with the listed availability or setup conditions. This is a reviewed requirements comparison, not a live integration, uptime, or security test.

Read the JSON receipt Compare all 90 pairs Follow this pair in RSS

Compatibility receipt

What the evidence supports

Direct means an official source names the pairing. Inferred means compatible documented requirements intersect, while every remaining condition stays visible.

Conditional

Current verdict

The connection requirements intersect, with the listed availability or setup conditions.

inferred

Evidence level

The documented transport and authentication requirements intersect, but the provider does not explicitly name the pairing.

2026-07-16

Oldest required review

This is the older of the client and tool reviews, not a live test. Client reviewed 2026-07-16; tool reviewed 2026-10-02. Check the linked guidance before use.

Portable compatibility receipt

Embed this badge

Copy the Markdown below into a repository or document. The image reflects this reviewed catalog result and links back to the dated compatibility receipt.

markdown · /badges/compatibility/vs-code/stripe.svg

[![VS Code ↔ Stripe MCP · Conditional · checked 2026-07-16](https://resolvemesh.com/badges/compatibility/vs-code/stripe.svg)](https://resolvemesh.com/compatibility/vs-code/stripe)

Requirements match

Transport, authentication, and remaining gates

The intersections below are computed from the reviewed client and tool profiles. Empty intersections remain explicit.

STREAMABLE_HTTP

Matched transport

Client supports STREAMABLE_HTTP · STDIO. Tool requires STREAMABLE_HTTP.

OAUTH_2_0 · BEARER_TOKEN

Matched authentication

Client supports OAUTH_2_1 · OAUTH_2_0 · BEARER_TOKEN · NONE. Tool requires OAUTH_2_0 · BEARER_TOKEN.

3 visible

Conditions and caveats

Stripe administrators must enable MCP access separately for sandbox and live environments.
From October 31, 2026, Stripe MCP rejects full-access secret keys and restricted keys without the Agent tag; migrate to Agent Keys or OAuth. Keep human confirmation enabled.
Connected-account access requires a Stripe-Account header and is not available through OAuth.

Reviewed profiles

VS Code and Stripe MCP

ResolveMesh compares the documented connection surfaces. It never sends credentials to either provider from this page.

Client

VS Code

Editor MCP host for local commands and remote HTTP servers with user, workspace, and profile configuration.

Reviewed 2026-07-16.

Hosted tool

Stripe MCP

Stripe's hosted MCP server for authenticated Stripe API reads and writes.

Reviewed 2026-10-02.

https://mcp.stripe.com

Compatibility change radar

Reviewed changes affecting this pair

Approved events matching this pair include client-wide and tool-wide changes. RSS and JSON use the same reviewed ledger.

action required

Stripe MCP requires Agent Keys or OAuth by October 31

Starting October 31, 2026, Stripe MCP will reject full-access secret keys and restricted keys without the Agent tag with HTTP 401. OAuth remains available.

Read the approved change

GET /v1/compatibility-changes?client=vs-code&tool=stripe

Machine-readable change feed

Poll the filtered JSON feed for reviewed events affecting this exact pair.

Free · no account

Keep this pairing in your feed reader

Follow reviewed changes for this pair, including relevant client-wide and tool-wide events. An empty feed means no published match, not proof of no changes. Your reader polls the feed; this is not an instant alert or an email watch.

Subscribe to this pair’s RSS

Primary evidence