Skip to content
EverrunsEverruns

Secure MCP Credentials

Use an Agent credential binding when an MCP tool requires a secret in its input, such as Visti’s visti_send.channel_key. Do not paste the value into chat, Agent instructions, memory, or session storage.

  1. Attach the MCP server capability to the Agent.
  2. Open the Agent and select Credentials.
  3. Add or open the exact server, tool, and parameter binding.
  4. Enter the value in the masked form and save it.

The value is encrypted and is never shown again. Everruns removes the bound parameter from the model-visible tool schema and injects the value only when it sends the MCP request. The same Agent binding works for a shared session and for triggers that create a new session per invocation.

Use Rotate to replace a value. Use the revoke action to delete the binding; future calls then return a setup-required result with a link back to the Credentials tab.

Session Storage has a separate encrypted secret lifecycle for session-local workflows. Those secrets do not follow per-invocation sessions, and a model can read them with secret_store get, so they are not a substitute for an MCP credential binding.