Combien d'outils expose io.bootify/mcp ?

io.bootify/mcp expose 57 outil(s). Le coût de contexte pour les charger tous est d'environ 100261 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Dev & Code / io.bootify/mcp

io.bootify/mcp

serveur MCP (Model Context Protocol) · bootify-mcp-server 1.0.0

▸ Dev & Code

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~100261 tokensCoût de contexte

57Outils

Est-ce que io.bootify/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.bootify/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 57 outils

addAppModule≈ 1945 tokens
Available with Bootify Professional. Add a custom application module. References name the modules this module depends on. The same graph defines package boundaries for MODULITH and physical build modules for MULTI_MODULE; select either with updateAdvancedOptions first. The implicit base module is the lowest-level shared module and is integrated directly or transitively by every other module. A custom module with no references depends on base. The implicit web module is the highest-level application wrapper and automatically depends on every custom root module; in MULTI_MODULE it assembles the executable application. Neither implicit module can be edited. Dependencies must be acyclic and should point from a feature toward the lower-level modules it uses. Background information: https://bootify.io/docs/modules-tab.html
Paramètres, retour & exemple (3)
Paramètres
- name · string · requis
  Name of the new custom module
- projectId · string · requis
  The project ID returned by startProject
- references · array · optionnel
  Unique names of existing custom modules used as direct dependencies. References already available through another selected module are removed automatically. Omit or use an empty array to depend on the implicit base module.
Exemple d'appel
```
{"name": "addAppModule", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addBreakpoint≈ 384 tokens
Available with Bootify Professional. Snapshot the current database schema so subsequent schema changes generate a new Flyway, Liquibase or Mongock changelog. Available only when getProject BREAKPOINTS reports AVAILABLE. Generated changelogs are blueprints and must be adapted to production data. Use this tool only after the user has explicitly confirmed adding a breakpoint.
Paramètres, retour & exemple (1)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "addBreakpoint", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"projectId": "texte", "breakpoints": [], "breakpointId": "texte", "breakpointStatus": "NO_SCHEMA", "userProjectChanged": true}}
```
addDataObject≈ 2218 tokens
Add a custom data object by name. Entity-generated DTOs are returned by getProject with generated=true and must be changed through their entity fields or REST/frontend options. Background information: https://bootify.io/spring-data/hibernate-json-type.html
Paramètres, retour & exemple (5)
Paramètres
- name · string · requis
  Name of the new data object
- fields · array · requis
  Complete ordered data object field list.
- appModule · string|null · optionnel
  Custom app module; null selects base. Available with Bootify Professional.
- projectId · string · requis
  The project ID returned by startProject
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "addDataObject", "arguments": {"name": "texte", "fields": [], "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addDependency≈ 1709 tokens
Add an extra application dependency to the generated Maven or Gradle build. Bootify already adds dependencies required by selected project features. Call listAvailableDependencies to find supported coordinates, then pass the returned groupId:artifactId. Spring Boot supplies the compatible dependency version.
Paramètres, retour & exemple (2)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- dependency · string · requis
  Maven coordinates: groupId:artifactId[:version]
Exemple d'appel
```
{"name": "addDependency", "arguments": {"projectId": "texte", "dependency": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addEntity≈ 2337 tokens
Add an entity to an existing Bootify project. Entity, field, module, inheritance and custom field-type references use names.
Paramètres, retour & exemple (11)
Paramètres
- name · string · requis
  Name of the new entity
- fields · array · requis
  Complete ordered entity field list. Exactly one primary key is required for a concrete entity unless inherited; abstract superclasses may omit it. A primary key must be the first field and use INTEGER, LONG, UUID or STRING. required is ignored for it.
- inherits · string|null · optionnel
  Name of the superclass entity; null removes inheritance
- appModule · string|null · optionnel
  App module name; null selects the base module. Available with Bootify Professional.
- projectId · string · requis
  The project ID returned by startProject
- superclass · boolean · optionnel
- restEnabled · boolean · optionnel
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
- frontendEnabled · boolean · optionnel
- paginationEnabled · boolean · optionnel
- searchFilterEnabled · boolean · optionnel
Exemple d'appel
```
{"name": "addEntity", "arguments": {"name": "texte", "fields": [], "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addEnum≈ 1810 tokens
Add an enum to an existing Bootify project, identified by name.
Paramètres, retour & exemple (5)
Paramètres
- name · string · requis
  Name of the new enum
- values · array · requis
  Ordered, unique enum values such as DRAFT and PUBLISHED
- appModule · string|null · optionnel
  Custom app module name; null selects base. Available with Bootify Professional.
- projectId · string · requis
  The project ID returned by startProject
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "addEnum", "arguments": {"name": "texte", "values": [], "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addFrontendController≈ 2374 tokens
Available with Bootify Professional. Add a custom frontend controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Paramètres, retour & exemple (7)
Paramètres
- name · string · requis
  Name of the new frontend controller
- path · string · requis
  Controller base path, with optional {name} placeholders
- appModule · string|null · optionnel
  Custom application module name; null selects the web module
- endpoints · array · requis
- projectId · string · requis
  The project ID returned by startProject
- parameters · array · requis
  Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter.
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "addFrontendController", "arguments": {"name": "texte", "path": "texte", "endpoints": [], "projectId": "texte", "parameters": []}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addIndex≈ 1837 tokens
Add a normal or unique index over ordered entity fields or owning-side relations. Many-to-many relations are excluded. The response returns its name selector as Entity.field1-field2.
Paramètres, retour & exemple (4)
Paramètres
- entity · string · requis
  Entity containing the indexed fields or owning-side relations
- fields · array · requis
  Ordered field or owning-side relation names. Order affects index usage; many-to-many relations are not available and a primary key cannot be used alone.
- unique · boolean · requis
  Whether the index enforces a unique field combination
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "addIndex", "arguments": {"entity": "texte", "fields": [], "unique": true, "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addRelation≈ 2121 tokens
Add a relation whose type describes the cardinality from fromEntity to toEntity. For MANY_TO_ONE, ONE_TO_ONE and MANY_TO_MANY the owning field is fromEntity.fromField; for ONE_TO_MANY it is toEntity.toField. The response includes that canonical owning-side value as identifier. Bidirectional relations require both fields. Background information: https://bootify.io/docs/jpa-relationship-types-with-examples.html. fromEntity and toEntity must already exist. The owning entity's application module must depend on the target entity's module.
Paramètres, retour & exemple (9)
Paramètres
- type · string · requis · MANY_TO_ONE | ONE_TO_MANY | ONE_TO_ONE | MANY_TO_MANY
  Cardinality from fromEntity to toEntity
- toField · string|null · optionnel
  Field generated on toEntity. Required for ONE_TO_MANY and bidirectional relations; also required for self-referencing MANY_TO_MANY relations
- required · boolean · optionnel
  Whether the owning foreign key is required. Not applicable to MANY_TO_MANY or self-relations
- toEntity · string · requis
  Entity on the to side of the cardinality
- fromField · string|null · optionnel
  Field generated on fromEntity. Required unless an unidirectional ONE_TO_MANY relation omits this reverse field
- projectId · string · requis
  The project ID returned by startProject
- tableName · string|null · optionnel
  Join-table name; required only for MANY_TO_MANY
- fromEntity · string · requis
  Entity on the from side of the cardinality
- unidirectional · boolean · optionnel
  Omit the reverse field. Relations across application modules must be unidirectional
Exemple d'appel
```
{"name": "addRelation", "arguments": {"type": "MANY_TO_ONE", "toEntity": "texte", "projectId": "texte", "fromEntity": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "identifier": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addRestController≈ 2552 tokens
Available with Bootify Professional. Add a custom REST controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Paramètres, retour & exemple (7)
Paramètres
- name · string · requis
  Name of the new REST controller
- path · string · requis
  Controller base path, with optional {name} placeholders
- appModule · string|null · optionnel
  Custom application module name; null selects the web module
- endpoints · array · requis
- projectId · string · requis
  The project ID returned by startProject
- parameters · array · requis
  Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter.
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "addRestController", "arguments": {"name": "texte", "path": "texte", "endpoints": [], "projectId": "texte", "parameters": []}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
addSecurityConfig≈ 1786 tokens
Create a config with safe defaults. Configure roles, login and an optional user source through their dedicated tools.
Paramètres, retour & exemple (5)
Paramètres
- name · string · requis
  Security config name
- type · string · requis · BASIC_AUTH | JWT | FORM_SESSION | KEYCLOAK_RESOURCE_SERVER | KEYCLOAK_CLIENT
- appModule · string|null · optionnel
  Custom app module; null selects base
- projectId · string · requis
  The project ID returned by startProject
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "addSecurityConfig", "arguments": {"name": "texte", "type": "BASIC_AUTH", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
configureSecurityLogin≈ 1797 tokens
Configure only login, JWT, Keycloak and session behavior. Provide just the fields that should change.
Paramètres, retour & exemple (9)
Paramètres
- name · string · requis
  Security config name
- projectId · string · requis
  The project ID returned by startProject
- rememberMe · string|null · optionnel · None | NONE | CHECKBOX | ALWAYS
- jwtAlgorithm · string|null · optionnel · None | HMAC | RSA
- loginMethods · array · optionnel
- loginClientIds · object · optionnel
- keycloakRealmId · string|null · optionnel
- keycloakClientId · string|null · optionnel
- registrationEndpoint · boolean · optionnel
Exemple d'appel
```
{"name": "configureSecurityLogin", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
configureSecurityUserSource≈ 1887 tokens
Configure the user entity and its credential, OAuth mapping, password reset and token fields. Provide just the fields that should change.
Paramètres, retour & exemple (14)
Paramètres
- name · string · requis
  Security config name
- hashField · string|null · optionnel
- projectId · string · requis
  The project ID returned by startProject
- sourceEntity · string|null · optionnel
  User source entity; null uses in-memory users
- mapEmailField · string|null · optionnel
- resetUidField · string|null · optionnel
- usernameField · string|null · optionnel
- loginTypeField · string|null · optionnel
- externalIdField · string|null · optionnel
- resetStartField · string|null · optionnel
- mapLastNameField · string|null · optionnel
- refreshTokenPath · string|null · optionnel
- mapFirstNameField · string|null · optionnel
- refreshTokenExpiryPath · string|null · optionnel
Exemple d'appel
```
{"name": "configureSecurityUserSource", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
copyProject≈ 7295 tokens
Copy a project owned by the bearer-authenticated user. Projects with an active one-time upgrade cannot be copied.
Paramètres, retour & exemple (1)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "copyProject", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "project": {}, "planLevel": "FREE", "projectId": "texte", "planStatus": "VALID", "projectUrl": "texte", "userProjectChanged": true}}
```
deleteAppModule≈ 1680 tokens
Delete a custom application module by name. The implicit base and web modules cannot be deleted. Bootify applies its consistency rules to references and assigned project elements. Available with Bootify Professional.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Name of the custom module to delete
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteAppModule", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteDataObject≈ 1688 tokens
Delete a custom data object by name. Entity-generated DTOs are returned by getProject with generated=true and must be changed through their entity fields or REST/frontend options. Background information: https://bootify.io/spring-data/hibernate-json-type.html
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Current name of the data object
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteDataObject", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteEntity≈ 1646 tokens
Delete an entity identified by name. Bootify applies its consistency rules to dependent project data.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Name of the entity to delete
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteEntity", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteEnum≈ 1646 tokens
Delete an enum identified by name. Referencing fields are changed to String by Bootify's consistency rules.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Name of the enum to delete
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteEnum", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteFrontendController≈ 1686 tokens
Available with Bootify Professional. Delete a custom frontend controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Current name of the frontend controller
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteFrontendController", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteIndex≈ 1644 tokens
Delete an index by its current name.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Current Entity.field1-field2 identifier
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteIndex", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteProject≈ 181 tokens
Close a project owned by the bearer-authenticated user.
Paramètres, retour & exemple (1)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteProject", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"closed": true, "projectId": "texte"}}
```
deleteRelation≈ 1716 tokens
Delete a relation using the current identifier returned by addRelation, updateRelation or getProject with RELATIONS details. The identifier is the owning entity and owning field joined with a dot; copy it verbatim because ONE_TO_MANY ownership is on the to side.
Paramètres, retour & exemple (2)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- identifier · string · requis
  Current identifier copied verbatim from addRelation, updateRelation or getProject RELATIONS
Exemple d'appel
```
{"name": "deleteRelation", "arguments": {"projectId": "texte", "identifier": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteRestController≈ 1682 tokens
Available with Bootify Professional. Delete a custom REST controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Current name of the REST controller
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteRestController", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
deleteSecurityConfig≈ 1634 tokens
Delete a security configuration by name.
Paramètres, retour & exemple (2)
Paramètres
- name · string · requis
  Security config to delete
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "deleteSecurityConfig", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
exportProject≈ 388 tokens
Return a ZIP download URL for an existing Bootify project. This tool should be called after all project details and the schema have been configured with the user and the current setup has been presented. Ask for approval before exporting unless the user already explicitly requested the export in the current context. The client can download and extract it when the environment supports it. Export fails when the project plan has expired. Successful calls record MCP usage and activity for this project. Generated files can include private signing keys for RSA JWT configurations; treat them as sensitive.
Paramètres, retour & exemple (1)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "exportProject", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "filename": "texte", "projectId": "texte", "contentType": "texte", "downloadUrl": "texte", "userProjectChanged": true}}
```
exportProjectToGit≈ 396 tokens
Available with Bootify Professional. Generate, commit and push to the saved repository and target branch. Replaces the target branch's file contents with the generated project, including deleting other files. Use only when the user has authorized the Git export. Inspect getGitExportStatus first. The optional message overrides defaultCommitMessage; when omitted it is calculated at export time. No commit is created when generated files have not changed; commitSha is then null. Requires saved Git credentials and active export access. Successful calls record MCP usage and activity.
Paramètres, retour & exemple (2)
Paramètres
- message · string · optionnel
- projectId · string · requis
Exemple d'appel
```
{"name": "exportProjectToGit", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "commitSha": "texte", "projectId": "texte", "hasChanges": true, "targetBranch": "texte", "repositoryUrl": "texte", "userProjectChanged": true}}
```
getGitExportStatus≈ 372 tokens
Available with Bootify Professional. Return the saved repository URL, target branch and defaultCommitMessage derived from current changes using the builder's commit message generator. This does not contact the remote or preview a Git diff. Credentials are never returned. If unconfigured, open configurationUrl to configure Git in the builder. Successful calls record MCP usage and activity for this project.
Paramètres, retour & exemple (1)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "getGitExportStatus", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"projectId": "texte", "configured": true, "targetBranch": "texte", "repositoryUrl": "texte", "configurationUrl": "texte", "userProjectChanged": true, "defaultCommitMessage": "texte"}}
```
getOpenApiPreview≈ 360 tokens
Available with Bootify Professional. Generate and return the OpenAPI document for the current project configuration. Use it to inspect resolved paths, parameters, request and response schemas, status codes and security schemes before exporting the project. Successful calls record MCP usage and activity for this project.
Paramètres, retour & exemple (1)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "getOpenApiPreview", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"document": {}, "pathCount": 1, "projectId": "texte", "schemaCount": 1, "openApiVersion": "texte", "userProjectChanged": true}}
```
getProject≈ 7241 tokens
Return the current basic configuration and plan information of an existing Bootify project. Entity, relation, index and other object lists are returned only when explicitly selected through details. Successful calls record MCP usage and activity for this project.
Paramètres, retour & exemple (2)
Paramètres
- details · array · optionnel
  Without details, only basic configuration and plan information are returned. Select additional areas explicitly, for example ENTITIES, RELATIONS and INDEXES. APP_MODULES, BREAKPOINTS, REST_CONTROLLERS and FRONTEND_CONTROLLERS: Available with Bootify Professional.
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "getProject", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "enums": [], "group": "texte", "indexes": [], "database": {}, "entities": [], "frontend": {}, "language": "JAVA", "buildType": "GRADLE", "planLevel": "FREE", "relations": [], "appModules": []}}
```
getProjectFile≈ 390 tokens
Return one generated project file. The path may exactly match a value returned by listProjectFiles, with or without the project root directory, such as pom.xml. Text is returned as UTF-8 and binary content as Base64. Successful calls record MCP usage and activity for this project. Generated files can include private signing keys for RSA JWT configurations; treat them as sensitive.
Paramètres, retour & exemple (2)
Paramètres
- path · string · requis
  An exact path from listProjectFiles, with or without the project root directory
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "getProjectFile", "arguments": {"path": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"path": "texte", "size": 1, "content": "texte", "message": "texte", "encoding": "UTF-8", "projectId": "texte", "contentType": "texte", "userProjectChanged": true}}
```
importSqlSchema≈ 1692 tokens
Parse SQL DDL and reconcile its tables, fields and relations with an existing Bootify project. Matching entities are updated and new entities are added.
Paramètres, retour & exemple (2)
Paramètres
- sql · string · requis
  SQL DDL containing CREATE TABLE statements
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "importSqlSchema", "arguments": {"sql": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "entitiesAdded": [], "entitiesUpdated": [], "userProjectChanged": true}}
```
linkProject≈ 257 tokens
Link an existing Bootify project to the bearer-authenticated user. Accepts either the project URL or its 12-character project ID and updates the project's plan.
Paramètres, retour & exemple (1)
Paramètres
- projectUrl · string · requis
  The project URL or 12-character project ID
Exemple d'appel
```
{"name": "linkProject", "arguments": {"projectUrl": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"planLevel": "FREE", "projectId": "texte", "planStatus": "VALID", "projectUrl": "texte"}}
```
listAvailableDependencies≈ 312 tokens
List dependencies that can be added to the generated Maven or Gradle build. These dependencies are managed by the project's Spring Boot version and therefore do not require a dependency version. Use the optional query to narrow the result. Successful calls record MCP usage and activity for this project.
Paramètres, retour & exemple (2)
Paramètres
- query · string · optionnel
  Optional case-insensitive text contained in the coordinates
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "listAvailableDependencies", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"dependencies": [], "userProjectChanged": true}}
```
listProjectFiles≈ 290 tokens
Return every file path that would be present in the ZIP export of an existing Bootify project, without generating or returning file contents. Listing fails when the project plan has expired. Successful calls record MCP usage and activity for this project.
Paramètres, retour & exemple (1)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "listProjectFiles", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"files": [], "message": "texte", "fileCount": 1, "projectId": "texte", "userProjectChanged": true}}
```
listSecurityPaths≈ 329 tokens
Return the canonical METHOD /path values that may be assigned to security roles. Pass securityConfigName while editing so that its current paths remain available. Frontend paths can only be protected by BASIC_AUTH, FORM_SESSION or KEYCLOAK_CLIENT. Successful calls record MCP usage and activity for this project.
Paramètres, retour & exemple (2)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- securityConfigName · string · optionnel
  Existing config being edited
Exemple d'appel
```
{"name": "listSecurityPaths", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"rest": [], "frontend": [], "userProjectChanged": true}}
```
removeBreakpoint≈ 376 tokens
Available with Bootify Professional. Permanently remove one breakpoint. This changes generated changelogs and cannot be undone. Copy its epoch-second ID from getProject BREAKPOINTS. Use this tool only after the user has explicitly confirmed removing the breakpoint.
Paramètres, retour & exemple (2)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- breakpointId · string · requis
Exemple d'appel
```
{"name": "removeBreakpoint", "arguments": {"projectId": "texte", "breakpointId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"projectId": "texte", "breakpoints": [], "breakpointId": "texte", "breakpointStatus": "NO_SCHEMA", "userProjectChanged": true}}
```
removeDependency≈ 1668 tokens
Remove a dependency from the generated Maven or Gradle build using groupId:artifactId. A version may be supplied but is not used for matching.
Paramètres, retour & exemple (2)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- dependency · string · requis
  Maven coordinates: groupId:artifactId[:version]
Exemple d'appel
```
{"name": "removeDependency", "arguments": {"projectId": "texte", "dependency": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
setSecurityRoles≈ 1816 tokens
Replace the role setup. Call listSecurityPaths first and use its exact METHOD /path values.
Paramètres, retour & exemple (6)
Paramètres
- name · string · requis
  Security config name
- roles · array · requis
- roleEnum · string|null · optionnel
  Enum supplying role names
- projectId · string · requis
  The project ID returned by startProject
- roleSource · string · requis · CONSTANTS | ENUM | ENTITY_FIELD
- roleFieldEnumPath · string|null · optionnel
Exemple d'appel
```
{"name": "setSecurityRoles", "arguments": {"name": "texte", "roles": [], "projectId": "texte", "roleSource": "CONSTANTS"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
startProject≈ 7834 tokens
Create a new Bootify project and return its project ID, URL, current setup and plan information. This changes server state and should only be called when the user wants a new project. Basic settings, developer preferences and database settings can be supplied during creation; omitted settings retain their defaults. All subsequent changes made through MCP are reflected live for the user at the returned project URL. Always show that URL to the user immediately after creating the project so they can follow the changes in their browser.
Paramètres, retour & exemple (7)
Paramètres
- name · string · optionnel
  A project name such as my-project
- group · string · optionnel
  A group name such as com.my-group, used for build settings and package name
- database · object · optionnel
- language · string · optionnel · JAVA | KOTLIN
- buildType · string · optionnel · GRADLE | MAVEN
- lombokEnabled · boolean · optionnel
  Ignored for Kotlin projects
- developerPreferences · object · optionnel
Exemple d'appel
```
{"name": "startProject", "arguments": {"name": "texte", "group": "texte", "database": {}, "language": "JAVA", "buildType": "GRADLE", "lombokEnabled": true}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "project": {}, "planLevel": "FREE", "projectId": "texte", "planStatus": "VALID", "projectUrl": "texte"}}
```
updateAdvancedOptions≈ 2055 tokens
Available with Bootify Professional. Update one or more advanced project options. MODULITH generates package-based application modules, while MULTI_MODULE generates physical Gradle or Maven modules. Select either before defining an application-module graph. Background information: https://bootify.io/docs/modules-tab.html
Paramètres, retour & exemple (10)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- testSetup · string · optionnel · NONE | TESTCONTAINERS | PLAYWRIGHT | ALL
  Generated test setup
- springSession · string · optionnel · NONE | JDBC | REDIS
  Spring Session persistence; JDBC uses the configured relational or embedded database
- hateoasEnabled · boolean · optionnel
  Use HATEOAS for the REST API
- modularization · string · optionnel · NONE | MODULITH | MULTI_MODULE
  NONE generates a monolith; MODULITH and MULTI_MODULE activate the application-module graph
- actuatorEnabled · boolean · optionnel
  Add Spring Boot Actuator
- mapStructEnabled · boolean · optionnel
  Use MapStruct instead of generated mapping code
- actuatorEndpoints · array · optionnel
  Actuator endpoints to expose; an empty list exposes all available endpoints
- multiModulePrefix · boolean · optionnel
  Prefix generated module artifact names with the project name in MULTI_MODULE mode
- serviceInterfaceEnabled · boolean · optionnel
  Generate separate service interfaces and implementations
Exemple d'appel
```
{"name": "updateAdvancedOptions", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateAppModule≈ 2007 tokens
Available with Bootify Professional. Update or rename a custom application module identified by its current name. When provided, references replace all current direct dependencies. The same graph defines package boundaries for MODULITH and physical build modules for MULTI_MODULE; select either with updateAdvancedOptions first. The implicit base module is the lowest-level shared module and is integrated directly or transitively by every other module. A custom module with no references depends on base. The implicit web module is the highest-level application wrapper and automatically depends on every custom root module; in MULTI_MODULE it assembles the executable application. Neither implicit module can be edited. Dependencies must be acyclic and should point from a feature toward the lower-level modules it uses. Background information: https://bootify.io/docs/modules-tab.html
Paramètres, retour & exemple (4)
Paramètres
- name · string · requis
  Current name of the custom module
- newName · string · optionnel
  New module name; omit to keep its name
- projectId · string · requis
  The project ID returned by startProject
- references · array · optionnel
  Unique names of existing custom modules used as direct dependencies. References already available through another selected module are removed automatically. Omit or use an empty array to depend on the implicit base module.
Exemple d'appel
```
{"name": "updateAppModule", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateDataObject≈ 2266 tokens
Update or rename a custom data object by name. Entity-generated DTOs are returned by getProject with generated=true and must be changed through their entity fields or REST/frontend options. Background information: https://bootify.io/spring-data/hibernate-json-type.html
Paramètres, retour & exemple (6)
Paramètres
- name · string · requis
  Current name of the data object
- fields · array · optionnel
  Complete ordered data object field list.
- newName · string · optionnel
  New data object name; omit to keep its name
- appModule · string|null · optionnel
  Custom app module; null selects base. Available with Bootify Professional.
- projectId · string · requis
  The project ID returned by startProject
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "updateDataObject", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateDatabase≈ 1699 tokens
Update the database and schema management settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
Paramètres, retour & exemple (4)
Paramètres
- type · string · optionnel · NONE | OTHER | MSSQL | MYSQL | MARIADB | ORACLE | POSTGRES | MONGODB
- projectId · string · requis
  The project ID returned by startProject
- schemaType · string · optionnel · NONE | HIBERNATE | FLYWAY | LIQUIBASE
- mongoSchemaType · string · optionnel · NONE | MONGOCK
Exemple d'appel
```
{"name": "updateDatabase", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateDatabaseNaming≈ 1718 tokens
Update one or more database naming settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
Paramètres, retour & exemple (5)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- tablePrefix · string|null · optionnel
- tableSuffix · string|null · optionnel
- namingStrategy · string · optionnel · NONE | UPPERCASE_ALL | UPPERCASE_TABLES | CAMELCASE_ALL | CAMELCASE_TABLES
- pluralizeTableName · boolean · optionnel
Exemple d'appel
```
{"name": "updateDatabaseNaming", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateDateFields≈ 1676 tokens
Enable or disable generated date fields and configure their names. Background information: https://bootify.io/docs/general-tab.html
Paramètres, retour & exemple (4)
Paramètres
- enabled · boolean · optionnel
- projectId · string · requis
  The project ID returned by startProject
- dateCreatedName · string · optionnel
- lastUpdatedName · string · optionnel
Exemple d'appel
```
{"name": "updateDateFields", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateDeveloperPreferences≈ 1876 tokens
Update one or more developer preferences of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
Paramètres, retour & exemple (8)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- deployment · string · optionnel · NONE | HEROKU_GITHUB | HEROKU_GITLAB
- javaVersion · integer · optionnel · 17 | 21 | 25
- openApiEnabled · boolean · optionnel
  Generate OpenAPI documentation and Swagger UI
- packageStructure · string · optionnel · TECHNICAL | DOMAIN_DRIVEN | MIXED
  Package layout: TECHNICAL groups classes by technical type in packages such as domain, repos, service and rest; DOMAIN_DRIVEN groups all classes related to an entity in a package named after that entity; MIXED creates an entity package with technical subpackages.
- applicationFormat · string · optionnel · YAML | PROPERTIES
  Format of the generated Spring application configuration
- dockerComposeEnabled · boolean · optionnel
  Generate Docker Compose support for local development
- includeAgentInstructions · boolean · optionnel
  Generate AGENTS.md with coding agent instructions
Exemple d'appel
```
{"name": "updateDeveloperPreferences", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateEntity≈ 2390 tokens
Update or rename an entity identified by its current name. Only provided properties are changed; a provided fields array replaces all fields.
Paramètres, retour & exemple (12)
Paramètres
- name · string · requis
  Current name of the entity to update
- fields · array · optionnel
  Complete ordered entity field list. Exactly one primary key is required for a concrete entity unless inherited; abstract superclasses may omit it. A primary key must be the first field and use INTEGER, LONG, UUID or STRING. required is ignored for it.
- newName · string · optionnel
  New entity name; omit to keep the current name
- inherits · string|null · optionnel
  Name of the superclass entity; null removes inheritance
- appModule · string|null · optionnel
  App module name; null selects the base module. Available with Bootify Professional.
- projectId · string · requis
  The project ID returned by startProject
- superclass · boolean · optionnel
- restEnabled · boolean · optionnel
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
- frontendEnabled · boolean · optionnel
- paginationEnabled · boolean · optionnel
- searchFilterEnabled · boolean · optionnel
Exemple d'appel
```
{"name": "updateEntity", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateEnum≈ 1873 tokens
Update or rename an enum identified by its current name. Provide newName, values, appModule, featurePackage, or several.
Paramètres, retour & exemple (6)
Paramètres
- name · string · requis
  Current name of the enum to update
- values · array · optionnel
  Ordered, unique enum values such as DRAFT and PUBLISHED
- newName · string · optionnel
  New enum name; omit to keep the current name
- appModule · string|null · optionnel
  Custom app module name; null selects base. Available with Bootify Professional.
- projectId · string · requis
  The project ID returned by startProject
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "updateEnum", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateFrontend≈ 1731 tokens
Update one or more frontend settings of an existing Bootify project. Background information: https://bootify.io/docs/frontend-settings.html
Paramètres, retour & exemple (6)
Paramètres
- buildTool · string · optionnel · NONE | VITE | WEBPACK
- framework · string · optionnel · NONE | THYMELEAF | JTE | ANGULAR | REACT
- projectId · string · requis
  The project ID returned by startProject
- htmxEnabled · boolean · optionnel
  Used only with Thymeleaf and JTE
- cssFramework · string · optionnel · BOOTSTRAP | TAILWIND
- typescriptEnabled · boolean · optionnel
  Used only with Vite or Webpack for Thymeleaf and JTE
Exemple d'appel
```
{"name": "updateFrontend", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateFrontendController≈ 2416 tokens
Available with Bootify Professional. Update or rename a custom frontend controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Paramètres, retour & exemple (8)
Paramètres
- name · string · requis
  Current name of the frontend controller
- path · string · optionnel
  Controller base path, with optional {name} placeholders
- newName · string · optionnel
  New controller name; omit to keep its name
- appModule · string|null · optionnel
  Custom application module name; null selects the web module
- endpoints · array · optionnel
- projectId · string · requis
  The project ID returned by startProject
- parameters · array · optionnel
  Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter.
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "updateFrontendController", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateIndex≈ 1880 tokens
Update an index by its current Entity.field1-field2 identifier. Only provided properties are changed; the response contains its updated identifier.
Paramètres, retour & exemple (5)
Paramètres
- name · string · requis
  Current Entity.field1-field2 identifier
- entity · string · optionnel
  Entity containing the indexed fields or owning-side relations
- fields · array · optionnel
  Ordered field or owning-side relation names. Order affects index usage; many-to-many relations are not available and a primary key cannot be used alone.
- unique · boolean · optionnel
  Whether the index enforces a unique field combination
- projectId · string · requis
  The project ID returned by startProject
Exemple d'appel
```
{"name": "updateIndex", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateMailSettings≈ 1736 tokens
Available with Bootify Professional. Enable or disable mail support and configure the generated application's SMTP connection.
Paramètres, retour & exemple (7)
Paramètres
- from · string|null · optionnel
- host · string|null · optionnel
- enabled · boolean · optionnel
- username · string|null · optionnel
- projectId · string · requis
  The project ID returned by startProject
- connection · string · optionnel · TLS | SSL
- displayName · string|null · optionnel
Exemple d'appel
```
{"name": "updateMailSettings", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateRelation≈ 2230 tokens
Update a relation whose type describes the cardinality from fromEntity to toEntity. For MANY_TO_ONE, ONE_TO_ONE and MANY_TO_MANY the owning field is fromEntity.fromField; for ONE_TO_MANY it is toEntity.toField. The response includes that canonical owning-side value as identifier. Bidirectional relations require both fields. Background information: https://bootify.io/docs/jpa-relationship-types-with-examples.html. Identify the existing relation with its current identifier returned by addRelation, updateRelation or getProject; do not reconstruct internal IDs. Only provided relation properties are changed. If an update changes the owning entity or field, use the newly returned identifier for subsequent calls.
Paramètres, retour & exemple (10)
Paramètres
- type · string · optionnel · MANY_TO_ONE | ONE_TO_MANY | ONE_TO_ONE | MANY_TO_MANY
  Cardinality from fromEntity to toEntity
- toField · string|null · optionnel
  Field generated on toEntity. Required for ONE_TO_MANY and bidirectional relations; also required for self-referencing MANY_TO_MANY relations
- required · boolean · optionnel
  Whether the owning foreign key is required. Not applicable to MANY_TO_MANY or self-relations
- toEntity · string · optionnel
  Entity on the to side of the cardinality
- fromField · string|null · optionnel
  Field generated on fromEntity. Required unless an unidirectional ONE_TO_MANY relation omits this reverse field
- projectId · string · requis
  The project ID returned by startProject
- tableName · string|null · optionnel
  Join-table name; required only for MANY_TO_MANY
- fromEntity · string · optionnel
  Entity on the from side of the cardinality
- identifier · string · requis
  Current identifier copied verbatim from addRelation, updateRelation or getProject RELATIONS
- unidirectional · boolean · optionnel
  Omit the reverse field. Relations across application modules must be unidirectional
Exemple d'appel
```
{"name": "updateRelation", "arguments": {"projectId": "texte", "identifier": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "identifier": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateRestController≈ 2594 tokens
Available with Bootify Professional. Update or rename a custom REST controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Paramètres, retour & exemple (8)
Paramètres
- name · string · requis
  Current name of the REST controller
- path · string · optionnel
  Controller base path, with optional {name} placeholders
- newName · string · optionnel
  New controller name; omit to keep its name
- appModule · string|null · optionnel
  Custom application module name; null selects the web module
- endpoints · array · optionnel
- projectId · string · requis
  The project ID returned by startProject
- parameters · array · optionnel
  Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter.
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
Exemple d'appel
```
{"name": "updateRestController", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateSecurityConfig≈ 1843 tokens
Change only the identity, type, module or authentication mode. Changing type resets type-specific settings to defaults.
Paramètres, retour & exemple (7)
Paramètres
- name · string · requis
  Current config name
- type · string · optionnel · BASIC_AUTH | JWT | FORM_SESSION | KEYCLOAK_RESOURCE_SERVER | KEYCLOAK_CLIENT
- newName · string · optionnel
  New config name
- appModule · string|null · optionnel
  Custom app module; null selects base
- projectId · string · requis
  The project ID returned by startProject
- featurePackage · string|null · optionnel
  Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment
- authenticationMethod · string · optionnel · ANNOTATION_BASED | CONFIG_BASED
Exemple d'appel
```
{"name": "updateSecurityConfig", "arguments": {"name": "texte", "projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateSettings≈ 1750 tokens
Update one or more basic settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
Paramètres, retour & exemple (6)
Paramètres
- name · string · optionnel
  A project name such as my-project
- group · string · optionnel
  A group name such as com.my-group, used for build settings and package name
- language · string · optionnel · JAVA | KOTLIN
- buildType · string · optionnel · GRADLE | MAVEN
- projectId · string · requis
  The project ID returned by startProject
- lombokEnabled · boolean · optionnel
  Ignored for Kotlin projects
Exemple d'appel
```
{"name": "updateSettings", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```
updateUtilities≈ 1796 tokens
Include utilities for custom code even when the project does not require them. Required utilities cannot be disabled. They remain included when no longer required, until explicitly disabled. Omitted options retain their values. Inspect utilities in getProject for the current inclusion state.
Paramètres, retour & exemple (5)
Paramètres
- projectId · string · requis
  The project ID returned by startProject
- includeInputRow · boolean · optionnel
  Include inputRow and supporting form utilities; requires Thymeleaf, jte, Angular or React
- includeFileHandling · boolean · optionnel
  Include file handling services and database storage
- includeSearchFilter · boolean · optionnel
  Include frontend search filter utilities; requires a frontend framework
- includePaginationAndSorting · boolean · optionnel
  Include frontend pagination and sorting utilities; requires a frontend framework
Exemple d'appel
```
{"name": "updateUtilities", "arguments": {"projectId": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"changes": {}, "projectId": "texte", "affectedAreas": [], "userProjectChanged": true}}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://bootify.io/mcp