# Tenable MCP connector

The Tenable connector brings Tenable users, groups, permissions, roles, templates and asset attributes to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, where each person works inside their own Tenable access and every action is logged.

Source: https://elaichi.ai/connectors/tenable/

## Facts

| | |
| --- | --- |
| Application | Tenable |
| Category | Security |
| AI tools | 437 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Tenable is connected

- List Tenable users who are not in any group
- Add Priya to the SOC group in Tenable
- Which Tenable permissions does the contractors group hold?

## Connect Tenable in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Tenable.
2. Optionally set Share with, then press Connect.
3. Paste a Tenable API key. One person generates a token in Tenable and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Tenable tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Tenable MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Tenable MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Tenable MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Tenable MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Tenable MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Tenable to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Tenable tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Tenable through Elaichi

### Check who still has Tenable access

Security. Ask for the full list of Tenable users and spot the accounts that should have gone with the last round of leavers.

### Add a new analyst in minutes

IT. Create the Tenable user, place them in the right group and set their role, without opening the admin console.

### Keep groups aligned with the on-call roster

Security operations. Move people in and out of Tenable groups as the roster changes, then confirm each group's members afterwards.

### Pull permissions before an audit

Compliance. List every Tenable permission and who holds it, then tidy the ones that no longer fit the person's job.

### Retag assets in one pass

IT. Update asset attributes across many Tenable assets at once when an owner, location or business unit changes.

### Find the right template for a scan

Security. Ask which Tenable templates exist and what each one covers before setting up a new scan.

## Elaichi vs Zapier MCP vs Composio for Tenable

All three can connect Tenable to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Tenable tools | Allow or restrict single Tenable tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Tenable call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Tenable to Claude?

Connect Tenable in Elaichi by pasting a Tenable API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself, and Tenable is ready to use.

### Does Tenable work with ChatGPT and Cursor as well as Claude?

Yes. Once Tenable is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Tenable once and every client picks it up.

### What can an AI agent actually do with my Tenable data?

It can list Tenable users, groups, permissions and roles, create or update them, add people to groups, and remove accounts that should be gone. It can also look up Tenable templates and update asset attributes across many assets at once. Short, concrete asks such as 'add Priya to the SOC group' work better than long sentences.

### Does connecting Tenable give the AI every user, group and permission?

No. Every call runs as the person who signed in, so an agent can only see and change what that person's own Tenable role allows. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Tenable already grants them.

### Can my team share one Tenable connection?

Yes. One administrator connects Tenable with an API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every change to a Tenable user or group.

### Can I stop an agent from deleting or changing things in Tenable?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting Tenable users or changing permissions for a role or for one person while leaving read-only asks open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Tenable connection when someone leaves?

Offboarding them in Elaichi ends their access to Tenable through every client at once. A shared Tenable connection keeps working for everyone else on the team. If you disconnect Tenable in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent in one step.

### Does the Tenable MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Tenable is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Tenable?

Yes. Both let Claude, ChatGPT or Cursor use Tenable. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Tenable call.

### How is Elaichi different from Composio for Tenable?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Tenable: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 437 Tenable tools

Every tool below is callable through https://api.elaichi.ai/mcp once Tenable is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Tenable users** (List). List users in Tenable Vulnerability Management. Returns each user's uuid, id, username, email, name, type, permissions, enabled, and group_uuids.
- **Get single Tenable user by ID** (Get). Get a single Tenable user's details by id. Returns the full user object including uuid, id, username, email, name, type, permissions, enabled, group_uuids, lockout, and preferences. Required: id (the user's uuid or unique id).
- **Create a Tenable user** (Create). Create a new user in Tenable Vulnerability Management. Returns the created user object including id, uuid, username, email, name, permissions, and enabled. Requires username and password; passwords must be at least 12 characters with mixed case, a number, and a special symbol. Required: username, password.
- **Delete a Tenable user by ID** (Delete). Delete a Tenable Vulnerability Management user by id. Returns an empty 204 response on success. Web App Scanning scans created by the user are not automatically reassigned — reassign them manually before deleting. Required: id, user_id.
- **Update a Tenable user by ID** (Update). Update an existing Tenable Vulnerability Management user account by id. Returns the updated user object including id, uuid, username, email, name, permissions, and enabled. Required: id.
- **List all Tenable groups** (List). List all user groups in your Tenable container. Returns the group objects including their uuid, name, user_count, id, container_uuid, and managed_by_saml.
- **Create a Tenable group** (Create). Create a user group in Tenable. Returns the created group with its id, uuid, name, container_uuid, and managed_by_saml. Requires name. Required: name.
- **Delete a Tenable group by ID** (Delete). Delete a Tenable user group by id. The group must contain no users before it can be deleted. Returns an empty 204 response on success. Required: id.
- **Update a Tenable group by ID** (Update). Update a user group in Tenable by id. Returns the updated group with its id, uuid, name, user_count, and container_uuid. Requires id and name. Required: id, name.
- **List all Tenable group users** (List). List users belonging to a group in Tenable. Returns each user's id, uuid, name, email, username, type, permissions, enabled status, group_uuids, and lastlogin. Required: group_id.
- **Create a Tenable group user** (Create). Add a user to a group in Tenable. Returns an empty JSON object on success. Required: group_uuid, user_id.
- **Delete a Tenable group user by ID** (Delete). Remove a user from a group in Tenable. Returns an empty JSON object on success. Required: id, group_uuid.
- **List all Tenable permissions** (List). List all access-control permissions defined for your Tenable Vulnerability Management container. Returns: permissions.
- **Get single Tenable permission by ID** (Get). Get details for a single access-control permission in Tenable by id. Returns: permission_uuid, name, subjects, actions, objects, created_at, created_by, updated_at, updated_by. Required: id.
- **Update a Tenable permission by ID** (Update). Update the access control list (ACLs) on a Tenable Vulnerability Management object. Returns an empty response body on success. Specify object_type `scanner-pool` to manage scanner-group permissions. Required: id, object_type, object_id.
- **Create a Tenable permission** (Create). Create a permission in Tenable Vulnerability Management that grants specified actions to specified subjects on specified objects. Returns: permission_uuid, name, subjects, actions, objects, created_at, created_by, and 2 more. Required: name, actions, subjects, objects. AllAssets objects only support limited actions such as CanView and CanScan.
- **Delete a Tenable permission by ID** (Delete). Delete a permission defined for your Tenable Vulnerability Management container by its UUID. Returns an empty response on success. Required: id.
- **List all Tenable user roles** (List). Get the roles assigned to a specific user in Tenable. Returns: container_uuid, user_uuid, role_uuids. Required: user_id.
- **Tenable user roles bulk update** (Update). Change the roles assigned to a specified user in Tenable Vulnerability Management. Returns: container_uuid, user_uuid, role_uuids. Required: user_uuid, role_uuids.
- **List all Tenable templates** (List). List Tenable-provided scan, policy, and remediation templates. Returns: unsupported, cloud_only, order, desc, subscription_only, is_was, title, is_agent, uuid, manager_only, name. Required: type.
- **Get single Tenable template by ID** (Get). Get details for a single Tenable template by id. Returns: is_was, title, name, is_agent, uuid, owner, user_permissions, filter_attributes, settings, credentials, compliance, plugins. Fields can vary by template type. Required: id, type, wizard_uuid.
- **List all Tenable asset attributes** (List). List custom asset attributes assigned to an asset in Tenable. Returns: id, name, value, description. Required: asset_id. An asset container can have a maximum of 10 custom attributes.
- **Tenable asset attributes bulk update** (Update). Assign multiple custom asset attributes to a Tenable asset in one call. Returns an empty 200 response on success. Required: asset_id, attributes.
- **Update a Tenable asset attribute by ID** (Update). Assign a single custom asset attribute to a Tenable asset by setting its value. Returns an empty 200 response on success. Required: id, asset_id, attribute_id.
- **Tenable asset attributes bulk delete** (Delete). Delete all custom asset attributes assigned to a Tenable asset. Returns an empty 200 response on success. Required: asset_id.
- **Delete a Tenable asset attribute by ID** (Delete). Delete a single custom asset attribute from a Tenable asset by id. Returns an empty 200 response on success. Required: id, asset_id, attribute_id.
- **Create a Tenable assets attribute** (Create). Create one or more custom asset attributes in Tenable Vulnerability Management. Returns an empty response body on success. Required: attributes.
- **Delete a Tenable assets attribute by ID** (Delete). Delete a custom asset attribute in Tenable Vulnerability Management by id, removing it from all assets it is assigned to. Returns an empty 204 response on success. Required: id.
- **List all Tenable assets attributes** (List). List custom asset attributes in Tenable. Returns: id, name, description. A container can have a maximum of 10 custom asset attributes.
- **Update a Tenable assets attribute by ID** (Update). Update the description of a custom asset attribute in Tenable Vulnerability Management by id. Returns an empty response body on success. Required: id. Only description can be updated; to change the name, create a new attribute instead.
- **List all Tenable assets** (List). List Tenable assets, up to 5,000 per response. Returns: id, has_agent, last_seen, last_scan_target, sources, acr_score, acr_drivers, exposure_score, scan_frequency, ipv4, ipv6, fqdn, mac_address, netbios_name, operating_system, hostname, agent_name, aws_ec2_name, security_protection_level, security_protections, exposure_confidence_value.
- **Get single Tenable asset by ID** (Get). Get details of a specific Tenable asset by id (asset UUID). Returns the full asset record including name, has_agent, created_at, updated_at, last_seen, sources, acr_score, exposure_score, and installed_software. Required: id.
- **Create a Tenable assets export** (Create). Start an asset export in Tenable Vulnerability Management that queues all assets matching the request filters. Returns: export_uuid. A request with identical filters to an in-progress export is rejected with 429. Required: chunk_size.
- **Tenable assets exports cancel** (Cancel). Cancel an in-progress Tenable Vulnerability Management asset export job. Returns: status. Required: export_uuid. Already-completed chunks remain downloadable for three days after cancellation.
- **Create a Tenable assets exports export** (Create). Start an asynchronous export of all Tenable Vulnerability Management assets that match the request criteria. Returns: export_uuid. Required: chunk_size. Max 10 concurrent exports per container; duplicate exports with the same filters are prevented.
- **Get single Tenable chunks export by ID** (Get). Download a specific Tenable asset export chunk by id. Returns an array of asset records with fields like id, ipv4s, fqdns, operating_systems, sources, and tags. Chunks expire 24 hours after creation (404 for expired chunks). Required: id, export_uuid.
- **Get single Tenable status by ID** (Get). Get the status of an assets export request in Tenable Vulnerability Management. Returns: status, reason, chunks_available. Chunks may complete out of order. Required: id.
- **List all Tenable status** (List). Get the status of a vulnerability export request in Tenable Vulnerability Management. Returns: uuid, status, reason, chunks_available, chunks_failed, chunks_cancelled, total_chunks, chunks_available_count, empty_chunks_count, finished_chunks, filters, num_assets_per_chunk, created, properties. Required: export_id.
- **List all Tenable export status** (List). List vulnerability export jobs in Tenable. Returns the 1,000 most recent jobs regardless of status, each including uuid, status, total_chunks, finished_chunks, filters, num_assets_per_chunk, and created.
- **List all Tenable export status export** (List). List asset export jobs in Tenable. Returns the 1,000 most recent export jobs regardless of status, including uuid, status, total_chunks, finished_chunks, num_assets_per_chunk, and created.
- **Create a Tenable import asset** (Create). Import asset data into Tenable Vulnerability Management. Queues an import job and Returns: asset_import_job_uuid. Required: assets, source. Each asset needs at least one of fqdn, ipv4, netbios_name, or mac_address; AWS, Azure, and GCP data must be imported separately. Max 5 MB per request.
- **List all Tenable import asset jobs** (List). List asset import jobs in Tenable. Returns: job_id, container_id, source, batches, uploaded_assets, failed_assets, start_time, last_update_time, end_time, status, status_message.
- **Get single Tenable import asset job by ID** (Get). Get the status of a specific Tenable asset import job by id. Returns: job_id, container_id, source, batches, uploaded_assets, failed_assets, start_time, last_update_time, end_time, status, status_message. Required: id.
- **Create a Tenable bulk jobs acr** (Create). Overwrite the Tenable-provided Asset Criticality Rating (ACR), an integer from 1 to 10, for one or more Tenable assets via a bulk update job. Returns an empty 202 response on success once the update request is queued. Requires a Lumin license; the request body is a bare JSON array of asset ACR update objects.
- **Tenable bulk jobs deletes bulk delete** (Delete). Bulk delete assets in Tenable Vulnerability Management by creating an asynchronous delete job. Returns the bulk operation result: response with data.asset_count, the number of assets deleted. Required: query.
- **Create a Tenable bulk jobs move to network** (Create). Move Tenable assets from one network to another — from the default network to a user-defined network, from a user-defined network to the default, or between user-defined networks — via an asynchronous bulk job. Returns the bulk operation result (response) including the number of assets moved. Required: source, destination, targets.
- **Create a Tenable compliance export** (Create). Export aggregated compliance scan data from Tenable Vulnerability Management. Queues an export job and Returns: export_uuid. A JSON request body is required even when empty ({}); the export aggregates all compliance scan data rather than results for individual scans.
- **Tenable compliance exports cancel** (Cancel). Cancel a Tenable compliance export job. Unprocessed chunks stop processing and the job status is set to CANCELLED. Returns: status. Required: export_uuid.
- **Create a Tenable vulns export** (Create). Export vulnerabilities from Tenable Vulnerability Management. Queues an asynchronous export of vulnerabilities matching the supplied filters and Returns: export_uuid. No body fields are required; with no time-based filter the export defaults to the last 30 days. Subject to concurrent export limits.
- **Tenable vulns exports cancel** (Cancel). Cancel a running Tenable Vulnerability Management vulnerability export job. Returns: status. Required: export_uuid. Completed chunks remain downloadable for three days after cancellation.
- ...and 387 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
