Integration

Venafi TLS Protect integration

Venafi Control Plane TLS Protect Cloud API for machine identity management: inventory the certificates of the tenant with their validity, subject, issuer and the instances where they were found installed, search that inventory with a structured expression, download the issued certificate, raise and follow certificate requests through their approval and issuance states, and read the applications, issuing templates, users and teams that govern who may request what.

Connect Venafi TLS Protect How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Venafi TLS Protect.Built from the 14 Venafi TLS Protect tools below, on the connection you add once.

Common Venafi TLS Protect use cases

finding the requests still waiting for approval
requesting a certificate for a newly deployed service
finding every certificate expiring in the next thirty days
retrieving an issued certificate to install it on a server
checking when a certificate expires and where it is installed
inventorying the certificates of a tenant for an expiry report
resolving the application identifier a certificate request needs
resolving the team that must approve a pending certificate request
resolving the issuing template identifier a certificate request needs
waiting for a requested certificate to be issued before installing it

What you can do with Venafi TLS Protect

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Certificate, 4 operations

download_certificateDownload certificateGETDownloads the issued certificate from Venafi TLS Protect as a file.
get_certificateGet certificateGETReturns one Venafi TLS Protect certificate with its full detail.
list_certificatesList certificatesGETLists the certificates Venafi TLS Protect holds for the tenant.
search_certificatesSearch certificatesPOSTSearches Venafi TLS Protect certificates with a structured field expression.

Certificate request, 3 operations

create_certificate_requestCreate certificate requestPOSTRequests a certificate from Venafi TLS Protect and returns the request to poll.
get_certificate_requestGet certificate requestGETPolls one Venafi TLS Protect certificate request and reports whether it has issued.
list_certificate_requestsList certificate requestsGETLists the Venafi TLS Protect certificate requests and their states.

Application, 2 operations

get_application_by_nameGet application by nameGETResolves a Venafi TLS Protect application name into its identifier and policy.
list_applicationsList applicationsGETLists the Venafi TLS Protect applications certificates can be requested for.

Issuing template, 2 operations

get_application_issuing_templateGet application issuing templateGETReturns the issuing template policy an application exposes under a given alias.
list_issuing_templatesList issuing templatesGETLists the Venafi TLS Protect issuing templates and the policy each applies.

Team, 1 operation

list_teamsList teamsGETLists the Venafi TLS Protect teams and their members.

User, 1 operation

list_usersList usersGETLists the Venafi TLS Protect users of the tenant.

User account, 1 operation

get_user_accountsGet user accountsGETReturns the Venafi user and company the API key authenticates as.

Use Venafi TLS Protect from Claude Code, Cursor or Codex

Connect Venafi TLS Protect in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Venafi TLS Protect operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Venafi TLS Protect

Create your workspace
Sign up free. Nothing to install.
Connect Venafi TLS Protect once
Add your Venafi TLS Protect connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Venafi TLS Protect integration FAQ

What can you do with the Venafi TLS Protect integration?

LiveContext exposes 14 operations on Venafi TLS Protect, covering certificate, certificate request, application and issuing template. Common uses include finding the requests still waiting for approval, requesting a certificate for a newly deployed service and finding every certificate expiring in the next thirty days.