🔐Integrations and the Vault (MCP)

How it fits together#

• Vault: where every credential lives, encrypted with AES-256-GCM. The browser never gets a value back, only its name and dates.
• Integration: your organization's connection to a tool (one per tool), set up once on the Connections page and shared by every workspace.
• Connector: the node that gives a Skill access to a tool. It points to a connection or to a credential of its own; it never holds the secret itself.
• MCP (Model Context Protocol): at run time, tools are called through the tool's MCP server.

Connect a tool#

1. 1

   Open Connections

   Go to Connections in the sidebar. Tools are grouped by category, and the search finds them by name.

2. 2

   Pick how to authenticate

   Paste a token or key (each tool's dialog has a step-by-step guide to create one), or use OAuth where this server has it configured.

3. 3

   Save it to the Vault

   The value is encrypted on the server as soon as it arrives. From then on, only its metadata is shown.

4. 4

   Test the connection

   Test connection checks the credential against the vendor's identity endpoint and, in parallel, runs an MCP handshake with the same token.

What the test results mean#

Use it on the Canvas#

1. 1

   Add a Connector

   Open the Connector Hub from the Assets panel and pick the tool: the Connector arrives pre-configured, linked under the selected Sub-Agent or Skill.

2. 2

   Link the credential

   In the inspector, link the Connector to the organization's connection or to a credential of its own. A Connector with neither uses the organization's connection at run time, unless its last test failed.

3. 3

   Point the Skill at the tool

   Link the Skill to the Connector and, optionally, set the Skill's MCP tool name to the exact tool on the server.

What the export contains#

Exported files never contain secrets. .mcp.json names each credential as an environment variable placeholder:

{
  "mcpServers": {
    "stripe": {
      "type": "http",
      "url": "https://mcp.stripe.com",
      "headers": { "Authorization": "Bearer ${ENV_STRIPE_KEY}" }
    }
  }
}

Set those variables in the environment where Claude Code runs.

Custom MCP servers#

For an internal tool, use Custom MCP server: give its URL (https://…) and a token, then test it like any other. In production, private and loopback addresses are refused (SSRF protection).

Security notes#

• Credentials are encrypted at rest (AES-256-GCM) and bound to your organization: a copied row doesn't decrypt anywhere else.
• Plaintext exists only on the server, only for the request that needs it: a run or a connection test.
• Rotate a credential by saving a new value: every node that points to it follows.
• Prefer least-privilege tokens: read-only where the workflow only reads.

Troubleshooting#