hermes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HERMES_COOKIE | Yes | Full cookie Name=Value string: AWSELBAuthSessionCookie-0=<value> | |
| HERMES_BASE_URL | No | Base URL of your Hermes instance. Defaults to https://hermes-sharepoint.hashicorp.services | https://hermes-sharepoint.hashicorp.services |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hermes_searchA | Search documents in Hermes using full-text search. Returns matching published documents with titles, owners, product areas, and document types. Each result contains an 'objectID' field (a SharePoint GUID like '01XOO7K4...') — pass that value to hermes_get_document to fetch full metadata. Do NOT pass the human-readable 'docNumber' (e.g. 'RFC-123') to hermes_get_document; it will return 404. |
| hermes_get_documentA | Get full metadata for a specific Hermes document by its SharePoint objectID. Returns title, status, approvers, summary, custom fields, and links. IMPORTANT: The document_id must be the 'objectID' field from hermes_search results (a SharePoint GUID like '01XOO7K4...'), NOT the human-readable docNumber like 'RFC-123' or 'HVS-022' — those will return a 404. Always call hermes_search first to obtain the objectID, then pass it here. |
| hermes_list_draftsA | List draft documents in Hermes. Returns documents that are in WIP (work-in-progress) status. Optionally filter by owner email address. |
| hermes_list_document_typesA | List all available document types configured in this Hermes instance (e.g. RFC, PRD, FRD) with their descriptions and custom fields. |
| hermes_list_productsA | List all products/areas configured in this Hermes instance. Useful for knowing valid product filter values when searching. |
| hermes_list_projectsA | List projects in Hermes. Projects group related documents together. |
| hermes_meA | Get the currently authenticated user's profile in Hermes. Useful to confirm the session cookie is working. |
| hermes_create_draftA | Create a new document draft in Hermes. Returns the new document's ID which can be used with other tools. The draft will have WIP (work-in-progress) status until published via hermes_request_review. |
| hermes_update_draftA | Update a document draft in Hermes (WIP status only). Supports updating title, summary, product, contributors, approvers, approver groups, and custom fields. All fields are optional — only provided fields are changed. The document_id must be the SharePoint objectID from hermes_list_drafts or hermes_create_draft. |
| hermes_update_documentA | Update a published document's metadata in Hermes. Supports changing status (In-Review, Approved, Obsolete), title, summary, owners, contributors, approvers, approver groups, and custom fields. For drafts (WIP), use hermes_update_draft instead. Valid statuses: 'In-Review', 'Approved', 'Obsolete'. |
| hermes_request_reviewA | Publish a draft document and request review from approvers. This moves the document from WIP status to 'In-Review' and notifies the assigned approvers. The draft must already have approvers set (use hermes_update_draft to add them first). The document_id must be the SharePoint objectID of a draft. |
| hermes_approve_documentA | Approve a document in Hermes as the currently authenticated user. The document must be in 'In-Review' or 'Approved' status. The current user must be listed as an approver on the document. Use hermes_get_document to check the current status and approver list before calling this. |
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
Each tool targets a distinct resource or lifecycle action: products, projects, drafts, published documents, review/approval, search, and metadata lookups. The only potentially overlapping pair (update_draft vs update_document) is clearly separated by WIP status vs published status.
Tool names follow a consistent hermes_verb_noun pattern (list_*, create_*, update_*, get_*, approve_*, request_*), with a minor deviation in hermes_me which lacks an explicit verb. Overall the naming convention is predictable and readable.
Twelve tools is well within the typical well-scoped range and each tool supports a distinct part of the document management workflow. No redundant or filler tools are present.
The core document lifecycle is covered: create draft, update draft, request review, approve, update published metadata/status, search, and retrieve. Minor gaps exist around rejection/request-changes and explicit deletion, but these are workable given the documented status transitions.