Updated Oct 25, 2026

AutoTalk MCP Connect

Use this action when AutoTalk's managed in-app helper agent needs to connect to AutoTalk's own MCP server and use its tools.

This action must be preceded by a Generate JWT token step at position 0: it reads the token with the CEL expression workflow.step(0).jwt and fails with autotalk_mcp_missing_jwt when that step did not produce one.

Best for

• Letting the in-app helper agent call AutoTalk MCP tools on behalf of your company
• Managed setups where the server URL and the authentication header are computed server-side instead of being configured by hand

Main fields

This action has no configurable fields. The server URL and the authentication header are computed server-side, and the helper relationship is verified at run time.

What later steps can use

Connection details are available at:

• workflow.step(N).url
• workflow.step(N).toolCount

As with Connect MCP Server, the step registers the server and discovery completes while the agent prepares its next model call, so workflow.step(N).toolCount reports 0 at the moment the step finishes.

Tips

• This is a managed action: it is hidden from the action picker and only runs for the company's in-app helper channel with its assigned agent. Any other context fails with autotalk_mcp_not_authorized.
• The injected token is a company-scoped /v1 JWT sent as the x-jwt-token header — the helper authenticates as your company, not as the individual signed-in user. It can do only what the token's scopes allow, which is the grant stored on your helper: full company access (account:admin) for a helper created with the current default. A helper keeps the grant it was created with, and your company can narrow it. Creating and publishing libraries, for example, needs automation:admin.
• The JWT step's default 300-second lifetime is normally enough; keep it short.
• For connecting your own servers, use Connect MCP Server (actions/mcp/connect) instead.