Mcp

I have a little hub, claude-net, that lets my Claude Code sessions talk to each other. Sessions register a name, send each other messages, join teams. It’s genuinely useful, the agent working on the MicroPython unix port can ask the agent working on the picolet runtime what branch it’s actually building, and get an answer, without me being the messenger. Every session runs a plugin to talk to that hub. The plugin is an MCP server: a child process Claude Code spawns, speaking JSON-RPC over stdio on one side and a wss:// websocket to the hub on the other. One per session. Written in TypeScript, run under Bun. ...

I’ve got an image generator wired straight into Claude Code now. Tell it “draw me a whiteboard diagram of the queue lifecycle” inline in any session, and 30 seconds later there’s a PNG on disk, an inline preview in chat, and a URL that’s good for an hour. It works in Claude Desktop too via a stdio extension that proxies to the same backend. ...