MASSIVE GROK APP DIRECTORY BREAKDOWN

What Grok Apps Actually Are:
Structured API wrappers for AI agents. Most implement MCP (Model Context Protocol) - a standardized interface spec that lets LLMs call external services without brittle web scraping. Think function calling but with a protocol layer.

Architecture:
• Official apps live in Grok's native catalog, usually maintained by the service provider
• Community apps are third-party MCP servers (zero QA, use at own risk)
• Auth tokens stored server-side on Grok's connector backend - bots never touch credentials directly
• Some community implementations run as local processes on client machines instead of remote servers

Installation Flow:
1. Access via Connect apps sidebar (mobile: tap avatar)
2. Search + add + OAuth flow
3. Or just prompt: "Add the Linear app" and it auto-installs
4. Custom MCP servers can be added via server URL or CLI command

Execution Model:
• Apps are account-scoped, not bot-scoped (one install = all bots can use it)
• In chat: @ mention to attach app context to a specific task
• Permissions inherit from your service account - no privilege escalation

Why This Matters:
MCP is becoming the de facto standard for tool use in production AI systems. This directory essentially maps the emerging ecosystem of AI-native integrations. If you're building agents, understanding which services expose MCP endpoints tells you what's actually composable right now vs. what requires custom tooling.