Shellphone: An MCP Extension to Bridge Claude Chat and Claude Code

If you've ever toggled between Claude's web chat and Claude Code's terminal interface, you know the friction: a great conversation in one place doesn't automatically inform the other. Shellphone, a new open-source MCP extension published on npm, aims to stitch those two worlds together. It's a small but clever piece of glue that lets Claude Code read from and write to Claude chat conversations via the Model Context Protocol, effectively turning your chat history into a resource your coding agent can tap into.

At its core, Shellphone acts as an MCP server that exposes endpoints for fetching recent conversations, retrieving specific messages, and pushing new messages back into a chat thread. That means you can, for example, start a design discussion in Claude's chat UI, then drop into Claude Code and have it pull that entire context into its working session — no copy-pasting, no losing track of where you left off. The reverse also works: you can have Claude Code post a summary or a code snippet back to a chat thread, so your collaborators or future-you can see what happened.

The implementation is straightforward: install the package, configure it as an MCP server in your Claude Code settings, and you're ready to go. The README offers a quick setup command and a few example workflows. Since it's built on the MCP spec, it should also be compatible with other MCP clients, though the docs currently focus on Claude's ecosystem.

What makes Shellphone interesting isn't just the convenience — it's the pattern it represents. MCP is rapidly becoming the universal adapter for AI tools, and extensions like this show how it can blur the lines between chat, IDE, and terminal. For developers who live in the command line but think in conversation, Shellphone is a promising bridge worth a look, even if it's early days and the project hasn't accumulated much traction yet (the HN launch got a single point and no comments).

If you're curious, you can grab it via npm and try it out. There are bound to be sharp edges — it's a brand-new project with a small footprint — but the idea is solid, and the MCP ecosystem is exactly the right place for this kind of integration.