It has been moving fast.

One weird thing I found a few weeks ago, when I added my remote MCP to Claude's integration tab on the website, I was getting OAuth errors.

Turns out they are requiring a special "claudeai" scope. Once I added that to my server, I was able to use it remotely in claude desktop!

I couldn't find any docs or reasons online for them requesting this scope.

Also, I have been using remote mcps in claude code for weeks with the awesome mcp-remote proxy tool. It's nice to not need that any longer!

Then as I'm writing a book currently on MCP Servers with OAuth, Elicitations come out! I'm rushing to update this book and be the best source for every part of the latest spec, as I can already see lots of gaps in documentation on all these things.

Huge shout out to VS Code for being the best MCP Client, they have support for Elicitations in Insiders already and it works great from my testing.

Yeah, security really is an afterthought with most of these tools, but man the community is moving insanely fast — probably because most of these people are using these automation tools to develop their MCP servers in the first place.

It’s interesting to see other tools struggling to keep up. ChatGPT supposedly will get proper MCP client support “any day now”, but I don’t see codex supporting it any time soon.

Aider is very much struggling to adapt as well, as their whole workflow of editing and navigating files is easily replaced by MCP servers (probably better as well, as it provides much effective ways of reducing noise vs signal), so it’ll be interesting to see how tools adapt.

I’d love for Claude Code (or any tool for that matter) to fully embrace the agentic way of coding, e.g. have multiple agents specialize in different topics and some “main” agent directing them all. Those workflows seem to be working really well.

    > Javascript community suddenly got automatic code creation agents, and went to town.

I've been working on an MCP server[0] that let's LLMs safely and securely generate and execute JavaScript in a sandbox including using `fetch` to make API calls. It includes a built in secrets manager to prevent exposing secrets to the LLM.

I think this unlocks a lot of use cases that require code execution without compromising security. Biggest one is that you can now ask the LLM to make API calls securely because the JS is run in a C# interpreter with constraints for memory, time, and statement limits with hidden secrets (e.g. API keys).

The implementation is open source with sample client code in JS using Vercel AI SDK with a demo UI as well.

[0] https://github.com/CharlieDigital/runjs

> Spec updates every three months are really tough, especially when not versioned, thoroughly documented, or archived properly.

Couldnt AI help with that..?

The crazy thing about things moving fast is that people bought Cursor for hundreds of millions when it is already outdated by Claude Code. Very foolish by the purchasers but very smart for the founders

That's great! It would be even better if one of the features included in the table was whether given MCP supports OAuth Dynamic Client Registration, which optional in the MCP standard.

Thanks!!!

I've found this from an old-school systems geek to be useful https://github.com/giantswarm/mcp-debug -- especially its REPL mode

Does anybody know of a cross-platform LLM-frontend with sync that is also open-source? I am currently using the web version of LobeChat on macOS and Android, but it's quite slow and has some features missing.

easiest one to get going with is to add the Playwright MCP. As a python dev you might have used it to do test automation? Anyway, it gives your tool eg Cursor, Claude Code access to the browser and automation using playwright. Meaning it can literally load a page to confirm its own change just had the desired effect.

The blender one is also fun as a starting point, if you do any 3d modelling (or even if you don't).

You can give LLMs useful tools to have more rich interactions with them - help them help you more.

They're also fun and easy to build.

Here's one I made - it wraps the vscode debugger: https://github.com/jasonjmcghee/claude-debugs-for-you

I've specifically tested it with continue.dev so it might serve as a useful example / template.

I’ve made one MCP server for fun https://altonote.com/.

it allows publishing any text or claude artifact directly from the claude.

I have made it mostly for fun and as an experiment to try what is possible.

Documentation everywhere is still mostly outdated with the recent changes.

Anthropic having created MCP should not be outdated though I agree ..

That MCP remote workaround is no longer necessary

Existing MCP support was for the stdio and SSE transport protocols which are either local MCP servers in docker/node/python or a remote server but still requiring a sort of workaround running locally in the form of the mcp-remote non package.

This now natively supports the latest streamable http transport protocol and the server is entirely remote, nothing is running on your local machine it's just an url (usually ending with /mcp, although not mandatory it's usually true and distinguishes from /sse servers).

  1.0.27
  Streamable HTTP MCP servers are now supported
  Remote MCP servers (SSE and HTTP) now support OAuth
  MCP resources can now be @-mentioned

i think this is coming very shortly. it was just extremely difficult to ship a remote mcp server with proper auth until like 1 week ago. its still barely there, but i think its coming. Every single client side chatbot can suddenly be 100x more effective in its ability to actually do stuff in the app.