Synergy/DE MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level: debug, info, warn, or error | info |
| SYNERGYDE_CACHE_DIR | No | Directory for caching parsed topics | ./cache |
| SYNERGYDE_DOC_BASE_URL | No | Base URL for online documentation | https://www.synergex.com/docs/ |
| SYNERGYDE_LOCAL_DOC_PATH | No | Path to local documentation directory. If provided, enables local documentation support. The path must be readable and point to a directory containing local documentation files. | |
| SYNERGYDE_DOC_DEFAULT_VERSION | No | Default documentation version to use | latest |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsB | Search documentation topics using full-text search. Returns a list of matching topics with relevance scores. |
| get_topicA | Fetch a documentation topic by ID or URL. Returns the topic with chunked content optimized for LLM consumption. |
| get_related_topicsC | Get related topics for a given topic (previous, next, parent, and related links). |
| list_section_topicsB | List all topics in a documentation section. Returns topic summaries with IDs, titles, URLs, and summaries. |
| describe_docsB | Get metadata about available documentation (versions, sections, source type). |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: describe_docs for metadata, get_related_topics for topic relationships, get_topic for fetching specific content, list_section_topics for section overviews, and search_docs for full-text search. An agent can easily distinguish between them based on their names and descriptions.
All tools follow a consistent verb_noun pattern with snake_case: describe_docs, get_related_topics, get_topic, list_section_topics, and search_docs. The verbs (describe, get, list, search) are appropriate and predictable, making the set easy to navigate and understand.
With 5 tools, the server is well-scoped for documentation access, covering metadata retrieval, topic fetching, section listing, relationship discovery, and search. Each tool earns its place without redundancy, aligning with typical MCP server sizes of 3-15 tools for focused domains.
The tool set provides complete coverage for documentation interaction: describe_docs for overview, list_section_topics and search_docs for discovery, get_topic for content retrieval, and get_related_topics for navigation. There are no obvious gaps, enabling agents to perform full documentation workflows without dead ends.