What's new
What we have shipped in MCP Studio, newest first. Bug fixes and small polish are left out — this is the list worth reading if you have been away for a month.
Looking for how something works? Read the documentation. Building on the MCP Studio SDK? That has its own list.
September 2026
4 updates- New feature
Upload files from your computer as a source
Not everything worth giving an agent has a URL. Upload a spreadsheet, Word document, PowerPoint deck, PDF, text or HTML file, or an image, and MCP Studio reads the text out of it and indexes it like any other source. Zip several together and the archive counts as one source. Extraction happens while you watch, so a file that cannot be read fails next to the file picker rather than as a job that failed quietly. A workbook is cited per sheet, a deck per slide, and a PDF per page, and every citation links to the text that was extracted. Images are transcribed by a vision model and labelled as such wherever they are quoted. Only the extracted text is stored — the file itself is discarded — and a server built on an upload starts out private.
Upload files as a source - Security
Terms of Service, accepted at sign-up
MCP Studio now has published terms, and accepting them is part of creating an account rather than something buried in a footer: the sign-in page asks you to confirm you have read them before it will hand you to GitHub or Google. Each version carries a date, so a change of substance asks existing accounts to accept again on their next sign-in instead of applying silently. The n8n node has its own terms covering what is specific to running inside n8n, and its credential form will not save until they are accepted.
Read the Terms of Service - New feature
Connect another MCP server, with or without an API key
Paste an MCP endpoint — a published GitBook site at /~gitbook/mcp, for example — and MCP Studio asks whether it needs authentication, connects, and shows you the tools it offers before you add it. Public servers work as they are; for one that needs a key, paste the key and MCP Studio authenticates for you and stores it encrypted. Questions are then forwarded to that server live, so its answers are always current. If the URL turns out not to be an endpoint you are offered to add it as a website instead, if a server needs details a search cannot supply you are told before adding it, and a server that stops answering says so on the dashboard rather than sitting there looking healthy.
Connect another MCP server - New feature
Build your own MCP tool
Describe a tool in your own words and MCP Studio builds it against your sources. Useful when your team keeps asking one question that none of the ten built-in tools targets well — "what changed between these two releases and what do I have to rewrite?" The tool appears in the wizard, deploys with your server, and any MCP client can call it. Five custom tools per account.
Build your own tool
August 2026
16 updates- Security
Private MCP servers and access tokens
Make a server private and it requires a token on every request — including the handshake and the tool list, since tool names describe what your content is about. Create and revoke per-server tokens from the dashboard. Adding a private GitHub repo now switches the server to private automatically instead of trusting the browser to say so.
Authenticate to a private server - Security
Disconnecting a source really deletes its content
Removing a source now clears everything derived from it, including cached search results and the stored passages in your request log. Previously the index was deleted while the text stayed readable through analytics and returnable from cache for a few minutes — which is not what "disconnect" implies, least of all for a private repo.
Managing sources - Security
A defined retention period for request telemetry
Query text and stored passages are scrubbed after 90 days on the free tier, and request rows are deleted at 395 days. Content is dropped before the row is, so your usage history and KPI charts survive even after the text behind them is gone.
Dashboard and telemetry - Security
Sign-in no longer asks for your private repositories
Signing in with GitHub now requests only your identity. Repository access is requested at the moment you paste a private repo URL, rather than being handed over by everyone at sign-up. Accounts are also never linked automatically by email address.
Creating an account - Plans & billing
Subscription lifecycle, missed payments, and automatic downgrades
Stripe is now the source of truth for what you have access to, rebuilt from webhook events rather than written once at checkout. A failed payment keeps your access while Stripe retries; we send a warning on day 12 and downgrade to Free on day 14. A downgrade removes paid capability and never deletes your servers, sources, or analytics history.
Billing and plans - Plans & billing
Deleting your account cancels billing for you
Requesting deletion cancels every live subscription immediately, and the account is not removed until billing has actually stopped. There is no longer any need to cancel a subscription first.
Billing and plans - Integration
AI Context by MCP Studio for n8n
A community node that gives n8n workflows grounded answers from your MCP servers. Pick a server from a list, query it, manage which tools are enabled, and read free-tier metrics — all inside a workflow. Published on npm as n8n-nodes-mcp-studio and installable from n8n's community nodes panel.
n8n integration guide - New feature
API keys scoped to specific servers
Account API keys can be limited to named MCP servers, so a key handed to an integration or a script cannot reach the rest of your account. Revoked keys can now be deleted rather than lingering in the list.
Managing your account - Analytics
Full request log history and clearer breakdowns
The request log shows your whole history rather than a recent window, paged twenty rows at a time, with filters by tool and client. Tool, source, and client breakdowns returned to donut charts with a hover readout, and CSV export.
Dashboard guide - New feature
API access for partner integrations
Create API keys to drive MCP Studio programmatically — create servers, manage sources and tools, and read metrics. This is what platform integrations are built on, and it is available to any account.
API reference - Plans & billing
30-day analytics trial and usage-based overage
New accounts get every analytics tier free for 30 days, plus five sources for life on their first MCP server. You can also opt into usage-based billing so requests beyond your plan are metered through Stripe instead of being refused.
Trials and overage - Analytics
Action and Predictive analytics
Two tiers beyond the free charts. Action shows the exact passage returned for each request, code snippet provenance, retrieval confidence per page, content gaps, and an impact model with a visible formula. Predictive groups question chains to show how many requests it took to reach a working answer, grades your sources A–D, and ranks the content fixes worth making.
Action and Predictive guide - New feature
Version-aware answers
Retrieval now carries which version of your documentation a passage came from, and labels it as current or version-pinned when handing it to an AI client. Agents are told to prefer current docs for things like minimum requirements and command syntax, which is where stale version-pinned pages caused confident wrong answers.
How indexing works - New feature
Durable indexing queue
Indexing became a real job queue instead of work done inside a request, so a large site keeps making progress rather than timing out. Per-source progress is visible on the dashboard, and sources that fail report why and how to fix it.
How indexing works - New feature
Full GitHub repository indexing
Repository sources index the whole text and code of a repo rather than just its documentation files, which makes code-shaped questions answerable from the repo itself. Private repositories are supported after connecting GitHub.
Adding sources - New feature
Restore a deleted MCP server
Deleting a server stops it answering immediately but keeps it restorable for seven days, so an accident is recoverable. Its indexed content is released right away and re-indexed on restore.
Dashboard guide
Build something with your own context
Paste a documentation URL, a GitHub repo, or a website, pick your tools, and get a live MCP endpoint your AI assistant can query.
Build an MCP server