SN-MCP-Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SN_LOG_DIR | No | Override the log file directory. | |
| GITHUB_TOKEN | No | GitHub Personal Access Token for sn_read_docs (branch lookup and GitHub search). | |
| LOGS_TIMEZONE | No | IANA timezone for log timestamps (CURRENT, GLOBAL, or a named zone). | CURRENT |
| SN_MCP_VERBOSE | No | Set to 'true' to enable debug logs. | false |
| SN_INSTANCE_CONFIG | No | Path to the sn-instance.json configuration file. |
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 |
|---|---|
| sn_read_docsA | Access the official ServiceNow AI Platform documentation from https://github.com/ServiceNow/ServiceNowDocs — pure markdown, optimised for LLM use. IMPORTANT: Never fetch servicenow.com/docs — it is a JS SPA with no readable content. Three execution modes: get_index — Fetch llms.txt (full release index) so you can study the layout and navigate on your own. Pass 'publication' to drill into one area's TOC. search — Pass a keyword to find relevant topics across all publications and supplement the results with GitHub code search in the ServiceNowDocs repo. Returns file_url and file_path values ready for get_file. get_file — Directly read any doc file when you know the path or URL (after reading an index or following a relative markdown link). Version resolution (fully dynamic — zero hard-coded branch names): • Pass 'version' with a release name (e.g. 'Xanadu', 'Zurich', 'Australia'). • Default branch is fetched live from GitHub API — always correct, zero maintenance. • Valid branches come from llms_template.txt in the repo — the authoritative list. • Matching is case-insensitive and fuzzy against that live list. • Unknown/mistyped versions fall back to the default branch with a clear notice. Recommended workflow:
|
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 1 tool
There is only one tool, so there is no ambiguity between tools. The tool's internal modes (get_index, search, get_file) are clearly distinct and well-documented.
The single tool name 'sn_read_docs' follows a clear verb_noun pattern with a consistent prefix. Since there are no other tools, consistency is trivially maintained.
With only one tool, the server is at the lower edge of what is typically appropriate. The tool is multi-functional and covers multiple operations, but a single tool still feels thin for a docs server.
The tool provides a complete workflow for accessing ServiceNow documentation: index browsing, keyword search, and direct file retrieval, with dynamic version resolution. There are no obvious gaps for a read-only docs access server.