How to replace a lost MCP Hub token in Blesta

Skip to main content
Print

How to replace a lost MCP Hub token in Blesta

Use New token when an MCP Hub credential has been lost, exposed or needs replacement. This retains the connection and its configured limits while immediately invalidating its old token.

Identify the affected assistant

Open PD Modules → MCP Hub → Connections. Match the connection name, staff account, recent use and visible token hint to the assistant you intend to reconfigure. The hint is not a recoverable copy of the credential.

The module shows a token only when it is issued. Opening Edit cannot reveal the previous token, and changing the connection’s name or ceiling does not generate a replacement.

Issue and save the replacement

  1. Arrange to update every assistant that uses this connection; each will stop authenticating with its old token.
  2. On the active connection’s row, choose New token.
  3. Read and confirm the notice that the current token stops working immediately.
  4. Copy the newly displayed token while it is available.
  5. Replace the saved credential in the intended assistant’s supported secret settings, then reconnect it.

Keep the endpoint from Connect unchanged unless the installation address has also changed. Supply the new token through the supported authentication header or client credential field. Never add it to an endpoint URL, screenshot, support ticket or shared configuration file.

Verify the handover

Refresh the client’s connection and tool list, then check Audit trail for a new connection entry or the result of an authorised lookup. Review the connection’s ceiling, areas and client scope; replacement preserves those limits rather than resetting them.

New token is offered for an active, unexpired connection. If the row is revoked or expired, review that state first rather than deleting it to make the button appear. If you lose the replacement before saving it, another replacement invalidates that one too.

For a credential that appeared in a URL or public copy, treat it as exposed and replace it. Removing the visible copy alone does not make the old credential suitable for continued use.

See the PD MCP Hub Blesta guide for related tasks, or explore PD MCP Hub.

Table of Contents

Get your website online with PD Hosting

UK hosting, domains and support from a real team. From a first site to a full server.

Terms and Conditions  ·  Privacy Policy

PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.

PD Hosting
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.