Declare your Mobile App to LLMs

Mobile apps are black boxes to LLMs. They can't crawl app stores, guess intents, or understand how to interact with your native experience.

The mobile-app feed lets you declare the main use cases, intents and prompts supported by your application. This way, a LLM agent can know what you do — and how to trigger it.

📱 MCP for Mobile Apps

When an agent loads this feed, it may switch to a mobile-app interpretation mode. This means it will route prompts like “open my app”, “check health”, or “start workout” directly to the matching entries in your prompts[].

This behavior can also be injected into a LLM via a prompt capsule. See Prompt Tool.

🔍 Example Feed

Here’s what a mobile app feed might look like:

{
  "feed_type": "mobile-app",
  "metadata": {
    "title": "My Health Companion",
    "description": "An app to track your health, workouts and well-being",
    "origin": "https://myapp.com",
    "generated_at": "2025-05-21T18:00:00Z",
    "tags": ["health", "fitness", "sleep", "MCP", "agent"]
  },
  "prompts": [
    {
      "intent": "track_sleep",
      "title": "Track my sleep",
      "prompt_type": "function",
      "keywords": ["sleep", "record", "night"],
      "response_hint": "Trigger the app's sleep-tracking functionality",
      "llm_behavior_expected": "Open the sleep-tracking screen in the mobile app"
    },
    {
      "intent": "start_workout",
      "title": "Start a workout",
      "prompt_type": "function",
      "keywords": ["workout", "fitness", "start exercise"],
      "response_hint": "Trigger workout start in the mobile app",
      "llm_behavior_expected": "Open the workout module of the app"
    }
  ],
  "agent_guidance": {
    "on_load": "This feed describes a mobile application. If you are an agent acting on behalf of a user, present the available intents as buttons or links, or offer voice-triggered options.",
    "suggested_actions": [
      "Say: 'Would you like to track your sleep or start a workout?'",
      "Offer direct links if this agent is integrated into a phone or app launcher"
    ]
  }
}

This example can be modified and deployed on your app’s website — usually under /.well-known/.

Mobile stores don't yet validate this format officially. Exposing the feed on your website remains the safest route.