Application settings

Core details

The application page opens after creation. Settings contains the common fields and publication state; type-specific capabilities are placed in the neighboring items.

• the name is shared by all language versions;
• the description is entered separately on the Russian and English tabs in the description block: the Russian description is shown in the Russian catalog and the English description in the English catalog;
• the avatar and cover can be uploaded, replaced, or removed after creation; an avatar is required for moderation, while the cover is optional;
• the application website can be added after creation: a domain without a protocol is saved with https://, while an explicit http:// or https:// is preserved;
• the application type is selected during creation and cannot be changed in the cabinet later;
• a ready-made solution also has the installed agent settings visibility switch here;
• a Website integration configures project access and user access independently under OAuth; there is no need to select one immutable option during creation.

Testing before publication

An application with Private status can be made available to a specific project without publishing it for everyone. This lets you test plugin or Ready-made solution installation before moderation.

1. Choose a regular test project. A Ready-made solution cannot be installed in its own source project.
2. Through the API, call POST /api/apps/{appId}/access with the JSON body { "project_id": "ID_TEST_PROJECT" }. You need a user-scoped OAuth token with can_manage_app_catalog permission and corresponding application access; a project API key does not work. In User MCP, find the Grant project access operation and use its returned schema.
3. In the selected project, open the plugin catalog or Ready-made solution catalog. The private application appears in that project's catalog. Install it and test the required tools, events, or steps. A Ready-made solution must already have a published version.

Granting this access neither installs the application automatically nor permits it to read project data. Installation and OAuth approval remain separate actions. To test a Website integration, complete project-scoped OAuth authorization: it is available before publication without a prior catalog access grant.

GET /api/apps/{appId}/access returns projects with granted access. DELETE /api/apps/{appId}/access/{projectId} closes that access, but does not remove an existing installation or revoke its tokens. To stop the application in a project, separately remove the installation.

Catalog publication

The publication block is located below the general settings for every application type. Before submission, enter the shared name and both the Russian and English descriptions, then upload an avatar. Complete the requirement for the selected type:

• for a Website integration, add at least one redirect URI;
• for a Plugin, configure at least one capability: agent tools, an embedded page, or application actions;
• for a ready-made solution, create the source project and publish at least one version.

Then select Submit for moderation.

The cabinet shows a pending status and submission date while the request is being reviewed; moderation may take up to two weeks. If moderation rejects it, fix the issues from the moderator comment and submit the application again. After approval, the application can be hidden from the catalog or shown again without another moderation review. A member without publication management permission can see the state but cannot submit the application or change its visibility.

Deleting an application

The Delete button is on the left of the bottom row of general settings, next to Save. Only the owner can delete the application. The button opens a confirmation dialog; the final action is performed through Delete in that dialog.

After confirmation, the application disappears from the cabinet and catalog. The API revokes every installation, project and user OAuth access, refresh token, and unused authorization code; the application's webhooks and settings stop working. The cabinet then returns to the application list.