# Tasks, contacts and outgoing mail

Enable additional domains deliberately, with their own permissions.

Source: https://docs.getridian.com/guides/additional-tools/
Language: en
Reviewed: 2026-09-20

## Separate permission domains

Google and Microsoft accounts can expose supported task, contact and outgoing-mail operations. Each domain requires its own provider consent, workspace allowance and client permissions. A calendar grant alone is insufficient.

| Domain | Examples of supported MCP operations | Scope boundary |
| --- | --- | --- |
| Tasks | List task lists, read tasks, create/update/delete, mark complete | `tasks:read`, `tasks:write` |
| Personal contacts | List eligible accounts, search/read/create/update/delete contacts | `contacts:read`, `contacts:write` |
| Outgoing mail | List eligible accounts and send an authorized message | `mail:send` |

The [MCP tool reference](https://docs.getridian.com/developers/mcp/) is the exact request/response contract. Provider support and restrictions still apply. These tools are not evidence of a corresponding REST endpoint.

## Test safely

For tasks, create an explicitly named test task in an allowed list, inspect it, then remove it. For contacts, use synthetic contact details. Sending mail delivers a real message: choose a recipient you control and explicitly confirm the intended send. Do not use customer addresses for infrastructure tests.

## Boundaries

Gmail support is outgoing mail, not inbox reading. Mail sending is not a bulk-campaign system. CalDAV calendar support does not imply CardDAV contacts or Apple Reminders access. Organization-wide directories and personal address books are different resources.

If a tool is absent, inspect domain permissions and refresh client metadata where appropriate. Do not broaden calendar access to compensate for a missing task or contact scope.