Tigris
Day 3 after signup
MCP
MCP auth got simpler, and you may need to re-authenticate.
Why it works
- Lead with the most significant change, then explain its practical impact on both the company and the reader.
- Keep smaller fixes in a compact roundup so the email shares useful detail without turning into a full release note.
- Use a direct link for deeper technical context and a personal sign-off to make a product update feel approachable.
How it is built
- Authentication change
- User impact explanation
- Blog post link
- Quick fixes roundup
Email copy
MCP auth went from effectively “figure it out yourself” to OAuth 2 Client ID Metadata documents. When you’re making an MCP server, it means no more having to clickops your way through getting secrets or figure out if you can support dynamic client registration. For us, it means we don’t have to run our own OIDC server anymore, so we replaced it with a thin frontend for Auth0. For you, it means you might need to re-authenticate. It’s much simpler, and feels more how auth should work. Read the blog post Now for the quick fixes: CopyObject and CompleteMultipartUpload calls now populate the version ID field on versioned and snapshottable buckets. Changing an object’s tags no longer resets the Last-Modified date, matching AWS S3 behavior. Fixed intermittent SignatureDoesNotMatch errors on uploads under 64 KiB using the AWS CLI and SDK. Shadow bucket migration from Cloudflare R2 now works on buckets with per-object ACLs, and conditional PUTs are honored on migration buckets. These updates and more on the Changelog. Sincerely, Ovais Tariq Co-founder and CEO, Tigris Data You are receiving this email because you opted in to receive updates from Tigris Data Tigris Data, 1250 Borregas Ave, Sunnyvale, CA 94089, USA Unsubscribe