Tenable Docs MCP server
Commit Nov 14, 2026An MCP server that provides cited answers from Tenable's product documentation across multiple languages and versions.
Also known as lanz/tenable-docs-mcp, tenable-docs-mcp
- Stars
- 0
- Tools
- 20
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Nov 14, 2026
- License
- GPL-3.0
What is Tenable Docs MCP?
Tenable Docs is an MCP server that provides cited answers from Tenable's product documentation across multiple languages and versions. It exposes 20 tools, such as search_docs, read_doc, outline.
Summary generated from the project's README
About Tenable Docs MCP server
Finding specific technical details within Tenable product documentation is what this MCP server enables for security professionals and developers. It provides cited answers from over 21,000 pages of documentation, covering products like Tenable.io, Tenable.sc, and Tenable.ad across multiple versions and eight different languages, including Japanese, Chinese, and Spanish.
The server runs locally as a single Go binary with an embedded SQLite index, ensuring privacy by avoiding telemetry. Users can connect it to MCP clients like Claude Desktop via a dedicated extension or by using a container image. It manages its own data by downloading a prebuilt index snapshot, which it updates daily to stay current with the latest product guides and release notes.
Unlike generic web searches, this tool understands the specific structure of technical docs, such as settings tables, requirement statements, and required roles. It includes specialized tools like verify_citations to ensure every link provided in an answer is valid and points to the correct version or language. If the documentation lacks an answer, the report_gap tool allows users to flag the missing information for the Tenable documentation team.
What you can do with it
- 1Retrieve specific product settingsAsk an AI assistant to find the default value for a specific security setting within a Tenable product guide.
- 2Verify documentation linksEnsure that the URLs provided in a technical response are active and point to the correct section of the manual.
- 3Search documentation in multiple languagesQuery technical requirements using Japanese or Spanish to get accurate results from translated documentation sites.
- 4Identify documentation gapsRecord instances where the official product manuals do not contain the information needed to solve a problem.
Written from the project's README. Every use case is checked against a quote from it.
How to install Tenable Docs MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Tenable Docs MCP in Claude Code
$ claude mcp add tenable-docs-mcp -- docker run -i --rm ghcr.io/lanz/tenable-docs-mcp:1.0.1Install Tenable Docs MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"tenable-docs-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/lanz/tenable-docs-mcp:1.0.1"
]
}
}
}Install Tenable Docs MCP in VS Code
.vscode/mcp.json
{
"servers": {
"tenable-docs-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/lanz/tenable-docs-mcp:1.0.1"
]
}
}
}Install Tenable Docs MCP in VS Code CLI
$ code --add-mcp '{"name":"tenable-docs-mcp","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/lanz/tenable-docs-mcp:1.0.1"]}'Install Tenable Docs MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"tenable-docs-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/lanz/tenable-docs-mcp:1.0.1"
]
}
}
}Install Tenable Docs MCP in Codex
$ codex mcp add tenable-docs-mcp -- docker run -i --rm ghcr.io/lanz/tenable-docs-mcp:1.0.1Install Tenable Docs MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.tenable-docs-mcp] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/lanz/tenable-docs-mcp:1.0.1"]
Install Tenable Docs MCP in Gemini CLI
$ gemini mcp add -s user tenable-docs-mcp docker -- run -i --rm ghcr.io/lanz/tenable-docs-mcp:1.0.1Install Tenable Docs MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"tenable-docs-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/lanz/tenable-docs-mcp:1.0.1"
]
}
}
}Tenable Docs MCP tools 20
Detected from the READMEsearch_docsread_docoutlinebrowse_guiderelated_pageslist_productsfind_settingrequired_rolerequirementsrelease_notescompare_versionswhats_changed
Show all 20 toolsShow fewer tools
define_termverify_citationsreport_gapopen_feedback_formindex_statusrefresh_indexproductsstatus
Configuration
TDM_INDEX_DIRTDM_INDEX_URLoff turns automatic downloads and updates of the index off
TDM_SITESOnly download these sites' docs, such as en,jp (default: all eight)
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelanz/tenable-docs-mcp is public and reachablegithub.com/lanz/tenable-docs-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)GPL-3.0spdx.org/licenses/GPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/lanz/tenable-docs-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model20 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubTenable Docs MCP
A Model Context Protocol server that answers questions from Tenable's product documentation, with a link to the exact section that supports each answer. It covers docs.tenable.com and its seven translated sites, in every product, guide, and published version, and it runs locally as a single Go binary with an embedded SQLite index.
For questions about Tenable's APIs, use the Tenable Developer Portal MCP, which developer.tenable.com hosts. The two are complementary: this server covers the product documentation, and that one covers the API reference.
Contents
- Why it exists
- Features
- Install
- Connect it to an MCP client
- The companion skill
- Tools
- Prompts, resources, and completions
- How a question becomes a cited answer
- The index and snapshot format
- Command line
- Hosted mode
- Privacy and security
- Search quality
- Limitations
- Development
- License
- Disclaimer
Why it exists
Tenable's documentation is large (about 21,200 pages across eight sites), versioned per product, partly translated, and structured in ways a generic web search ignores: settings tables, requirements tables, required-role statements, release-note entries, and per-guide tables of contents.
Tenable Docs MCP indexes that structure and exposes it through MCP tools, so an assistant can:
- find the section that answers a question, in the right product, version, and language;
- read it as Markdown, with its place in the guide and the roles it requires;
- answer narrow questions (a setting's default, a port, a required role) from the tables the docs already contain;
- cite a stable link to the heading, and check every link before sending the answer;
- say plainly when the docs don't cover something.
With and without the Tenable Docs MCP shows the difference on four real questions: without it, an assistant answers from memory, and gets two of them wrong.
Features
- Eight sites, one index. English, Japanese, Simplified Chinese, Traditional Chinese, Korean, French, German, and Spanish, each with current and older-version guides.
- Language-aware full-text search. SQLite FTS5 with a tokenizer per language: Porter stemming for English, diacritic folding for French, German, and Spanish, and trigrams for Japanese, Chinese, and Korean.
- Question understanding. Recognizes 22 products by current, retired, and short names (Tenable.io, Tenable.sc, Tenable.ad, NNM, PVS, and others), product versions ("Security Center 6.3"), quoted phrases, and the kind of question: how-to, what's new, or requirements.
- Version and language fallback. Searches the version a question names, falls back to its major and minor version, then to the current version, and says so. Falls back to English when a translated site has nothing for the question, and says so.
- Section-level citations. Pages are split at their headings, and every section carries the URL of its anchor. Translations and older versions also return the current English page with the same anchor.
- Structured answers. Dedicated tools read settings tables, requirements tables, required-role statements, release-note entries, and glossaries.
- Citation checking.
verify_citations(and theverify-linkscommand) checks every docs link in an answer or a draft: the page exists, the anchor is on it, and whether the link points to an older version or a translation. - Honest gaps. When the docs don't answer a question,
report_gaprecords it locally and, if the user chooses, sends it to Tenable's documentation team through a form the user approves. - Local and private. No telemetry. The only routine network access is downloading the prebuilt index and checking it for updates once a day, or reading the docs sites when it can't be reached; both can be turned off. See Privacy and security.
- Single static binary. Pure Go, including the SQLite driver (modernc.org/sqlite), so it builds with
CGO_ENABLED=0for Linux, macOS, and Windows on amd64 and arm64.
Install
Each release has these ways to install it. Releases are on the releases page, with a SHA256SUMS file, an SBOM, and build provenance attestations (gh attestation verify FILE --repo lanz/tenable-docs-mcp).
Claude Desktop extension
Download tenable-docs-mcp_<version>.mcpb from the release, and open it, or drag it onto Claude Desktop's Settings > Extensions. Claude Desktop installs it and adds the server; there's nothing to configure. The extension holds a binary for each platform: a universal macOS binary for Apple silicon and Intel, Windows (x64, which Windows on Arm runs too), and Linux (x64).
A binary
Download the archive for your platform (macOS, Linux, or Windows; x64 or Arm), unpack it, and put tenable-docs-mcp somewhere on your path. Then set up your client (see Connect it to an MCP client); tenable-docs-mcp config prints the settings.
A container image
docker run -i --rm --mount type=volume,src=tenable-docs-mcp,dst=/data ghcr.io/lanz/tenable-docs-mcp
The image runs the server over stdio, as a user without privileges, and keeps the index (and any recorded questions) in the volume, so it's downloaded once rather than on every start. For a client, use docker as the command and the rest as its arguments. The image is built for x64 and Arm Linux.
The MCP Registry
The server is listed in the MCP Registry as io.github.lanz/tenable-docs-mcp, with the extension and the container image, so clients and directories that read the registry can install it.
From source
With Go 1.26 or later:
go install github.com/lanz/tenable-docs-mcp/cmd/tenable-docs-mcp@latest
Or build a clone with go build ./cmd/tenable-docs-mcp. A build from a clone reports a version from its commit, such as v0.0.0-20261107200239-5f52e6e8e77f; go install …@vX.Y.Z reports the release.
Updating
The documentation index updates itself every day, whatever version of the server you run. A new release of the server brings new features and fixes; the server tells you when one is out. The daily index download names the newest release, so the server finds out without asking anyone else, and then:
index_statusand thetenable-docs://statusresource include anupdatewith the new version and its link,tenable-docs-mcp versionandtenable-docs-mcp doctorprint a line about it, and- your assistant is told, once per session, so it can pass it on.
To update, install the new release the way you installed this one:
| Installed with | Update by |
|---|---|
| The Claude Desktop extension | Downloading the new .mcpb from the release and opening it |
| A release archive | Downloading the new archive and replacing the binary |
go install |
Running go install github.com/lanz/tenable-docs-mcp/cmd/tenable-docs-mcp@latest again |
| The container image | docker pull ghcr.io/lanz/tenable-docs-mcp |
The server never updates itself. Prereleases aren't announced, and a build from a clone doesn't report updates.
Getting an index
There's nothing to set up. The first time the server starts, it downloads the prebuilt index snapshot from https://docs.tenable.com/mcp/index/v1/ in the background and builds the local index from it: about 21,200 pages in 13 shards, 12 MB to download, and a local index of about 380 MB, in under a minute. Until it's done, index_status reports downloading, and the search and reading tools say the index is downloading.
After that, the server checks for an update once a day. Only shards whose files changed are downloaded and rebuilt, and each is swapped in whole, so searches keep working during an update. A failed check is retried an hour later, or after five minutes while the index is still empty. index_status shows when the index was last checked, when the snapshot was built, and the last error, if any.
To download or update the index without starting the server, run tenable-docs-mcp index pull.
When the prebuilt index can't be reached
If a check for an update fails, for example because a proxy blocks the download or a newer snapshot format needs a newer version of the server, the server reads the live docs sites instead, at most once a day, and keeps going until the prebuilt index can be downloaded again. Then it replaces what it read.
- A site the index has nothing for is read in full, as the snapshot is built: its sitemap,
robots.txt, every page, and each guide's table of contents. It's built beside the index and swapped in when it's done. At the polite request rate (see Limits on traffic), all eight sites take about an hour, and Spanish alone under a minute. - After that, each read compares the sitemap with the index. It fetches pages that are new or whose sitemap date changed, and removes pages the sitemap no longer lists or
robots.txtnow disallows. Sitemap dates can lag behind the pages, so it also checks a seventh of the other pages with conditional requests, which cost a304when nothing changed; over a week, every page is checked. For all eight sites, that's about 3,000 requests a day, which take about 10 minutes. - A page that redirects is recorded, so a link to its old address finds the new one. A sitemap entry that isn't a page is remembered, and fetched again only when its sitemap date changes.
- A sitemap that leaves out more than a fifth of a site's pages looks broken, so nothing is removed, and the read reports it.
- The index's change history records what each read added, updated, and removed.
index_status says when the index is kept up to date from the live sites, and when it was last read. tenable-docs-mcp index crawl does the same from the command line, and builds an index from the live sites without the prebuilt one.
Pages that are new since the last update
When read_doc, outline, or related_pages is given a docs page the index doesn't have, the server first follows any redirect a read of the live sites recorded, and otherwise fetches the page from its live site (if robots.txt allows it), adds it to the index, and answers from it. Hosted mode doesn't.
Other ways to build the index
tenable-docs-mcp index import SNAPSHOTbuilds the index from a snapshot folder on disk.tenable-docs-mcp index build -source …builds from local copies of the sites' published files, one folder per site. Most users won't have these.
Settings
| Variable | Effect |
|---|---|
TDM_INDEX_URL |
off turns automatic downloads and updates off. Any other value is the https:// address of a snapshot folder to use instead of the one on docs.tenable.com. |
TDM_CRAWL |
off turns off reading the live sites when the prebuilt index can't be reached, and fetching new pages on demand. The default is on. |
TDM_SITES |
Only download or read these sites, such as en,jp (default: all eight). -sites on index pull and index crawl does the same for one run. |
TDM_SYNONYMS |
The file of your own synonyms, instead of synonyms.txt in the settings folder (see Synonyms). |
NO_COLOR |
Any value turns off color in the help, doctor, and the launch screen. Color is used only in a terminal, and never when TERM is dumb. |
Connect it to an MCP client
The server speaks MCP over stdio, so a client runs it as a command. Connecting MCP clients has a guide for each client, each setting this server up beside the Tenable Developer Portal MCP:
| Client | Where the settings go |
|---|---|
| Claude Desktop | The .mcpb extension, or claude_desktop_config.json |
| Claude Code | claude mcp add |
| VS Code | mcp.json |
| Cursor | ~/.cursor/mcp.json |
| Devin Desktop (formerly Windsurf) | ~/.config/devin/mcp_config.json |
| Gemini CLI | gemini mcp add, or ~/.gemini/settings.json |
| Codex | ~/.codex/config.toml |
tenable-docs-mcp config prints each client's settings with this binary's path already in them and quoted correctly; -client picks one, and -index adds an index folder. It only prints, and never edits a client's files. tenable-docs-mcp doctor checks that everything the server needs is in place.
For example, in Claude Code:
claude mcp add --scope user tenable-docs -- /path/to/tenable-docs-mcp
claude mcp add --scope user --transport http tenable-developer https://developer.tenable.com/mcp
Other clients
Any MCP client that launches stdio servers works the same way. Over stdio, standard output carries only protocol messages, and diagnostics go to standard error.
To use an index somewhere other than the default folder, pass it as arguments, or set TDM_INDEX_DIR in the server's environment. TDM_INDEX_URL and TDM_SITES (see Getting an index) go in the same env block:
{
"mcpServers": {
"tenable-docs": {
"command": "/path/to/tenable-docs-mcp",
"args": ["serve", "-index", "/path/to/index"]
}
}
}
Streamable HTTP
For a client on the same machine that prefers HTTP:
tenable-docs-mcp serve -http 127.0.0.1:8080
The server listens at http://127.0.0.1:8080/mcp, with a health check at /healthz. It accepts only loopback addresses (127.0.0.1, ::1, or localhost) and refuses to start on any other, unless it's a hosted server; see HTTP server hardening. In Claude Code, for example:
claude mcp add --transport http tenable-docs http://127.0.0.1:8080/mcp
The companion skill
The server's own instructions tell an assistant to search before answering. skills/tenable-docs/SKILL.md goes further: it's an Agent Skill that teaches the assistant how to answer from the docs. It covers:
- searching first, and rephrasing two or three times before saying the docs don't cover something
- reading the section before answering, and choosing the specific tools (settings, roles, requirements, release notes, terms) when they fit
- giving the documented steps in order, with the section's link and the required role
- saying which product, version, and language an answer is for, and asking when that's ambiguous
- checking the answer's links with
verify_citationsbefore sending it - offering
report_gapwhen the docs don't answer, and the page's feedback form when a page looks wrong, with the user writing their own feedback - sending API questions to the Tenable Developer Portal MCP
- with the Tenable Hexa AI MCP connected, offering to do the task, and doing it only when the user says yes
To install it in Claude Code, copy the skills/tenable-docs folder into ~/.claude/skills/ (every project) or .claude/skills/ in a project. Claude Code loads it when a question is about a Tenable product. Clients that support Agent Skills from a ZIP file, such as Claude Desktop and claude.ai, take the folder zipped.
Tools
The server registers 18 tools. Each returns structured output (with a JSON schema) and a short text summary for the assistant. The search and reading tools are annotated read-only and idempotent. Most are closed-world, reading only the local index; read_doc, outline, and related_pages are open-world, because for a page the index doesn't have, they can fetch it from its live site (see Pages that are new since the last update).
Search and read
| Tool | What it does | Main inputs |
|---|---|---|
search_docs |
Ranked sections that answer a question, each with its link, a snippet with matched words marked «like this», product, guide type, version, language, location, last-modified date, and required roles. Also returns same-titled pages in other products (also_in), spelling suggestions when nothing matches, and the products that do match when a product filter excluded everything. |
query, plus optional product, guide_type, guide, version, language, release_notes, required_role, and limit (1 to 25, default 8) |
read_doc |
A section (link with #anchor) or a whole page (link without one) as Markdown, starting with a header that gives its location, product, version, required roles, source URL, and update date. Long content comes in parts. Returns the previous and next sections, and the page in other languages and versions. |
url, part, and max_chars (1,000 to 30,000, default 8,000) |
outline |
A page's headings with links and word counts, or a guide's pages from its table of contents. | url or guide, and language |
browse_guide |
A guide's name and table of contents in reading order, with depths, links, and counts of entries below the depth shown. | guide (a path such as nessus/10_8, or any page's URL), language, and depth (1 to 10, default 3) |
related_pages |
A page's parent, previous, and next entries in its table of contents; the docs pages it links to and that link to it; same-titled pages in other products; and the page in other languages and versions. | url |
list_products |
Every product and language in the index, with page counts, each product's English guides with their names and older versions, and when each language was last indexed. | none |
Specific questions
| Tool | What it does | Main inputs |
|---|---|---|
find_setting |
A setting's description, default, valid values, and whether it's required, from the docs' settings tables. Rows that give a default rank higher. | query, product, version, and limit (1 to 20, default 5) |
required_role |
The roles and permissions the docs say a task needs, by page. When no matching page states a role, it says so and lists the closest pages. | task, product, version, and language |
requirements |
Rows from requirements tables: ports, hardware, operating-systems, browsers, dependencies, or other. Infers the kind and product from a question such as "Security Center hardware for 10,000 hosts". |
product, kind, query, version, and limit (1 to 100, default 30) |
release_notes |
Release-note entries, newest first, filtered by product, date range, version (10.8 matches 10.8.1), and words. | product, since, until (YYYY, YYYY-MM, or YYYY-MM-DD), version, query, language, full, and limit (1 to 50, default 10) |
compare_versions |
How a page, or a setting, differs between two versions of an on-premises product: the sections that changed, were added, or were removed, with the lines that differ, or how a setting's default, values, and description changed. Links to the same page in each version don't count as changes. | url (a page in any version) or setting (with product), from_version, and to_version (default: the current version) |
whats_changed |
The pages added, updated, or removed since a date, newest first, with the sections each update changed. See Change history. | since (2026-10-01, 2026-10, or 30d), product, guide, language, and limit (1 to 100, default 20) |
define_term |
Glossary definitions (abbreviations also match by initials, so NVD finds National Vulnerability Database), what a product name refers to, including retired names, and the term's synonyms. | term and language |
find_setting and requirements read English pages, because they recognize tables by their English column headings. For a question in another language, they say so in their notes.
Citations, gaps, feedback, and the index
| Tool | What it does | Network |
|---|---|---|
verify_citations |
Checks every docs link in an answer or draft (Markdown, HTML, or plain text, up to 200,000 characters). See Citations and verify_citations. | Only with check_live |
report_gap |
Records a question the docs didn't answer in a local file only the user can read. If the client can show forms, it then offers the user a form to send the question to Tenable's documentation team. | Only if the user accepts the form |
open_feedback_form |
Shows the user a feedback form for a docs page. The assistant chooses only the page and whether the user found it helpful; the user writes the comment, and there's no argument for one. | Only if the user accepts the form |
index_status |
The server's version, Go version, index folder, and each shard's pages, sections, schema version, build time, and last-indexed time; the automatic updates: where they come from, the last check, when the snapshot was built, any update in progress, and the last error; and whether a newer release of the server is available. | No |
refresh_index |
Updates given pages (up to 500), or every page of a guide and its table of contents, from the live sites. Reports checked, updated, unchanged, removed, and skipped pages, with progress notifications when the client asks for them. | Yes |
Prompts, resources, and completions
Prompts
Each prompt expands into instructions that name the tools to use and end with the same rules: cite the links used, check them with verify_citations, state the product and version, and say when the docs don't cover something.
| Prompt | Use it to | Arguments (required in bold) |
|---|---|---|
how-to |
Get the docs' steps for a task, with the role it needs and what to do first | task, product, version, guide_type, language |
explain-setting |
Explain a setting: what it does, its options and default, where it is, and when to change it | setting, product, version, language |
troubleshoot |
Find likely causes and fixes for a problem or error message, including known issues in release notes | problem, product, version, language |
whats-new |
Summarize a release: features, changes, fixes, known issues, and removals | product, version, language |
who-can |
Find the role or permissions an action needs | action, product, version, language |
upgrade-check |
List what changes between two versions: requirements, deprecations, defaults, upgrade paths, and known issues | product, from_version, to_version, language |
fact-check |
Check a reply or draft against the docs: what's right, wrong, out of date, or unsupported | text, question |
Tenable Docs MCP questions
How do I add Tenable Docs MCP to Claude Code?
Run claude mcp add tenable-docs-mcp -- docker run -i --rm ghcr.io/lanz/tenable-docs-mcp:1.0.1 in your terminal. Add --scope user to make it available in every project.
How do I add Tenable Docs MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Tenable Docs MCP provide?
It exposes 20 tools, including search_docs, read_doc, outline, browse_guide, related_pages.
How is the documentation index updated?
The documentation index updates itself automatically every day by downloading a prebuilt index snapshot.
Is my data private when using this server?
Yes, the server has no telemetry and the only routine network access is for downloading the index or checking for updates, both of which can be disabled.
What languages are supported?
The server indexes English, Japanese, Simplified Chinese, Traditional Chinese, Korean, French, German, and Spanish.