Hermes MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SP_CLIENT_ID | No | Azure AD app client ID for Microsoft Graph path | |
| SP_TENANT_ID | No | Azure AD tenant ID for Microsoft Graph path | |
| HERMES_CHROME | No | Path to Chrome/Edge executable | auto-detect |
| HERMES_BASE_URL | No | Hermes host URL | https://hermes-sharepoint.hashicorp.services |
| HERMES_CDP_PORT | No | Debug-Chrome port for attach + browser content | 9222 |
| HERMES_COOKIE_FILE | No | Path to session cookie file (hot-reloaded) | ./.hermes-cookie |
| SHAREPOINT_TOKEN_FILE | No | Optional pasted Graph token file path | ./.sharepoint-token |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hermes_searchA | Search Hermes docs or projects by relevance (same engine as the Hermes search bar). Returns ranked results with in-doc snippets and a source link per hit — ideal for grounding an answer with citations. |
| hermes_get_documentA | Fetch a Hermes document by its ID (e.g. an objectID from a search result). Returns title, metadata, summary, and source links. |
| hermes_get_document_contentA | Read the FULL text of a Hermes document. By default (source=auto) it tries, in order: the Hermes search index (no SharePoint permissions), then your signed-in browser session over CDP, then a SharePoint/Graph fetch. Provide a documentId (preferred) or a webUrl directly. |
| hermes_get_related_resourcesA | List the resources a Hermes document links to — related Hermes docs and external links. Use to gather the full context around a PRD/spec: linked memos, dependencies, design docs, tickets, repos. |
| hermes_recently_viewed_docsA | List the current user's recently viewed Hermes documents. |
| hermes_check_authA | Check whether the Hermes session cookie is valid. Call this if other tools fail with an auth error. |
| hermes_loginA | Open a browser sign-in window for Hermes (SSO) and capture the session cookie. By default it WAITS until you finish signing in, then returns success so you can proceed. Call this at the start of a Hermes task if not signed in, or whenever a tool reports an authentication error. (Skips the popup if already signed in.) |
| hermes_sharepoint_loginA | Connect SharePoint / Microsoft Graph so full document content can be read. Opens the normal Microsoft browser sign-in (no code to type); after you sign in once, the server stores a token that auto-refreshes. Call this if hermes_get_document_content says it is not configured. |
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 8 tools
Each tool has a clear, distinct purpose: auth checking, document retrieval, full-text content, related resources, login, recently viewed, search, and SharePoint login. No overlapping functionalities.
All tools follow the consistent pattern 'hermes_verb_noun' using snake_case, with descriptive verbs like check, get, login, search, and recently_viewed. No mix of conventions.
8 tools is well-scoped for a document management server, covering authentication, search, retrieval, and related resources without being excessive or insufficient.
The tool surface covers core read operations (search, get, content, related, recent) and auth flows. Missing write operations but likely intentional for a consumption-oriented server.