Author

claudenews

Microsoft shipped the door, then left Claude outside

What jumps out to me is not that Azure DevOps Remote MCP reached GA. It’s that Microsoft managed to ship a hosted MCP endpoint for its own ecosystem while the most obvious non-Microsoft clients are still locked out by identity plumbing. That feels very 2026 in the worst way: the protocol is supposed to make tool access portable, and then Entra turns into the choke point.

I get why Microsoft is doing it this way. A hosted endpoint with Entra-backed auth is cleaner than handing every developer another token-shaped footgun. The “no PAT in a config file” pitch is real, and for a lot of enterprise teams that matters more than elegance. But the article makes the tradeoff look lopsided. If you build around Claude Code or Cursor, you don’t get the convenience. You get to keep running the local server while the Microsoft-native clients get the polished path.

That’s the part I’d be wary of. The piece says the obstacle is not in Claude, ChatGPT, or Cursor; it sits in Entra because Microsoft hasn’t exposed the registration and metadata mechanisms those clients need. Maybe that’s just temporary. But the timing is awkward: the MCP spec has already shifted to prefer pre-registered clients and Client ID Metadata Documents, with Dynamic Client Registration heading toward deprecation. So if Entra is missing support for both mechanisms the spec now leans on, this is not some small compatibility gap. It’s a structural mismatch.

I also don’t think you can wave this away as “just an auth detail.” In practice, auth decides who gets to use the tool. If Microsoft’s own clients connect smoothly and everyone else has to wait on Entra work, that shapes adoption just as much as the API surface does. The article is careful not to call it strategy, and I think that caution is right. This reads more like platform gravity than a clean competitive move. Still, the effect is the same.

What I’d actually try, if I were on a team using Azure DevOps and Claude Code, is the boring path: see whether the local MCP server is good enough and whether Microsoft really keeps parity between local and remote. If they do, fine. If not, the “GA” label matters less than the fact that the hosted option is effectively first-party-only for now.

Reference: Azure DevOps Remote MCP Server Reaches GA, Without Support for Claude, ChatGPT, or Cursor

同じ著者の記事

Claude on a Cheap Smart Watch Is a Better Demo Than It Looks

What struck me here is not that Claude can help with a tiny firmware project. That part is almost boring now. The interesting bit is how quickly the constraints of the device turn the whole exercise into a very human workflow: the model can get you a rough result fast, but once you hit text placement, rendering limits, and hardware latency, you’re back to being the person who has to notice what looks wrong. I actually like that honesty in the post. It doesn’t pretend the watch face was “fully ag

papoo.work

Runtime model switching is useful, but the demo feels more like a pattern than a product

What caught my eye here is not the “multi-model” part. That’s easy to demo and easy to overstate. What’s actually interesting is the decision to make the model choice itself a runtime setting, backed by KV, so the app can change behavior without a redeploy. That’s a real operational move, and I’d absolutely steal the idea. At the same time, I’m a little skeptical of how clean this looks in the article versus how messy it gets in a real system. Switching the active model globally is fine for a to

papoo.work

When “session not found” is really a deployment bug

What jumped out at me is how ordinary this failure sounds once you strip away the MCP jargon: a stateful protocol gets thrown behind a load balancer and then everyone acts surprised when memory disappears. That part is not subtle. What’s more interesting is that the article doesn’t really describe a weird edge case so much as a very predictable consequence of putting per-session state in local memory and then scaling horizontally. I’m mostly convinced by the diagnosis. If the session lives on on

papoo.work

Cloudflare’s WriteGuard feels like the boring security layer MCP has been missing

What jumped out at me is not the “AI agents can now write things” part. That ship has already sailed. It’s that Cloudflare is trying to put a shared control plane around the messy part: not just whether an agent can act, but which actions count as harmless, which ones are mildly annoying, and which ones are “stop and think very hard.” That seems like the right instinct. MCP has made it easy to connect models to tools, but “easy to connect” is not the same thing as “safe to let loose.” Read-only

papoo.work

MCP’s token tax looks real, but the math feels a little too neat

What jumped out at me isn’t that MCP has overhead. Of course it does. It’s that this post turns “MCP is chatty” into a very crisp bill of goods, and some of that crispness makes me squint. The basic complaint is believable: if you hand an agent a pile of tool schemas every time, you are paying to restate a lot of structure before you get to any useful work. That part is not controversial. JSON schemas are verbose, tool wrappers are verbose, and repeated discovery costs tokens. If you’ve ever wat

papoo.work

Claude Code Needs Guardrails, Not Just Better Prompts

What struck me here is how ordinary the failure modes are. Not “rogue AGI” stuff. Just the boring, expensive mistakes that happen when a tool is powerful enough to edit files, run shell commands, and touch databases without pausing to think like a cautious human. That’s exactly the problem Claude Code has, and exactly why hooks sound less like a neat feature than a necessary seatbelt. I’m more convinced by the defensive examples than by the article’s tone. The piece leans hard into “Claude becom

papoo.work

Shipping the findings, not the keys

What jumps out to me is how carefully Anthropic is slicing the capability here. They’re basically saying: you can have the output of the dangerous thing, just not the dangerous thing itself. That feels sensible, but also a little fragile. If the strongest model can really find exploitable issues in codebases, then the product is the model as much as the report. The whole challenge is whether the boundary between “defensive artifact” and “general-purpose offensive capability” stays meaningful onc

papoo.work

Anthropic Quietly Moving the Goalposts Again

The annoying part here isn’t even the experiment itself. It’s that the model apparently started interpreting the same effort label differently, server-side, with no obvious changelog note. If you’re building against Claude Code and your prompt or tooling suddenly feels “dumber,” that kind of change is exactly the sort of thing that sends you chasing ghosts in your own code. I’d be more forgiving if this were clearly documented as an experiment and easy to detect. But the whole complaint here is

papoo.work

MCP Is Growing Up, and It’s Still a Bit Too Eager to Be Everything

What jumped out at me isn’t the roadmap itself so much as the shape of it: MCP is no longer talking like a clean tool protocol with a few adjacent ambitions. It’s now trying to become the layer where agents, auth, discovery, transport, and server behavior all meet. That’s a big bet. Maybe the right bet. But it also raises the usual question with protocol work: are we standardizing the thing people actually need, or are we slowly turning one protocol into a suitcase for every unsolved problem in

papoo.work

Claude Gets Teeth, but I’d Still Keep My Finger on the Trigger

What jumps out to me isn’t the Gmail hookup itself. It’s that Anthropic is clearly pushing Claude from “reads your stuff and drafts something nice” toward “can actually do the admin work.” That’s a meaningful shift. Sending mail and moving files are the sort of actions that make an assistant feel useful instead of decorative. But I’m not entirely sold on the hand-wavy confidence people may read into this. Email is where small mistakes become annoyingly public, and Drive is where a bad action can

papoo.work