Status: Not connected

Compatible MCP clients can use proposed Mailflow tools after a future server and authorization flow are released.

Raw API secrets are never displayed here.

1. Choose a project and environment.
2. Select minimal scopes.
3. When a Mailflow MCP server is available, complete its authorization flow.
4. Add its configuration to a compatible MCP client.

Example configuration is illustrative and will not connect today.

{
  "mcpServers": {
    "mailflow": {
      "command": "<future-mailflow-mcp-client>",
      "args": [
        "--project",
        "prj_core_01",
        "--environment",
        "test"
      ],
      "env": {
        "MAILFLOW_TOKEN": "<scoped-token>"
      }
    }
  }
}

Request (illustrative): tools/call list_sending_domains
Arguments: {"project_id":"prj_core_01"}
Response: {"domains":[{"name":"example.com","status":"verified"}]}

Authentication: use a future scoped authorization token. Do not paste production API secrets into client configuration.

Permission denied? Check selected scopes and project access. Connection unavailable? The MCP server has not been implemented.