outpost
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| task_addC | Add a new task to Microsoft To Do. |
| task_listB | List tasks from Microsoft To Do. |
| cal_addB | Add a calendar event to Outlook. |
| cal_todayA | Get today's calendar events from Outlook. |
| cal_listC | List calendar events from Outlook. |
| cal_nextB | Get the next upcoming calendar event(s) from Outlook. |
| task_updateB | Update an existing task in Microsoft To Do. |
| task_completeA | Mark a task as completed in Microsoft To Do. |
| task_deleteB | Delete a task from Microsoft To Do. |
| task_listsA | List all task lists in Microsoft To Do. |
| task_lists_createA | Create a new task list in Microsoft To Do. |
| task_lists_deleteB | Delete a task list from Microsoft To Do. |
| cal_updateB | Update an existing calendar event in Outlook. |
| cal_deleteB | Delete a calendar event from Outlook. |
| mail_listC | List email messages from Outlook. |
| mail_readB | Read a specific email message from Outlook. |
| mail_sendB | Send an email via Outlook. |
| mail_replyB | Reply to an email in Outlook. |
| mail_deleteB | Delete an email from Outlook. |
| mail_searchA | Search email messages across all folders in Outlook. |
| mail_attachmentsB | List attachments for an email message. |
| mail_download_attachmentB | Download an email attachment. Returns filename and base64-encoded content. |
| contact_listC | List contacts from Outlook. |
| contact_searchB | Search contacts in Outlook by name or email. |
| auth_statusA | Check if the user is authenticated with Microsoft. |
| teams_listA | List your joined Microsoft Teams. Requires the Teams feature to be enabled in outpost setup. |
| teams_channelsB | List channels in a Microsoft Team. |
| teams_messagesC | Read messages from a Teams channel. |
| teams_sendB | Send a message to a Teams channel. |
| teams_filesA | List files in a Teams channel's SharePoint folder. |
| teams_chatsA | List your recent Teams chats (1:1, group, and meeting). Requires the Teams feature. |
| teams_chat_messagesC | Read messages from a Teams chat (1:1 or group). |
| teams_chat_sendB | Send a message to a Teams chat (1:1 or group). |
| teams_downloadA | Download a file from Teams/SharePoint to the local workspace. The file is saved to the local workspace. To read or analyze the file, use the filesystem server to read it at the returned workspace_path. Use teams_workspace_read only for plain text files. Use teams_upload to push changes back. |
| teams_uploadA | Upload a file from the workspace to Teams/SharePoint. Best suited for text-based files created with teams_workspace_write (markdown, CSV, plain text). Binary files (DOCX, XLSX, etc.) should be treated as read-only — use teams_workspace_extract to read them, not modify and re-upload. |
| teams_workspace_listA | List files currently in the transient workspace directory. For binary files (docx, pdf, xlsx, etc.), read them directly at the returned path using the filesystem server. |
| teams_workspace_readA | Read a text file from the workspace directory. For binary files (docx, pdf, xlsx, etc.), this tool returns metadata and a path hint instead of content. Use the filesystem server to read binary files directly. |
| teams_workspace_writeA | Write a text file to the workspace directory for sharing via Teams. For text-based formats only (markdown, CSV, plain text, etc.). Do not use this to create or overwrite binary files (DOCX, XLSX, PPTX, PDF) — use teams_workspace_extract to read those instead. |
| teams_workspace_extractA | Extract text content from a binary file in the workspace. Supports DOCX, XLSX, PPTX, and PDF files. Returns the extracted plain text content. Much faster than reading binary files through the filesystem server. |
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 39 tools
Each tool has a clear prefix (cal_, mail_, task_, teams_) and a descriptive verb or noun, making their purpose immediately distinguishable. Overlaps are minimal and well-documented in descriptions, e.g., teams_messages vs teams_chat_messages.
Most tools follow a consistent verb_noun pattern with underscores, grouped by service prefix. Minor exceptions like cal_next, cal_today, and teams_channels deviate from the verb_noun pattern but are still intuitive.
39 tools is on the higher side but justified by the integration of three Microsoft services (Outlook, To Do, Teams). Some areas like teams_workspace have multiple tools that could be consolidated, slightly bloating the count.
The tool set covers core CRUD operations for calendars, mail, tasks, and Teams, including edge cases like attachments and file workspace. Missing advanced features like calendar sharing or team creation, but these are reasonable omissions for an integration server.