# Mailtwine MCP

Use this skill when a user wants to connect an MCP-compatible client to Mailtwine email workflows.

## Endpoint

Use the remote MCP endpoint:

```text
https://mcp.mailtwine.com/mcp
```

## Authentication

Mailtwine uses OAuth. Start with the MCP endpoint and let the client discover authorization metadata. Do not ask users to paste browser cookies or share raw logged-in sessions.

Discovery:

- MCP Server Card: https://mailtwine.com/.well-known/mcp/server-card.json
- Protected resource metadata: https://mcp.mailtwine.com/.well-known/oauth-protected-resource/mcp
- Authorization server metadata: https://app.mailtwine.com/.well-known/oauth-authorization-server/oauth

## Expected Use

After authentication, use Mailtwine MCP tools for mail search, triage, thread summaries, draft suggestions, routing recommendations, and approval review.

Do not send, delete, archive, close, or reassign mail without explicit approval unless the user has configured that automation.