Help & Documentation

Disconnect AI tools from your DashHarbor website

Revoke an EmDash API token, verify that access has stopped and remove the connection and credentials from your AI tool.

Revoke the token in your website's native EmDash editor first. Removing an AI application's local connection does not revoke its server-side access.

These steps apply to the native personal-token setup in Connect AI tools to your DashHarbor website. Each website and environment has its own tokens, so check the hostname before making changes.

1. Revoke the token in EmDash

Sign in to DashHarbor, open the intended website and choose Edit website or Open EmDash editor. In EmDash, go to Settings → API Tokens.

Find the named token for the tool, select Revoke and confirm. If each tool has its own token, revoking this one leaves the others independent. If you shared a token between tools, every connection using it loses access.

2. Verify that new requests are rejected

Before removing the local connection, use it to make a fresh read request. It should be rejected for failed authorization. A previous reply or cached result is not a new request and does not prove revocation failed.

If a new request still succeeds, check whether the client retried with another configured credential and whether you revoked the correct token on the correct website. Do not keep granting access to troubleshoot. Contact support with the hostname and a redacted error if the result is unclear.

Revocation does not erase content already returned to an application or stored in a conversation. Manage that history separately through the application's own controls.

3. Remove the client connection

Use your AI application's connection settings to remove the matching MCP server. Procedures differ between clients.

For the Codex CLI example in the connection guide, run:

codex mcp remove dashharbor-production
unset DASHHARBOR_MCP_TOKEN DASHHARBOR_MCP_URL

Use your actual server name if you chose a different one. These commands remove local configuration and variables; the EmDash revocation in step 1 is what ends server-side access.

4. Clear locally stored credentials

Remove the token from the client's secret store or secret manager if it was saved there. Clear it from other terminals, running processes or local configuration you used for this connection, then restart affected clients as needed.

The Bash unset command only clears variables in the current shell. It cannot erase a value inherited by an already running process or stored elsewhere. Avoid printing the token while checking cleanup.

Connect again later

Create a new token in the same website's EmDash settings. A revoked token cannot be reused. Choose a clear name, an expiry and only the required permissions, then follow the connection guide.

If you cannot find the token, contact DashHarbor support with the website hostname and the connection name. Never send the credential value.