> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livefaces.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools and integrations

> Connect MCP servers and choose which tools a conversation can use.

An MCP connection makes an external service's tools available to your organization. Registering a connection and enabling it for a session are separate steps.

## Register a connection

An owner or administrator can open **Tools → Register MCP**:

1. Enter a recognizable **Connection name**.
2. Enter the server's public HTTPS **Endpoint URL** for Streamable HTTP.
3. Select **Bearer token** or **No authentication**. Enter the token when required.
4. Click **Save & test**, then review the status and discovered tools.

Credentials cannot be viewed after saving. When editing the same endpoint, leave the token blank to keep the current credential. Use **Test & refresh** after changing the server's available tools.

## Use tools

| Context | How to select tools |
| - | - |
| Playground | Expand **Tools for this session**, enable a connection, and select individual tools. |
| Conversation goal / Collect information | Select from **Approved read tools** in the node inspector. |
| Call MCP tool | Select one **Approved MCP tool** and map its inputs. |
| Authenticate | Select the connection, authentication challenge, and trusted verifier. |

Workflow tool selectors require approved bindings. If a connected server's tools are missing, ask an owner or administrator to check their approval and connection revision.

For actions that change external data, pair **Confirm action** with **Call MCP tool**. See the [node explorer](https://docs.livefaces.ai/workflows/nodes.md#confirm-action).

## Connection states

**Active** connections can be selected. For **error** connections, review the displayed error, correct the endpoint or credential, and test again. **Disable** prevents selection until re-enabled. Deleting a connection prevents new sessions from selecting it.

Published workflows use pinned dependencies. Refreshing discovery does not automatically update a published workflow; review, test, and publish changes deliberately.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.