MCP Shouldn't Require a Desktop: Designing a One-Tap Mobile MCP App

Description and use

Prototype of a mobile-first app for one‑tap MCP tool connection, lacking full OAuth and Drive integration verification.

Problem

Connecting to MCP tools on mobile is cumbersome due to desktop‑centric setup involving runtimes, JSON configs, credentials, and server URLs.

Outcome

The project provides a mobile‑first prototype that demonstrates one‑tap connection to Google Drive for metadata search, but full deployment, live OAuth, and MCP protocol exposure remain unverified.

Workflow

• Open the mobile app or PWA
• Select a connector (e.g., Google Drive)
• Authenticate via Google OAuth
• Review requested permissions
• Use the connector to search for file metadata
• Disconnect when finished

Evidence

Project status, before the marketing goblin gets near the keyboard: the Mobile MCP 0.1.0 source draft exists, and nine focused unit tests passed in the authoring environment.

Google OAuth, a real Drive search, PostgreSQL integration and a deployment have not been tested live.

The first meaningful acceptance test should be boring in the best possible way: Open the actual HTTPS app on a phone. Connect a real Google test account through OAuth. Search for a known file in that account.