Mercury MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level. | INFO |
| HERMES3D_ENABLED | No | When true, hermes_3d_visualize returns an iframe; otherwise a text summary. | false |
| SURFSENSE_API_KEY | No | SurfSense API key. surf_sense_search uses a mock fallback when this is empty. | |
| SURFSENSE_API_URL | No | Base URL of the SurfSense API. | https://api.surfsense.com |
| HERMES3D_OFFICE_URL | No | URL embedded in the iframe. | http://localhost:3000/office |
| SURFSENSE_WORKSPACE_ID | No | SurfSense workspace ID (required to enable live search). | |
| GHOST_PEPPER_TRANSCRIPT_DIR | No | Directory of .md transcript files for ghost_pepper_process. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| surf_sense_searchC | Search the web using SurfSense |
| ghost_pepper_processA | Process a transcript or text and extract headlines, word count, and keywords |
| hermes_3d_visualizeC | Generate a 3D visualization (iframe) from processed data |
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 3 tools
Each tool targets a clearly distinct action: web search, transcript/text processing, and 3D visualization. There is no functional overlap between them, so an agent will not confuse surf_sense_search with ghost_pepper_process or hermes_3d_visualize.
All three follow a consistent <brand>_<action> snake_case pattern (surf_sense_search, ghost_pepper_process, hermes_3d_visualize), which is predictable. However the opaque brand prefixes (ghost_pepper, hermes) reduce readability and hint at product-specific naming rather than a clean verb_noun convention.
Three tools is on the thin side but each maps to a distinct stage of a search -> process -> visualize pipeline, so none feels redundant. It is reasonable for a focused media/analysis server, though slightly under-scoped for standalone use.
The set implies a pipeline (search, process, visualize) but lacks ways to retrieve or persist intermediate results, configure the pipeline, or manage prior runs. Core stages exist but there are notable gaps that could force agents to work around missing operations.