Release notes
What's new
Changes to the MCP Studio SDK, newest first. Bug fixes and small polish are left out — this is the list worth reading if you have been away for a month.
Changes to MCP Studio itself are tracked separately, on the MCP Studio what's new page.
September 2026
3 updates- New feature
A published Terms of Service, and accepting it is now part of signing in
The SDK now has a Terms of Service written for the developer embedding it rather than for an end user, covering your client credentials, what you owe the customers who create MCP servers inside your product, how the per-user server limit and the pooled request limit are counted, overage and its budget, and what happens to your end users' servers if you delete your account. Accepting it is required to sign in: there is a checkbox on the sign-in page, and we record which version you accepted and when. If you already have an account, you will be asked once at your next sign-in, and again only if we publish a materially new version. Your integration, your credentials, and your end users are unaffected either way.
Read the SDK Terms - Plans & billing
Pay past your plan limits instead of turning customers away
Your plan's server and request limits used to be hard stops: once your integration spent its monthly allowance, every end user was refused for the rest of the month and there was nothing you could do about it. You can now turn on usage beyond your plan in the Developer Portal — $0.10 per additional MCP request and $25 a month for each MCP server past one end user's allowance. A monthly budget is required rather than optional, and it is the most the overage can add to your bill. Available on Free as well as Pro, so needing more requests does not force an upgrade. Your end users never see anything about your budget or your bill.
Billing and subscriptions - Plans & billing
Server limits are counted per end user
The server limit used to be shared across your entire user base, so SDK Free allowed one server for everybody put together — you spent it testing and every real customer was turned away. Servers are now counted per end user: Free gives each person one, SDK Pro gives each person ten, and there is no cap on how many end users you have. MCP requests stay pooled across your whole integration, because that is the limit that reflects cost, and SDK Free now includes 1,000 of them a month.
SDK plan limits
August 2026
6 updates- New feature
See your usage before your customers hit a limit
The Developer Portal now shows how many MCP servers exist across your embed and how many requests your integration has served this month, against your plan's allowance. The person who hits a limit is an end user inside your product — someone who cannot see this portal and cannot do anything about it — so the point is that you see it coming rather than hearing about it from a customer.
SDK plan limits - Plans & billing
Subscription lifecycle, missed payments, and a billing portal
Stripe is now the source of truth for what you have access to, rebuilt from webhook events rather than recorded once at checkout — so renewals extend your plan and cancellations actually revoke it. A failed payment keeps your access while Stripe retries; we warn you on day 12 and downgrade on day 14. You can update a card, download invoices, or cancel yourself in Stripe's billing portal.
When a payment fails - Plans & billing
Deleting your developer account cancels billing for you
Requesting deletion cancels every live subscription immediately, and the account is not removed until billing has actually stopped. Deletion also revokes the analytics tier mirrored to your end users, so nothing keeps being granted by an account that no longer exists.
Deleting your account - Analytics
Grant analytics to your end users from one subscription
Subscribe once at the integration level and every end user who deploys a server through your embed receives that tier — they do not buy an MCP Studio analytics subscription separately. Choose which tier to grant in the configurator, and see the same depth in your own portal dashboard. Telemetry is captured on every request regardless of tier, so turning one on backfills the dashboard with history you already have.
Analytics and observability - Analytics
30-day trial with every analytics tier
New developers get Core, Action, and Predictive included for 30 days, with no card required. It is the whole dashboard rather than a sample of it, so you can decide what your customers actually need before paying for a tier.
What you can pay for - New feature
Interactive playground and sample apps
Try the real embedded wizard against your own credentials before writing any integration code, and change tools, sources, branding, and layout to see the effect immediately. The sample apps show the embed inside a realistic product shell rather than on a blank page.
Sample apps