dend

8 ms·

1.
by dend 2mo ago
We are actively working on this - the support is rolling out across the ecosystem: https://claude.com/blog/bringing-mcp-2026-07-28-to-claude
2.
by dend 2mo ago
This protocol change doesn't require you to do anything to existing running MCP code - only if you want to take advantage of new capabilities!
3.
by dend 2mo ago
Hey folks - one of the Lead Maintainers for MCP. Happy that we got this release out the door today, this is an exciting change for those that wanted to roll out remove MCP servers into serverless hosts. There is, of course, more good stuff
4.
by dend 3mo ago
Depending on the setup, you just have to be really careful to avoid confused deputy scenarios. I wrote about it: https://den.dev/blog/mcp-confused-deputy-api-management/
5.
by dend 3mo ago
Was great collaborating with you and your team on this!
6.
by dend 3mo ago
There's theoretically nothing really stopping this integration from working in the consumer space - you just need to establish a trust relationship (e.g., if I am logged in with GitHub, also log me in to Sentry automatically). There is
7.
by dend 3mo ago
We are in touch with the Microsoft Entra ID folks to see how we can better integrate EMA in their stack!
8.
by dend 3mo ago
It is available! The feature is available in Claude, with Okta being the first IdP to support it (hopefully more coming soon) and with a bunch of MCP partners launching with us today. The underlying extension has been in the MCP protocol fo
9.
by dend 3mo ago
You don't actually need to ask me for that - a lot of the data is very public, and we've been on a roll announcing MCP partnerships, and developer adoption keeps going up. There is always room to make the protocol better, but it c
10.
by dend 3mo ago
Hey - one of the lead maintainers of the MCP project here. There are a lot of scenarios where this simply won't scale (both from a usability and security standpoint). Cookies were made for the browser. MCP servers and clients often ope
11.
by dend 3mo ago
The standard itself is not MCP-specific. As long as the client and the server adopt ID-JAG, they're golden. RFC draft: https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-a...
12.
by dend 3mo ago
FWIW, we never vibe-coded the spec to begin with, but yes - auth is a continuous learning process, and we're lucky to collaborate with some really talented folks both inside and outside the company (e.g., this launch we worked closely
13.
by dend 3mo ago
Love more adoption of EMA and, of course, better infra for MCP developers. Thanks for such a quick turnaround on this feature work!
14.
by dend 3mo ago
We're always looking at making it a smoother experience - it's a top pain point for developers and IT admins alike. If you have feedback - feel free to send it my way!
15.
by dend 3mo ago
What's interesting about this standard is that it's not really MCP-specific. It can work just as nicely for any other workload - it just requires the authorization server/IdP to support it and the receiver to know how to hand
16.
by dend 3mo ago
Hey folks - I am one of the folks at Anthropic that helped deliver this in partnership with Okta and a handful of MCP partners. We're very excited about this taking shape in Claude (in addition to the MCP spec, of course, where EMA is
17.
by dend 6mo ago
More of the latter than the former. The protocol itself is constrained to a set of well-defined primitives, but clients can do a bunch of pre-processing before invoking any of them.
18.
by dend 6mo ago
One of the MCP Core Maintainers here, so take this with a boulder of salt if you're skeptical of my biases. The debate around "MCP vs. CLI" is somewhat pointless to me personally. Use whatever gets the job done. MCP is much m
19.
MCP Apps – UI and Interactivity for MCP(blog.modelcontextprotocol.io)
6 points by dend 8mo ago|0 comments
20.
Whorl – Use Mentions in Thunderbird(github.com)
2 points by dend 8mo ago|0 comments
21.
Model Context Protocol Wrapped(2025.mcpwrapped.den.dev)
1 points by dend 9mo ago|0 comments
22.
Model Context Protocol turns one, releases new spec version(blog.modelcontextprotocol.io)
7 points by dend 10mo ago|0 comments
23.
You need to become a full stack person(den.dev)
2 points by dend 10mo ago|0 comments
24.
by dend 1y ago
Core contributor behind this project. If folks have any feedback, we're all ears!
25.
by dend 1y ago
One of the MCP Core Maintainers here. I want to emphasize that "If you see something, say something" very much works with the MCP community - we've recently standardized on the Spec Enhancement Proposal (SEP) process, and are
26.
A New Governance Model for MCP(blog.modelcontextprotocol.io)
2 points by dend 1y ago|0 comments
27.
by dend 1y ago
The analogy that was used a lot is that it's essentially USB-C for your data being connected to LLMs. You don't need to fight 4,532,529 standards - there is one (yes, I am familiar with the XKCD comic). As long as your client is M
28.
by dend 1y ago
I am just glad that we now have a simple path to authorized MCP servers. Massive shout-out to the MCP community and folks at Anthropic for corralling all the changes here.
29.
by dend 1y ago
But where would you get bearer tokens? How would you manage consent and scopes? What about revocation? OAuth is essentially the "engine" that gives you the bearer tokens you need for authorization.
30.
by dend 1y ago
Can only speak for the authorization spec, where I am actively participating - zero. The entire spec was written, reviewed, re-written, and edited by real people, with real security backgrounds, without leaning into LLM-based generation.

More ›