Siemens Docs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIEMENS_DOCS_HOSTS | No | Comma-separated extra hosts, appended to the built-in two (docs.tia.siemens.cloud, docs.industrial-operations-x.siemens.cloud). | |
| SIEMENS_DOCS_LOCALE | No | Default locale for search and listings. | en-US |
| SIEMENS_DOCS_MIN_INTERVAL | No | Minimum seconds between requests to a host. | 0.3 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Full-text search of Siemens documentation. Returns a numbered Markdown list (1-50 hits via |
| read_pageA | Read one documentation page as Markdown, with a header (publication, version, breadcrumb, source URL).
If the page is longer than |
| get_tocA | Show the table of contents (1-6 levels via |
| list_publicationsA | List documentation publications (up to 50 rows): title, product, version, locale and reader URL.
Use it to discover valid |
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 4 tools
Each tool serves a distinct purpose: search_docs for full-text discovery, read_page for page content, get_toc for hierarchical navigation, and list_publications for catalog browsing. Descriptions clearly state inputs/outputs and how reader URLs flow between tools, leaving no overlap.
All four tools use a consistent snake_case verb_noun pattern: search_docs, read_page, get_toc, list_publications. The only minor variation is the plural 'docs' in search_docs, but the convention remains predictable.
Four tools are well-scoped for a documentation access server, covering discovery, navigation, and reading without redundancy. Each tool earns its place and the set remains lightweight.
The read-only documentation workflow is fully covered: list_publications finds valid products/versions, search_docs locates content, get_toc reveals structure, and read_page retrieves pages with pagination. No obvious missing operation for this domain.