Connect an AI Assistant Using the MCP Server
Tenable Security Center includes a Model Context Protocol (MCP) server that exposes the Tenable Security Center REST API as a set of tools that AI assistants, such as Claude Desktop or Claude Code, can call. With the MCP server, you can query and manage Tenable Security Center using natural language instead of navigating the user interface or writing API requests by hand.
The MCP server is installed with Tenable Security Center. You do not need to install or build anything. You connect your AI assistant to the MCP server endpoint on your Tenable Security Center host.
The MCP server is stateless and has no database of its own. It translates each tool call from your AI assistant into an authenticated Tenable Security Center API request, and returns the result. Because the MCP server authenticates with your Tenable Security Center API keys, the assistant can only perform actions that your user account has privileges to perform.
Requirements
-
A Tenable One Foundation or Tenable One Advanced license.
-
An MCP-capable client, such as Claude Desktop or Claude Code.
-
API key authentication enabled in Tenable Security Center. For more information, see Enable API Key Authentication.
-
Network access from your AI assistant to your Tenable Security Center host on port 443. The MCP server is available at the /mcp path on your Tenable Security Center host.
Connect an AI Assistant to Tenable Security Center
Before you begin:
-
Generate API keys for your user account, as described in Generate API Keys.
To connect an AI assistant to the MCP server:
-
If your Tenable Security Center instance uses a self-signed TLS certificate, trust the certificate on the computer where your AI assistant runs. Node.js-based clients, such as Claude Code and Claude Desktop, reject the connection with an UNABLE_TO_VERIFY_LEAF_SIGNATURE error if they do not trust the certificate.
-
Copy the certificate from your Tenable Security Center host to your computer. For example:
scp root@<your-sc-host>:/opt/sc/support/conf/TenableCA.crt ~/sc-cert.pem
-
In your Claude Code settings file (~/.claude/settings.json), add the path to the certificate as the NODE_EXTRA_CA_CERTS environment variable. Create the file if it does not exist.
{
"env": {
"NODE_EXTRA_CA_CERTS": "/Users/yourname/sc-cert.pem"
}
}
-
Restart Claude Code.
-
-
Add the MCP server to your AI assistant.
-
For Claude Code, run the following command in your terminal, replacing the placeholders with your Tenable Security Center host and API keys:
claude mcp add sc https://<your-sc-host>/mcp --transport http --scope user -H "X-APIKey: accesskey=<your-access-key>;secretkey=<your-secret-key>"
The --scope option determines which projects can use the MCP server:
-
user — Saves the configuration globally, so the MCP server is available in every project on your computer.
-
local — Saves the configuration to your user settings but activates it only in the directory where you ran the command.
-
project — Saves the configuration to a .mcp.json file in your project root. Use this option only with placeholder values, because the file is typically committed to source control.
-
-
For Claude Desktop and other MCP clients, add the following to your client's MCP configuration file, replacing the placeholders with your Tenable Security Center host and API keys:
{
"mcpServers": {
"sc": {
"type": "http",
"url": "https://<your-sc-host>/mcp",
"headers": {
"X-APIKey": "accesskey=<your-access-key>;secretkey=<your-secret-key>"
}
}
}
}
-
-
Restart your AI assistant.
-
Verify the connection by asking your AI assistant to call the sc_system tool with the whoami action.
If the connection works, the assistant returns your Tenable Security Center user name and role.
Caution: Your API keys grant access to Tenable Security Center with your user privileges. Store them securely and do not share them. Your AI assistant sends the keys with every request to the MCP server.
Available Tools
The MCP server provides tools, called toolsets, that each correspond to a Tenable Security Center resource type, such as scans, policies, assets, or users. Most tools accept an action parameter, such as list, get, create, update, delete, or launch, that specifies the operation to perform.
Toolsets are either organization-scoped or administrator-scoped:
-
Organization-scoped toolsets operate within the organization of the user whose API keys you use. Examples include scans, policies, analyze, assets, credentials, reports, and dashboards.
-
Administrator-scoped toolsets operate across organizations and require the API keys of an administrator user. Examples include organizations, users, roles, groups, scanners, zones, feeds, license, and repositories.
Tenable Security Center enforces role restrictions on every request. If a user without sufficient privileges calls an administrator-scoped tool, Tenable Security Center denies the request and the MCP server returns an error to your AI assistant.
Destructive actions, such as deleting a scan, policy, or asset list, require the assistant to ask for your confirmation before it proceeds.
Limit the Toolsets Your AI Assistant Loads
By default, your AI assistant loads all toolsets. To reduce token usage and limit the actions available to the assistant, add an X-SC-Toolsets header to your MCP server configuration that lists only the toolsets you want to use. Separate toolset names with commas and no spaces. Use the tool name without the sc_ prefix.
For example, to load only scanning and analysis toolsets, add the following header:
X-SC-Toolsets: scans,scan_results,analyze,queries
Troubleshoot the MCP Server Connection
Claude Code shows the MCP server as connected, but no sc_* tools are available
Newer versions of Claude Code (2.1.276 and later) use a stateless request flow that the current Tenable Security Center MCP server does not support. The client shows the server as connected, and may show it as not authenticated, but the assistant has no sc_* tools. Calling a tool fails with a No such tool available error. This is not caused by your API keys.
To resolve the issue, add the MCP_PROTOCOL_NEGOTIATION environment variable to your Claude Code settings file (~/.claude/settings.json), and then restart Claude Code. If you already added NODE_EXTRA_CA_CERTS, keep both variables in the same env object.
{
"env": {
"MCP_PROTOCOL_NEGOTIATION": "legacy",
"NODE_EXTRA_CA_CERTS": "/Users/yourname/sc-cert.pem"
}
}
You must restart Claude Code. Reconnecting from the /mcp panel does not restore the tools.
The MCP server rejects requests with a 401 Unauthorized error
The MCP server requires the X-APIKey header on every request. Confirm that your client configuration includes the header in the format accesskey=<key>;secretkey=<key>, and that the API keys are valid and API key authentication is enabled.
Related Topics