Node Reference
MCP Credential Node
Configure an encrypted credential surface for MCP tool handlers.
The MCP Credential node is part of Builder Studio's MCP Server Builder. It declares the encrypted credential surface a published user MCP tool handler requires — for example an API key or token the backing workflow needs to reach a third-party service — so secrets are configured and stored securely rather than written into the graph.
Availability
The MCP Server Builder node types are part of the published user MCP roadmap and are not yet available to place on the canvas in this build. This page documents their intended purpose so you can plan around them. For what is live today, see the marketplace and the Builder MCP CLI.
What it is meant to do
- Declare which credentials a published MCP tool's workflow needs to run.
- Keep those secrets in an encrypted credential surface that the published server owner manages, rather than embedding them in node data.
- Let a tool handler read its required credentials at call time without exposing them to the calling client.
Credentials are owner-managed
Following the published-MCP model, credentials for a protected server are managed by the server owner. They are not issued self-serve to other operators who consume the server. See Marketplace overview for the auth model.
How it relates to the other builder nodes
- MCP Tool— defines the tool surface and inputs.
- MCP Output— selects the value returned to the client.
- MCP Credential — declares the encrypted credentials a tool handler needs.
Where to continue today
For configuring real provider credentials and keys that work now, see Integrations and Authentication.
Was this page helpful?