Two updates shipped in August. Here's what changed.
TL;DR: August 2026 Update
- Personal Credentials — Invite users to your servers and let them connect with their own credentials. Their permissions on every integration stay intact — no unintended access, no matter what tools are on the server.
- Performance Improvements — Under-the-hood fixes for a faster, more reliable experience across the board.
✨ What's New 🚀
Personal Credentials: Every Action Under the Right Account
July brought Access Management — the ability to invite members to your MCP Express workspace. August makes that invitation smarter.
Here's the problem it solves. When you invite a user to one of your MCP servers, they connect using your credentials by default. That means they don't just get access to your tools — they inherit your permissions on every integration behind them.
Say you're an admin on a database with full read and write access, including deletion. You invite a team member who, in that database, only has read access. No deletion rights. But on your MCP server, they're running under your credentials — so when they use the database tool, they can delete. The restriction that existed in the database doesn't apply anymore, because they're not acting as themselves.
Personal Credentials fixes this at the source. Enable the option when inviting, and the user connects to the server using their own credentials. They bring their own Slack account, their own database user, their own GA4 access. The tools on the server stay the same — but what each person can actually do with them is determined by their own permissions, not yours.
A few scenarios where this matters:
Database with role-based access. A junior team member has read-only access to your database. With Personal Credentials enabled, they join the MCP server under their own credentials — and even though the delete tool is right there on the server, they can't execute it. Their database role enforces the limit.
Slack with restricted channels. A contractor is only supposed to access certain Slack channels. Under your credentials, those restrictions disappear. Under their own, they're scoped exactly as their Slack account allows.
GitHub with branch protection. A team member can't push directly to main in GitHub. With Personal Credentials enabled, that protection holds on the MCP server too — their GitHub permissions travel with them.
Enable the option when inviting — and the permissions that exist outside MCP Express stay intact inside it.
This month also included a round of under-the-hood improvements — faster response times and reliability fixes across the platform. Nothing to configure on your end, just a smoother experience overall.
✨ What's Next For September 🚀
Coming in September: Publicly Accessible MCP Servers
In September, we're planning to ship publicly accessible MCP servers.
Once you make a server public, you get a URL. Anyone with that URL can paste it directly into Claude or their AI client and start using the server — no MCP Express account, no OAuth, no setup on their end. You build the server once. Everyone else connects.
More details when it ships.
Try It
Both updates are live. Head to your server settings to start using Personal Credentials when inviting members.
New here? Start free — no credit card required.
Tell us what to build next We're adding integrations every month based on what people actually need. If there's a tool you rely on that isn't here yet,
drop us a line.
