I’ve been watching the rise of the Model Context Protocol (MCP) with interest. While it’s gaining traction in the enterprise space for internal tools and databases, I’m convinced we’re heading toward a future where consumers will interact with all sorts of remote services via MCP. The problem I hit was that while the ecosystem is growing, there wasn't a great way to use remote MCP servers from a mobile device without a monthly subscription. I wanted a high-quality native experience on my phone that I actually owned, so I built Joey.
Joey is a mobile-first AI chat client that connects to any model via OpenRouter and supports remote MCP servers over HTTP. It handles the full agentic loop, including many MCP features like sampling, elicitation, and OAuth. All your OAuth tokens and history stay on your device since there is no middle-man proxy server, and I collect no telemetry.
The project is source-available under the FSL-1.1-MIT license. Since it is a standard Flutter app, it is easy to build it yourself and deploy to your own device if you have the SDK installed. I’d love to hear your thoughts on the future of consumer MCP and how we'll be managing these tools on the go.
I’ve been watching the rise of the Model Context Protocol (MCP) with interest. While it’s gaining traction in the enterprise space for internal tools and databases, I’m convinced we’re heading toward a future where consumers will interact with all sorts of remote services via MCP. The problem I hit was that while the ecosystem is growing, there wasn't a great way to use remote MCP servers from a mobile device without a monthly subscription. I wanted a high-quality native experience on my phone that I actually owned, so I built Joey.
Joey is a mobile-first AI chat client that connects to any model via OpenRouter and supports remote MCP servers over HTTP. It handles the full agentic loop, including many MCP features like sampling, elicitation, and OAuth. All your OAuth tokens and history stay on your device since there is no middle-man proxy server, and I collect no telemetry.
The project is source-available under the FSL-1.1-MIT license. Since it is a standard Flutter app, it is easy to build it yourself and deploy to your own device if you have the SDK installed. I’d love to hear your thoughts on the future of consumer MCP and how we'll be managing these tools on the go.
GitHub: https://github.com/benkaiser/joey-mcp-client