read_inbox, search_email, and create_draft that work every time.
How Integrations Work
When you connect a service, Miteos spins up a dedicated MCP server for that integration running as an isolated container in your account. The container handles all communication with the external service using your stored credentials. Agents talk to the MCP server — never to the external service directly — which means:- No credential exposure — Your OAuth tokens and API keys live in an encrypted vault. Agents call tools through the MCP server; they never see or touch the underlying credentials.
- Structured tool calls — Every action the agent takes against an integration is a typed, validated function call with a defined input schema and return value. No improvised scraping or fragile workarounds.
- Auditable actions — Every tool call appears in the War Room Timeline with its inputs and outputs, giving you a full record of what the agent did with each connected service.
Available Integrations
| Service | Available Agent Tools | Category |
|---|---|---|
| Gmail | read_inbox, search_email, create_draft, send_email* | |
| Slack | read_messages, post_message, search_slack | Messaging |
| GitHub | read_repo, create_pr, push_code, search_code | Development |
| Stripe | list_payments, create_invoice, get_customer | Payments |
| Notion | read_page, create_page, update_page, search_notion | Productivity |
| Google Ads | get_campaigns, get_performance, create_report | Advertising |
| Telegram | send_message, read_messages | Messaging |
send_email always triggers an approval gate unless your autonomy level is set to 80 or above. See Autonomy Dial for details.
Connecting an Integration
Go to the Integrations page
Navigate to platform.miteos.com/integrations. You’ll see a catalog of all available integrations with their connection status.
Click "Connect"
Find the service you want to connect and click the Connect button next to it. Miteos redirects you to that service’s authorization page.
Complete OAuth authorization
Sign in to your account on the external service and grant the requested permissions. You’ll be redirected back to Miteos once authorization is complete.
Integration Permissions
Miteos is designed so that agent actions on integrations are powerful but always contained.- Isolated containers — Each integration runs in its own container. A compromised or misbehaving agent cannot pivot from one integration to another.
- Encrypted OAuth vault — Credentials are stored in an encrypted vault and are never passed to the agent runtime. The MCP server acts as a secure proxy.
- Credential isolation — Agents cannot read, log, or exfiltrate your OAuth tokens or API keys. The only thing an agent can do with an integration is call its defined tools.
- Revoke at any time — Disconnect an integration from the Integrations page at any time. The MCP container is torn down and the credentials are removed from the vault immediately.