OutlookGPT
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTLOOKGPT_CONFIG | No | Absolute path to a config file. | |
| OUTLOOKGPT_READ_ONLY | No | true or false. Overrides server.read_only for this process. Default is true, so write and send tools are refused. | true |
| OUTLOOKGPT_TRANSPORT | No | stdio or http. Selects the transport. HTTP mode is loopback only. | stdio |
| OUTLOOKGPT_ALLOW_DESTRUCTIVE | No | Set to 1 to arm outlook_send_mail. Environment-only; ignored if placed in YAML. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
OutlookGPT is a local Microsoft Outlook MCP server for classic Outlook on Windows. It starts read-only. Write tools require confirm=true. Sending mail is destructive and also requires the process environment variable OUTLOOKGPT_ALLOW_DESTRUCTIVE=1. Tools cover mail search, message reading, draft replies, sending, calendar, and tasks.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_healthA | Report version, transport, read-only mode, and whether destructive tools are armed. |
| mcp_list_modulesA | List which modules are enabled. This server only mounts Outlook. |
| job_statusC | Status of a background job. |
| job_logsC | Recent log lines for a background job. |
| outlook_list_foldersA | List mail stores and folders up to two levels deep. |
| outlook_search_mailB | Search recent mail by subject, sender, or body. An empty query returns the newest messages. |
| outlook_read_mailA | Read one message by the entry_id returned from search_mail. |
| outlook_draft_replyA | Save a reply in Drafts. Does not send it. |
| outlook_send_mailB | Send a new email through the running Outlook profile. This cannot be undone. |
| outlook_list_calendarB | List calendar events starting from now, up to 31 days ahead. |
| outlook_create_eventB | Create a calendar appointment. Times are ISO-8601, local if they have no offset. |
| outlook_list_tasksB | List Outlook tasks. Completed tasks are omitted unless include_completed is true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target a distinct resource+action: search_mail vs read_mail vs draft_reply vs send_mail are cleanly separated, and calendar/task/job tools don't overlap. The only mild fuzziness is between mcp_health and mcp_list_modules (both server-metadata) and job_status vs job_logs, but descriptions make the boundaries clear.
Predictable prefix scheme: mcp_* for server introspection, job_* for background jobs, and a consistent outlook_verb_noun pattern (list_folders, search_mail, read_mail, draft_reply, send_mail, list_calendar, create_event, list_tasks). Minor deviations where metadata tools use noun-only names (mcp_health, job_status, job_logs) instead of verb_noun, but overall readable and consistent.
12 tools is well within the ideal 3-15 range and each tool maps to a concrete operation across mail, calendar, and tasks, plus lightweight infra tools. No obvious filler or redundancy.
Mail covers search/read/reply-draft/send, and calendar covers list/create, but there are notable gaps: no calendar update/delete, no task creation or completion (tasks are only listable), and no mail management like delete, move, or forward. Reply drafting exists but general draft composition does not, leaving several dead ends.