# How to connect Digicert to OpenClaw (paste one key, 101 tools) > Connect Digicert to OpenClaw with ClawLink: paste your Digicert key once and 101 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/digicert The usual route to Digicert access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Digicert setup: install one ClawHub skill, connect Digicert in the browser, and OpenClaw can call real Digicert actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/digicert ## Setup It takes three steps to connect OpenClaw to Digicert. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Digicert** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect digicert # connect Digicert (browser OAuth) npx -y @useclawlink/cli actions digicert # list available actions npx -y @useclawlink/cli run digicert --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Digicert in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Digicert API key once. Verify the connection by asking OpenClaw: > Use Digicert to add tags to certificate and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Digicert is connected in the dashboard, that agent calls the same 101 Digicert tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Digicert MCP for OpenClaw Looking for a Digicert MCP server for OpenClaw? ClawLink connects Digicert to OpenClaw and exposes 101 Digicert tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Digicert integration](https://claw-link.dev/hermes/digicert) works the same way. ## What the OpenClaw Digicert integration can do 101 Digicert tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 101. ### 30 of 101 Digicert tools for OpenClaw | Tool | What it does | |---|---| | **Add tags to certificate** `digicert_add_tags_to_certificate` | Add custom tags to one or more certificates for categorization | | **Check permission** `digicert_check_permission` | Check if a specific permission is available | | **Create API key** `digicert_create_api_key` | Create a new API key with specified permissions | | **Create auth key** `digicert_create_auth_key` | Create a new AuthKey for account authentication | | **Create container ip rules** `digicert_create_container_ip_rules` | Add an IP restriction rule to a CertCentral account | | **Create finance order pricing** `digicert_create_finance_order_pricing` | Get price estimates for a certificate order | | **Create scan list** `digicert_create_scan_list` | Retrieve the list of scan templates along with their name, status, and configuration | | **Execute graphql query** `digicert_execute_graphql_query` | Execute GraphQL queries against DigiCert Custom Reports API | | **Filter keys** `digicert_filter_keys` | Filter keys in DigiCert Discovery API by various criteria | | **Get account** `digicert_get_account` | Retrieve details about your CertCentral account | | **Get account details** `digicert_get_account_details` | Retrieve account details for the authenticated user | | **Get account guest access** `digicert_get_account_guest_access` | Retrieve the guest access URL for your DigiCert account | | **Get account metadata** `digicert_get_account_metadata` | Retrieve metadata for custom order fields in the account | | **Get account saml entity** `digicert_get_account_saml_entity` | Retrieve SAML entity details for your account | | **Get agent ip port** `digicert_get_agent_ip_port` | Retrieve agent IP port details from DigiCert Discovery API | | **Get alert count** `digicert_get_alert_count` | Retrieve alert count from DigiCert Discovery API dashboard | | **Get auth key** `digicert_get_auth_key` | Retrieve AuthKey details by ID | | **Get authorization container** `digicert_get_authorization_container` | List all containers authorized to perform a permission action | | **Get certificate authority helper** `digicert_get_certificate_authority_helper` | Retrieve certificate authority API helper information including version details | | **Get certificate rating** `digicert_get_certificate_rating` | Retrieve SSL certificate security rating from DigiCert Discovery API | | **Get cloud scan** `digicert_get_cloud_scan` | Get cloud scan details from DigiCert Discovery API | | **Get container by container** `digicert_get_container_by_container` | Get details about a specific container using its ID | | **Get container children** `digicert_get_container_children` | List all child containers for a parent container | | **Get container ip rules** `digicert_get_container_ip_rules` | Retrieve a list of existing IP restriction rules in a CertCentral account | | **Get container order organization** `digicert_get_container_order_organization` | List all organizations assigned to a container | | **Get container product limits** `digicert_get_container_product_limits` | Get information about the limits and settings for a container's enabled products | | **Get container role** `digicert_get_container_role` | Retrieve all access roles available to a container | | **Get container template by template** `digicert_get_container_template_by_template` | Get details about a template in a container | | **Get domain dcv** `digicert_get_domain_dcv` | Retrieve domain DCV (Domain Control Validation) information from DigiCert | | **Get domain dcv emails** `digicert_get_domain_dcv_emails` | Retrieve email addresses that receive validation emails from DigiCert for the email domain | ## Example prompts **Add Tags To Certificate** > Use Digicert to add tags to certificate and walk me through the result in plain English. **Check Permission** > Use Digicert to check permission and walk me through the result in plain English. **Create Api Key** > Create it in Digicert for me, then confirm the important fields before you finish. **Create Auth Key** > Create it in Digicert for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Digicert working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Digicert API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Digicert account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Digicert. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Digicert actions to the runtime in a format your agent can reliably use. | 101 tools for Digicert are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Digicert to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Digicert in the browser, and the 101 tools above work from chat. There is no SDK and no config file, and the Digicert key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Digicert skill but can't call the tools The ClawHub skill teaches OpenClaw about Digicert, but the calls run through the ClawLink plugin and your connected account. Make sure Digicert is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Digicert from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Digicert tools Digicert tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Digicert call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Digicert returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Digicert has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Digicert integration? Yes. ClawLink is the fastest way to connect OpenClaw to Digicert: link your Digicert account once in the browser and OpenClaw can call the Digicert API through 101 ready-made tools — no custom code or token handling. ### How do I add Digicert to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Digicert skill from ClawHub, then you click Connect in the dashboard to authorize Digicert. OpenClaw calls the tools from the next message — no config files, and the Digicert key you paste is stored server-side instead of in your environment. ### How long does it take to connect Digicert to OpenClaw? About two minutes. Sign in, click Connect next to Digicert in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Digicert up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Digicert working from chat. ### OpenClaw installed the Digicert skill but can't call the tools The ClawHub skill teaches OpenClaw about Digicert, but the calls run through the ClawLink plugin and your connected account. Make sure Digicert is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.