Tool

What this type is for

Choose Tool when an installed application needs to give agents new actions, show its own interface inside the cabinet, or combine both capabilities. For example, an agent can create a payment link or find an order in an external CRM, while an embedded page displays connection settings.

Capabilities you can enable

• HTTP tool builder — several actions with separate URLs, parameters, execution modes, and request signatures.
• MCP server — one MCP endpoint from which Senler loads available tools.
• Embedded page — the application's cabinet interface for settings, reports, or other user work.
• Configurable tool instance — a form that opens when an action is added to an agent and stores public and private settings for that particular connection.

Tools and the embedded page are enabled independently. You can publish agent actions only, the page only, or both.

How the application appears in a project

The user installs the application from the plugin catalog. Installation connects its capabilities to the project but does not add every action to every agent: the required tool is selected separately in the agent settings. If the application needs to read or change project data through the API, it also runs a regular OAuth authorization flow.

The user installation flow is described in Plugins.

Agent tools

In the tools section, choose one connection method for the complete application: builder or MCP server. For an HTTP action, define its system name, clear Russian and English names and descriptions, endpoint, parameters, timeout, and execution mode. The handler must verify the request signature and use event_id as an idempotency key.

When a user needs to select an account or provide a secret while adding an action, enable a configurable instance and implement its form through Senler Bridge. Private data must not be returned by the public API or written to logs.

Embedded page

In the embedded page settings, enter the primary HTTPS URL. A separate developer URL can point to a local or test environment for application team members. The page server verifies the one-time launch_code; senler_* query parameters help render the interface but do not prove access by themselves.

Through Senler Bridge, the page receives verified launch context and can support highlighting and permitted interactions with interface elements. Use stable data-ai-context-id values in the app.* namespace so the documentation and interface work consistently.

Before publication

Check installation in a test project, HTTP request signatures or MCP endpoint availability, timeout handling, embedded-page framing, OAuth permissions when used, and public documentation. Then submit the application for moderation from Catalog publication.