This is cool, I’ve been wanting this for ages. The “AI powered game” usecase is going to be huge and really requires BYO API key to work.
I tried wiring something up and immediately hit a gap where I need to be able to call a tool. I think the state management aspect of this is going to be crucial; while you can obviously call a remote MCP server, and they mention this as planned (and that would be the right way to make a full product with persistence work), for Artifact-based development I wonder if you could wrap the API calls in client-side tool calling plumbing and run an MCP server there, so that a single client-side JS Artifact can do both the UI and handle MCP interactions from the API (Claude sandwich, between two slices of browser JS).
I tried wiring something up and immediately hit a gap where I need to be able to call a tool. I think the state management aspect of this is going to be crucial; while you can obviously call a remote MCP server, and they mention this as planned (and that would be the right way to make a full product with persistence work), for Artifact-based development I wonder if you could wrap the API calls in client-side tool calling plumbing and run an MCP server there, so that a single client-side JS Artifact can do both the UI and handle MCP interactions from the API (Claude sandwich, between two slices of browser JS).