MCP server authorization

Choose a Connection Method

• Shared project account for a custom server: no authorization, a token, custom headers, or MCP OAuth.
• Lead JWT for a custom MCP: the server verifies the signed identity of a specific visitor.
• Ready-made MCP authorization: available sign-in methods are defined by the connection template.

Website Visitor

If a ready-made connection supports a user token, use server-side visitor token linking. This is a separate option, not the JWT flow for a custom MCP.

Access Errors

Authorization required and Access denied call for different actions:

• If visitor sign-in is required, use the method configured for the connection: ready-made MCP authorization, token linking, or lead JWT. Signing in to the Senler cabinet does not by itself authorize a visitor in an arbitrary MCP.
• If a shared project account is used, check its token, headers, or OAuth connection in the MCP settings. Visitor sign-in does not replace project authorization.
• When access is denied, check the connected account's permissions for the required data and actions. Signing in again does not guarantee those permissions.

A network failure or an unavailable server does not prove the token is invalid. Check the error in the tool call history before changing the authorization method.

Deleting a connection

Click Delete and confirm with the button in the confirmation dialog. After deletion, agents that selected this connection cannot use its tools until another connection is selected.

Check project agent settings before deletion.