> ## Documentation Index
> Fetch the complete documentation index at: https://docs.miteos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Protocol

> How Miteos uses Model Context Protocol to connect services as agent tools.

# MCP Protocol

Miteos uses the Model Context Protocol (MCP) to integrate external services as agent tools. Each connected service exposes capabilities that agents can invoke during task execution.

## How It Works

1. Service registers tools via JSON-RPC schema
2. Agent discovers available tools from connected services
3. Agent invokes a tool during execution (e.g., gmail.send\_email)
4. Service executes the action and returns result
5. Agent uses the result in its next step

## Server Types

**Internal MCP Servers** — Our own engines running as Docker containers:

* Trading Engine, Stealth Browser, Video Generator, Ads Auditor, Email Agent, Social Media

**Third-Party MCP Servers** — External services connected via OAuth or API keys:

* Gmail, Slack, GitHub, Notion, Stripe, Shopify, Discord, Telegram, Linear, Jira, Airtable, Figma, Supabase

## Architecture

Each MCP server instance is isolated per user session. The hub manages OAuth token refresh, rate limiting, and container orchestration. Idle containers are killed after 5 minutes and auto-scale based on demand.