Creating and Configuring an Application Through User MCP
What Each Source Is For
| Source | What AI reads from it |
|---|---|
| Senler documentation | Application types, OAuth rules, launch_code, Bridge, webhook contracts, steps, and publication limits. |
| Senler.io User MCP | The user's current applications and the operations that create or change them. |
| Installed Senler UI and SDK packages | Exact TypeScript types, exports, and method signatures while implementing the code. |
| Official external-service documentation | The current amoCRM, payment-provider, or other connected API contract. |
Project MCP works with one project. A direct personal User MCP connection is used to create and configure applications owned by the developer.
AI first looks for an existing application owned by the user and creates a new one only when none matches. Requests such as “create an application through User MCP,” “configure my application,” and “check whether this application already exists” therefore follow the same workflow below.
Workflow
- AI reads the relevant application-type and capability pages with
search_documentationandget_documentation_page. - AI uses
searchto find the operation that lists the user's applications and checks whether the application already exists. - If it does not exist, AI searches for the operation that creates an application through user OAuth. It must use the OAuth provision operation with
can_create_apps; the similarly named cabinet operation that requires session authentication is not available through User MCP. - AI discovers a separate operation for each concern: general settings, OAuth, embedded page, tools, application actions, webhooks, or automation steps. Fields come from
describe_method, and unrelated settings are preserved. - After a write, AI reads the application or its steps again and verifies the state that was actually saved.
Developer-application methods use appId; they do not need project_id. A direct User MCP connection uses project_id only for a particular project's data or for actions of an application already installed in that project.
Drafts And Publication
A new automation step starts as a draft. It can be published after its endpoint has been implemented and tested. Publishing a step and submitting an application for moderation change availability, so AI performs them only when the user explicitly requests those actions.
Manual Steps
User MCP does not return secrets that require session authentication, such as the application's shared webhook secret. The developer copies such a secret in the cabinet and stores it on the backend. AI should explain this step instead of trying to retrieve the secret through another method.
User MCP alone is not sufficient for an external integration: the Senler contract comes from this documentation, while the external API contract must be checked against that provider's current official documentation.