Know your data sources.

Google Docs connector for reading and editing documents (read & write). CRITICAL USAGE RULES: 1. Provide documentId from the Docs URL (https://docs.google.com/document/d/{documentId}/edit). 2. Use getDocument() for full structural data; getDocumentText() to quickly extract plain text. 3. Use batchUpdate operations for insertText, updateParagraph, and applyFormatting.

Unified OneDrive + SharePoint document ingestion and structured extraction. CRITICAL USAGE RULES: 1. Use ingest_onedrive_folder() to list/search OneDrive files, download, parse, and normalize. 2. Use ingest_sharepoint_library() to resolve site/drive, ingest library files, and normalize. 3. Parsers support: PDF, CSV, XLSX/XLS, DOCX/DOC, TXT (max file size configurable). 4. Incremental mode supports existing itemId + etag/lastModified to skip unchanged files. 5. Use extract_structured_data() for strict typed extraction (invoice, lease, report). 6. Use upsert_document_record() to keep raw text and extracted JSON separate in a deterministic record shape.

Google Drive connector for listing, searching, downloading, and uploading files. CRITICAL USAGE RULES: 1. Use listFiles() first to discover folder and file IDs. 2. downloadFile() returns file content as base64 (decode client-side if needed). Google Workspace files are auto-exported. 3. searchFiles() searches by name across the entire drive. 4. uploadFile() requires filename + exactly one of contentBase64, contentText, sourceUrl, or fileContent (Buffer/Uint8Array). Prefer sourceUrl (server fetches the bytes) over contentBase64 for large files. 5. listFiles() supports pageSize, pageToken, orderBy, and q (query) for advanced filtering. 6. getFileById(), getFileByPath(), createFolder(), deleteFile(), moveFile(), copyFile(), and createShareLink() are available for file management.

Microsoft Excel connector for workbook automation via Microsoft Graph. CRITICAL USAGE RULES: 1. Provide itemId (drive item ID for the workbook) for all calls. 2. Use siteId when working with SharePoint-hosted workbooks. 3. For long-running workflows, create a session and pass workbook-session-id on subsequent calls. 4. Range addresses should use Excel A1 notation (e.g., Sheet1!A1:B10).

GitHub connector for managing repositories, issues, pull requests, commits, and code. CRITICAL USAGE RULES: 1. Use listRepositories() to discover available repos before other operations. 2. Repository names use owner/repo format (e.g., "anthropics/claude-code"). 3. Use searchCode() for finding code patterns across repositories. 4. Issue and PR numbers are integers, not IDs. 5. File contents are returned as base64 - decode if needed. AUTHENTICATION: - Uses OAuth token from user's connected GitHub account - Scopes: repo, read:user, user:email, read:org

GitHub Projects V2 connector for managing project boards, items, fields, and views. CRITICAL USAGE RULES: 1. Use listProjects() to discover project IDs before other operations. With no args, it lists the authenticated user's projects. 2. Projects use numeric IDs (project_number) visible in the URL. 3. Items can be issues, PRs, or draft issues. 4. Use GraphQL field IDs from listProjectFields() for field updates. 5. View filters and sorts use GraphQL syntax. AUTHENTICATION: - Uses OAuth token from user's connected GitHub account - Scopes: repo, read:user, user:email, read:org, project

Gmail connector for reading messages, threads, and labels, and for sending, drafting, deleting, and relabeling messages on the user's behalf (read & write). CRITICAL USAGE RULES: 1. Use listMessages() or listThreads() to discover IDs before calling getMessage(), deleteMessage(), or modifyLabels(). 2. Search using the q parameter with Gmail search syntax (from:, to:, subject:, has:attachment, etc.). 3. Write operations available: sendEmail, createDraft, trashMessage, deleteMessage, modifyLabels. Prefer trashMessage for "move to trash" / "delete" intents (reversible). deleteMessage is PERMANENT and irreversible — only use when explicitly asked to permanently/forever erase. 4. deleteMessage() permanently removes the message and cannot be undone — confirm with the user before calling it.

Google Calendar connector for managing calendars and events (read & write). CRITICAL USAGE RULES: 1. Use createCalendar() to create new calendars; deleteCalendar() to remove them (cannot delete primary). 2. Use listCalendars() to discover calendar IDs; use "primary" when unsure. 3. Provide ISO timestamps for timeMin/timeMax when filtering events. 4. For createEvent/updateEvent, start and end must include either dateTime or date. 5. Use deleteEvent with sendUpdates='all' to notify attendees of cancellations.

Microsoft OneDrive connector for listing, searching, downloading, and uploading files. CRITICAL USAGE RULES: 1. Use listDriveItems() first to discover folder and file IDs. 2. downloadDriveItem() returns file content as base64 (decode client-side if needed). 3. searchDriveItems() searches from the drive root only. 4. uploadDriveItem() requires filename + exactly one of contentBase64, contentText, sourceUrl, or fileContent (Buffer/Uint8Array). Prefer sourceUrl (server fetches the bytes) over contentBase64 for large files. 5. listDriveItems()/searchDriveItems() support select/top and fetchAll for pagination. 6. getItemByPath(), createFolder(), deleteItem(), moveItem(), copyItem(), createShareLink(), and batchDownload() are available for path and folder management.

Microsoft Outlook mail: search/read messages, parse attachments, and send emails with generated files. RULES: 1. Use outlookMail_get_emails_with_attachments then outlookMail_parse_email_attachments to understand files. 2. Use outlookMail_get_and_parse_emails for one-step retrieval and parsing (PDF/CSV/XLSX/XLS/DOCX/DOC/TXT). 3. Use outlookMail_send_email_with_files when Hermes builds a proposal/report; pass files[].contentText, contentBase64, or path. 4. Raw downloads default metadata-only; use mode:"inline" only for small files or parsing. 5. Use outlookMail_advanced_search for multi-criteria mailbox searches.

Microsoft Outlook calendar connector for calendars and events. CRITICAL USAGE RULES: 1. Use outlookCalendar_list_calendars() to discover calendar IDs before event operations. 2. outlookCalendar_list_events() supports $filter, $orderby, and $search on calendars. 3. Use outlookCalendar_create_event() with a calendarId to add events to shared calendars.

Retrieve Outlook email and parse attachments. Use getEmailsWithAttachments for metadata, parseEmailAttachments for one message, or getAndParseEmails for both. DOCX, XLSX, XLS, CSV, and TXT become Markdown; PDFs and images return in __PATCHOPS_FILES__ as native model content. Legacy .doc is unsupported. fileTypes filters extensions. Default max size is 10 MB; adjust maxFileSizeMB. DOCX tables render as HTML.

Microsoft Planner connector for managing plans, buckets, tasks, and task metadata. CRITICAL USAGE RULES: 1. Use planner_list_plans() to discover plan IDs before task or bucket operations. 2. Updating tasks requires the latest ETag; the planner_update_* helpers auto-fetch when omitted. 3. Task image flow: upload -> attach -> set preview for best results.

Microsoft Power BI — ask questions of existing dashboards and build new ones. READ: listWorkspaces/Dashboards/Reports/Datasets, executeDaxQuery/runDax (DAX server-side aggregations), getDashboardTiles, refreshDataset. BUILD: createPushDataset + pushRowsToTable, createDashboard + cloneTile, uploadPbixOrTemplate + setDatasetParameters (highest-fidelity: real .pbit template). LIMITS: DAX caps 100k rows / 1M values per query — filter via TOPN/SUMMARIZECOLUMNS. Push datasets: 10k rows/request, 1M rows/hour per dataset. Works on Pro and Premium. Premium-only XMLA features TBD.

Microsoft PowerPoint connector for presentations stored in OneDrive or SharePoint. CRITICAL USAGE RULES: 1. Use powerpoint_list_presentations() first to discover item IDs before downloading or exporting. 2. powerpoint_download_presentation() returns base64 content (pptx by default). Use powerpoint_export_presentation() for PDF. 3. Upload requires filename plus contentBase64/contentText/binary fileContent. conflictBehavior supports fail/replace/rename. 4. powerpoint_preview_presentation() returns preview/embed URLs from Microsoft Graph preview.

Microsoft SharePoint connector for sites, lists, drives, and permissions. CRITICAL USAGE RULES: 1. Use sharepoint_search_sites() or sharepoint_get_site_by_path() to resolve site IDs. 2. Use sharepoint_list_lists() to discover list IDs before item/column operations. 3. Use sharepoint_list_drives() to locate drive IDs for document libraries. 4. upload/download file content use base64 payloads for binary data. 5. For batch operations, use sharepoint_bulk_upload() and sharepoint_bulk_download() for parallel processing. 6. For path-based operations, use sharepoint_upload_by_path() and sharepoint_download_by_path().

Google Sheets connector for reading and writing spreadsheet data (read & write). CRITICAL USAGE RULES: 1. Use createSpreadsheet() to create new spreadsheets. 2. Provide spreadsheetId from the URL (e.g., https://docs.google.com/spreadsheets/d/{spreadsheetId}/edit). 3. Use A1 notation ranges (e.g., "Sheet1!A1:D10") for value operations. 4. Write operations available: createSpreadsheet, updateCells, createSheet, formatRange, appendRows.

Google Slides connector for creating and editing presentations (read & write). CRITICAL USAGE RULES: 1. Use createPresentation() to create new presentations. 2. Provide presentationId from the Slides URL (https://docs.google.com/presentation/d/{presentationId}/edit). 3. Use batchUpdate operations for adding, updating, and deleting slides. 4. Write operations available: createPresentation, addSlide, updateSlide, deleteSlide.

Microsoft Teams connector for managing teams, channels, members, chats, and messages. CRITICAL USAGE RULES: 1. Use list_teams() or get_team_by_name() to resolve team IDs before channel/member actions. 2. Provide teamId whenever possible to avoid name collisions. 3. For channel operations, supply channelId or channelName along with teamId. 4. get_chat_id_with() returns a chatId string (not an object) and creates a chat if it doesn't exist. 5. Channel and chat message bodies must be plain text in the content field. PARAMETER ALIASES: - search_users() accepts both "query" and "searchTerm" - get_chat_id_with() accepts both "email" and "userId"